By Altitudes on Monday, 18 January 2016
Posted in Technical Issues
Replies 5
Likes 0
Views 1.2K
Votes 0
Hello

Image inserted in a blog post with Composer generates the following HTML (example from this page)

<img src="//http://www.altitudes.asso.fr/images/easyblog_articles/48/b2ap3_thumbnail_04_soire_accueil.jpg">

I have 2 remarks regarding this:
- URL starting with // instead of http:// is a bit strange. Maybe not incorrect technically speaking, but a bit unexpected.
- hostname is hardcoded. I you move your site to another server hostname, original hostname remains (I have tested it). Not a big issue when you are just copying your site to a dev site as I do, but if one day one of your customers moves his site to another hostname, he will have to go through all his posts to change the image URLs

+Enhancement Request
Hey Altitudes,

By using // instead of http:// , it will be protocol independent. If we use http:// over https:// and you decide to access the site with https://, it will have issues too

Yes, we store absolute urls to the image but we're finding a way to store images using relative paths instead. However, we have a mixed feeling about using relative paths.

Some sites just wouldn't work with relative paths unfortunately.
·
Monday, 18 January 2016 22:59
·
0 Likes
·
0 Votes
·
0 Comments
·
OK regarding my 1st remark.

For the 2d one, I don't understand your sentence (2d part of it):
Mark wrote:
Yes, we store absolute urls to the image but we're finding a way to store images using relative paths instead.

And Joomla uses relative paths for images in articles, so why may it be an issue if EasyBlog does too?
·
Monday, 18 January 2016 23:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Joomla uses relative urls but it can be configured to use absolute urls in TINYMCE settings. It will have lots of issues when it comes to RSS feeds and external items as these items needs to use absolute paths.
·
Tuesday, 19 January 2016 02:23
·
0 Likes
·
0 Votes
·
0 Comments
·
OK, I'll stop wasting your time with my questions

Anyway it is working as it is now, with a few drawbacks that seem to have their reasons
·
Tuesday, 19 January 2016 02:47
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem We'll see what we can do about this in the future
·
Tuesday, 19 January 2016 11:06
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post