By Chris Chase on Friday, 12 May 2017
Posted in General
Replies 5
Likes 0
Views 402
Votes 0
Hello,

The RSS feed on the catalysttg.com web page is pulling blog images, but their WP Plugin that pulls from the RSS feed and builds posts isn't pulling them. Nothing has changed on their end but they are going to check with the developer of the plugin (WP Robot).

That said, Anthony pointed out that the images in the RSS feed are loading without http:.

If you look at the source code, the link to the image is: href="//jc.catalysttg.com/images/easyblog_shared/May_2017/5-5-17/get_yourself_a_career_in_the_cloud_400.jpg"

We think that might be causing the conflict, but we're not sure.

Catalyst's RSS Feed URL is: http://jc.catalysttg.com/index.php?option=com_easyblog&view=latest&format=feed&type=rss

Thanks,
- Richard
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

The reason why we populate these image link without http protocol is because some of the site might be use https , if you view this following RSS feed link on your Firefox browser :
http://jc.catalysttg.com/index.php?option=com_easyblog&view=latest&format=feed&type=rss

The browser should able to read those image and populate the image on the feed.

Regarding with your current issue, is it when you trying to fetch those feed from Easyblog RSS feed URL, it unable to show the image on the feed?
·
Saturday, 13 May 2017 10:36
·
0 Likes
·
0 Votes
·
0 Comments
·
This breaks some RSS feed aggregators, namely that pull the RSS feed into other blogs like on WordPress. Is there a solution around it or a way to enforce http vs https?
·
Monday, 15 May 2017 21:30
·
0 Likes
·
0 Votes
·
0 Comments
·
In EasyBlog 5.0, we use protocol dependent as the uri to avoid conflicts between http / https. In EasyBlog 5.1, you may now configure EasyBlog to use relative urls to store the content instead of absolute path.
·
Monday, 15 May 2017 21:40
·
0 Likes
·
0 Votes
·
0 Comments
·
Is there nothing we can do? It's breaking the RSS feed capture.
·
Tuesday, 16 May 2017 21:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, because it already stored this attribute href="// into database.

The only way I can think of is :

1. Run a PHP script update all the existing image path from your database href="//site.com/images/... to href="/images/... data.

2. Truncate this `#__easyblog_revisions` table data
3. Regenerate all the existing blog content into this `#__easyblog_revisions` revision data
4. Turn on this "Use relative path" setting from backend > Setting > media , once you turn on this, it will only affect the new post which included the image path, so it will store it as href="/images/....

I have a question for this, may i know which editor you use ?

And how many blog post you have?

If you would like to do this, it would be best if you can setup a staging site of this, if everything work correctly then only proceed this on your live site.
·
Wednesday, 17 May 2017 12:12
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post