a

Maurizio,

This is caused by an HTML error in your code- check the widget block right above the slide show:

<pre><a href="https://blucode.com/?cat=6&paged=4">PRODUCTIONS | YOUTUBE<a href="https://blucode.com/?cat=6&paged=5"> ?</pre>
<pre id="spazio">BLUCODE LAP<a href="https://blucode.com/?cat=6&paged=6"> ::</pre>

<pre id="spazio">EVENT<a href="https://blucode.com/?cat=6&paged=7"> ::</pre>
<pre id="spazio">PERFORMANCE<a href="https://blucode.com/?cat=6&paged=8"> ::</pre>
<pre id="spazio">RUMINANZE?<a href="https://blucode.com/?cat=6&paged=3"> ::</pre>
<pre>ARES<a href="https://blucode.com/?cat=6&paged=2"></pre>
<pre>TREAS<a href="https://blucode.com/?cat=6"></pre>
<pre>6 PARAMITA</pre>

None of those links (<a href=...) have closing tags (</a>). That’s what’s causing your problem.

Hi Bruce,

I just checked your site- what is the feed URL you’re using for the slide show? Is it different then this one?
https://www.brasscomics.com/feed/

The RSS pulled by the proxy script for this plugin is showing an rss version of 0.92, where the link above shows rss 2.0. I think that might be the root of the problem.

Either should technically work though- I’d like to run some tests with the other URL if you wouldn’t mind providing it.

Thanks!

Nnlee,

I’m not sure why you’re still having trouble- I specifically tested the NASA daily feed with the plugin in all major browsers and had no trouble at all. If you’re still interested in using my plugin, I would be happy to look into this further with you.

Please bare in mind, this plug-in isn’t even a week old yet. ??

Thanks!

Hi Handig,

I think the issue here was caused by that feed having broken images in it. When I was last testing it, all three of the images were broken- though earlier one was functional.

I have made changes to the code to detect broken images on the fly, and remove them from the slide show. This should resolve this issue.

Please let me know if you have any trouble with the new version. Thanks!

Hi Maurizio,

Version 1.0.7 has just been released. Please let me know if this helps!

Maurizio,

This is caused by another server error: Your hosting provider does not support fopen accessing external files. I will add a curl alternative for you in the next version, but I do not know if your hosting provider allows you to use the curl PHP module.

<br />
<b>Warning</b>:  fopen() [<a href='function.fopen'>function.fopen</a>]: URL file-access is disabled in the server configuration in <b>/usr/local/psa/home/vhosts/blucode.com/httpdocs/wp-content/plugins/anyfeed-slideshow/anyfeed_slideshow.php</b> on line <b>40</b><br />
<br />
<b>Warning</b>:  fopen(https://vimeo.com/blucodelap/subscriptions/videos/rss) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: no suitable wrapper could be found in <b>/usr/local/psa/home/vhosts/blucode.com/httpdocs/wp-content/plugins/anyfeed-slideshow/anyfeed_slideshow.php</b> on line <b>40</b><br />
Failed to open urlhttps://vimeo.com/blucodelap/subscriptions/videos/rss

Hi Maurizio,

I just looked at that link and saw the following error:

<br />
<b>Warning</b>:  fopen(feed://vimeo.com/blucodelap/subscriptions/videos/rss) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: No such file or directory in <b>/usr/local/psa/home/vhosts/blucode.com/httpdocs/wp-content/plugins/anyfeed-slideshow/anyfeed_slideshow.php</b> on line <b>40</b><br />
Failed to open urlfeed://vimeo.com/blucodelap/subscriptions/videos/rss

Make sure you change the URL to https:// instead of feed://!

Neal,

The plug-in is working, though there are a few tweaks that need to be made to ensure it works for all feeds.

I received your email, and found the problem you’re experiencing; That feed only has three images, and two of them are broken. As I did not include error correction to account for broken images, it hangs indefinitely waiting for those images to load.

I am re-writing the image caching engine to correct this problem; Your issue should be resolved in version 1.0.7.

Thanks for the detailed report!

Hi Maurizio,

It looks like one of your other plugins has a Javascript Error, which stops browsers from continuing to execute Javascript on those pages. The error is:

rot is undefined
https://blucode.com/wp-content/themes/blucodelap/sliders/scripts/slider_freshcubes.js
Line 156

Could you try disabling that plug-in, just to see if that solves this problem?

Thanks!

Hello Handig,

I will look into this in more detail later this morning, and report back to you when I’ve determined what’s going on here. Expect a release later today that resolves this issue.

Thanks for reporting this issue! Without folks like you, WordPress plug-ins would be doomed to forever be buggy and broken. ??

Hi Handig,

That sounds like a great feature! I will add that to planned development for the 1.1 release (first, I want to work out all or at least most of the bugs).

Thank you for the feedback!

Maurizio,

This issue is very frustrating to troubleshoot blind. Is there any way you could install the plugin on a dev blog, or leave it up on your main blog for a short while so I can more closely inspect the problem on your blog?

Thanks!

Hi Maurizio,

I have just submitted version 1.0.6, which should resolve the issues you’re having. Please let me know if you run into any more trouble!

Thanks!

Maurizio,

I think the problem here is that your WordPress blog is set to use a different url then the one you’re accessing it from. This is a limitation of JavaScript.

Presently, the plug-in loads the xml proxy from wherever WordPress says the URL should be, which means if you access your blog from https://www.url.com and wordpress has just url.com listed, it won’t load.

I will push a new version in which that has been fixed. That should *fingers crossed!* be the last issue. ??

Thanks for sticking with me on this!

Hi Maurizio,

Could you do me a favor, and see if you see the feed on this page:
https://home.tixen.net/devblog

I think I have one final thing nailed down, but I want to make sure.

Hi Maurizio,

I just noticed the cause of your problem. I’m so sorry I didn’t catch it before!

use https:// instead of feed://, and it should work (I just tested it myself on my dev install).

Sorry for running you through hoops!

Hi Maurizio,

I just added version 1.0.5 to the system, which should fix your last bug. ??

Thanks again for all your help!