SP developer

Hi ade11,
thanks for the detailed response. I like the idea of a configurable cache path and will add that in the next release. Also thanks for the heads up on the cache delete var. I’ll take a look.

Since this is a an urgent request for your client I will see if I can get to it this evening. A donation would be greatly appreciated. ??

We can take this conversation off of the forumif you like. Use the email address in the SP Admin support tab.

Best regards,
SP Developer.

Hi ade11,
Have you observed a problem with multisite wp? The cache dir is based on the wp installation path. Also, the cached files are unique for each feed url. If the feed url is the exact same, then the cache filename would be the same. Please post your site url.

Best regards,
SP Developer

Hi ade11,
I think I can get your request into the next release.

Thanks for bringing this up.

Best regards,
SP Developer

Hi sime0n,
I just delivered the div feature for the article body in version 1.0.21.

Best Regards,
SP Developer

Hi sime0n,
I just tried to reproduce your char length issue and was unable to do so.

I wonder if your cache dir permissions are set correctly? Perhaps SP was unable to delete the cache? How did you install SP? Can you contact me directly via the address in the admin help tab. Send me the url of your site and the SP version along with your exact config setting for the display tab.

Thanks,
SP Developer

Hi sime0n,
I’ll check on the article char limit this evening. Thanks for the heads up.

Regarding the feature request, I am actually currently working on that and about 1/2 way done. ?? The articles will be in their own divs and we’ll be able to set the formatting just like the titles can be set.

Best regards,
SP Developer

Hi slimandslam,
I have delivered this fix into the latest version, 1.0.19.

Best Regards,
SP Developer

The output to the page is based on the feeds. Articles are pulled from each feed and then displayed on the page. I understand your idea and think it is a good one. The problem that I see is that splitting individual articles out of the context of the publishers feed may violate the publishers terms of use and copyright.

Syndicate Press strongly supports publishers copyright and is specifically designed to protect the integrity of the publishers feed while making the feed content fit in with the look and feel of the site the feed is being syndicated on.

Perhaps there is a way to satisfy your idea and make sure that we protect the publishers feed. I think you have a good idea, but lets keep talking about it and evolve it a bit.

Looking forward to hearing more ideas on this topic…

Best regards,
SP Developer

Thanks,
I’ll put this on the todo list.

Best regards,
SP Developer

Hi theduke19,
thanks for providing a great description of the issue and including the config info. That helps a lot.

Looks like the issue is that the words ‘pro’ and ‘eagles’ are matchings those words in at least 2 of your feeds. The words in the feedList will match the feed if the word is in the feed name OR in the feed url.

Try giving each feed a unique name, then use the unique names in the feedlist.

The reason that the matching works like it does is because it makes grouping feeds via a common word very easy.

Best regards,
SP Developer

I just added this feature and it is now part of the 1.0.18 release.

Best Regards,
SP Developer

Hi rvturnage,
right now, this is not supported in the short-codes.

This is a great feature idea and I will put it on the todo list. I think I can get this one taken care of pretty quickly.

Best Regards,
SP Developer

Hi thob,
yes, the shortcodes work in a standard Text widget. Just put in the sp# short-code just like you would do on a page or a post.

Best Regards,
SP Developer

Hi thob,
will you post a url to an rss feed that has enclosures embedded in it?

Thanks,
SP Developer

It is important to note that the SP plugin caches the feed article content on the server, but resources such as feed images and video/etc… would be loaded by the client browser. I think wthis could be accompdated by placing the enclosure link into either the pages header with a link element set to prefetch, or simply in the page body with a link set to prefetch.

Since SP is a server side aggregator and not a client side tool, the link prefetch approach may be a viable way to support enclosures.