Has anyone else experienced problems with RSS Simple Pie when upgrading to 1.11.4?
I have an RSS Simple Pie tag that aggregates the following feeds:
1. ;http://www.mydomain.com/feeds/news_fp.rss
2. ;http://www.mydomain.com/forums/index.ph ... 1;limit=16'
The first feed is from the CMSMS news module, the second one is from a Simple Machines Forum installation which is integrated with my CMSMS site.
Both feeds included in the "feeds" parameter, comma separated.
After upgrading, the first feed is being parsed and displayed correctly, but the second feed is not working.
Initally the page was failing to load correctly. After researching the forum, I guessed this might be a Smarty3 issue with the URL parameters, so I backticked the second feed. The tag now returns correctly, and the page renders, but only items from the first feed are displayed; the second feed generates nothing in the template output.
Has anyone else experienced this problem, or can anyone offer any advice, please?
[solved] 1.11.4 upgrade and RSS Simple Pie problem
Re: [solved] 1.11.4 upgrade and RSS Simple Pie problem
I discovered that the backticks were a red herring and not necessary.
The cause of my problem was the RSS Simple Pie template used to render my feeds.
A section of {php}{/php} code that I was using to do a regex match inside my template no longer works under 1.11.4 and prevents the page from loading.
I fixed this by replacing my existing {php} code with Damiano Venturin's preg_match plugin:
http://www.venturin.net/2012/01/17/smar ... ch-plugin/
This works using smarty code, and allows the template to render successfully.
I assume the root cause of this problem is the syntax changes imposed by Smarty3?
The cause of my problem was the RSS Simple Pie template used to render my feeds.
A section of {php}{/php} code that I was using to do a regex match inside my template no longer works under 1.11.4 and prevents the page from loading.
I fixed this by replacing my existing {php} code with Damiano Venturin's preg_match plugin:
http://www.venturin.net/2012/01/17/smar ... ch-plugin/
This works using smarty code, and allows the template to render successfully.
I assume the root cause of this problem is the syntax changes imposed by Smarty3?
