Feed loading really slow (Even though it's cached)

Ok. Ill check it out

Oh, found another possible bug, when uninstalling the plugin, it doesn’t delete the feeds or the feed items from the db. Is that intentional?

yeah…I’ll fix this

Could you please make couple of lines summary of the best practice – “How to CACHE feeds”?

Maybe something like?

1) fetch&cache RSS-feeds by CRON script instead of letting my web visitors to wait for any fetching. [OUTPUT: compilation-RSS.xml on my server]

2) And then just “parse&echo” this static complation-RSS.xml on my server for web visitors. [OUTPUT: Items of compilation-RSS parsed&displayed on WordPress pages according to user settings]

The general caching can be then done by dedicated plugins such as “W3 Total Cache”.

(currently getting regularly “server timeout”-error when fetching feeds from multiple sources; I could add server-timeout-value but it would not shorten the time that user needs to wait; and as principal – you should not let user/search engine wait anything but just printout pages he/she wants to see)

The way he is doing it in the beta is actually quite robust. Patience, grasshoppa!

ok…try this…this should fix a) the html issue, b) the deleting entries upon uninstall, and c) the double entries

https://dl.dropboxusercontent.com/u/3132388/beta/wp-rss-multi-importer.zip

A and C confirmed. I’m willing to take your word for B atm ??

2 things… One of which is mainly a feature request:

Are the feeds being pulled and displayed from the DB now as opposed to pinging the actual feeds?

I would muchly appreciate it if on the social stuff you would add a google+1. ??

Edit: Just found another thing… In limited HTML, could you add support for lists?

Thanks much. God this is just getting better and better and better ??

the feeds are being pulled into the database as often as your schedule it with the cron…if it’s in the db when someone goes to the site, then it will be displayed.

google +1 is already added to the plugin (I just tested it and it works).

You can always edit the excerpt_functions.php file and find the two places where you can add whatever html you want to allow. That way you can customize it for yourself (of course, this isn’t in the core, so you’d have to do that each time). The only other way I can handle this (where people want their own unique set of html they want (or don’t want) is to have a text box where you enter whatever you to allow…which I may do.

Yeah, I didn’t want to do that simply because of upgrading woes.

G+ is there? Oh. Derp. Might wanna add a mention of it in the shortcode settings page ??

Thanks much

Text box for html elements would be bouse. ??

Looks out generally very good! I would have couple of questions:

1. AUTHOR OF ITEM
It seems that Author of item is not working in this version (https://www.ads-software.com/support/topic/items-author-not-displayed-author-attribute-isnt-parsed-at-all?replies=12). Could the Author-fix be added here too?

1.1. Beta version OK to use?
Indeed does it make sense to start to use this Beta-version? Yes it does in that sense that scheduled feed-fetching is obligatory but how it will be updated and is it compatible with upcoming new version of official version? Is Beta its own version branch or same as public one and we will see these changes as updates in couple of days in the official public plugin?

2. META-information
Could list of feeds include information about 1) the timestamp when the specific feed is fetched last time, and 2) number of total items and number of items that were fetched to db this time. (Indeed, how does the script notice now if an item is fetched already in db or not?)

Alternatively/in addition, could each Item include information about fetching time. So that you could see when it is fetched – especially good for “archived” items that have disappeared already from original feed.

I think this kind of META-information would be user friendly for plugin-administrator. You would get some feedback of fetching process and knowledge that it works properly.

you can update the beta plugin here..I think this fixes the author issue

https://dl.dropboxusercontent.com/u/3132388/beta/wp-rss-multi-importer.zip

the beta version is still beta (2.68) – once it become official it will move to 2.70 you yours will be updated accordingly.

I’ll consider the request about the meta information – seems like useful information. Thanks.

Great thank you very much – “author” works now OK!!

Probably unnecessary to remind but could be good to update rss_multi_importer_widget.php for 2.70 too, I think it still fetches feeds by every page load and if used as element displayed on every page it is especially heavily loaded.

The widget in 2.70 is pulling from the database, and yes it does that by every page load (just like any page or post on wordpress). If it is going slow, the next step is to use a wordpress caching plugin.

OK – 2.70 sounds really great, waiting forward!

Ok, utilizing the latest beta that you just provided me, I have been able to narrow the source of the issue to this feed:

https://feeds.feedburner.com/Zero-kNews (the original source feed is: https://zero-k.info/News)

If I remove it, the page with the shortcode on it loads all feeds instantly. If I re-add it, everything gets really slow, including pagination, unless that page doesn’t have one of the items from that feed on it.

This feed has 75 items on it, and I wouldn’t think that that would cause an issue because I have the plugin to only grab the last 20.

I was under the impression that the content of the feed was being cached as well in the db (cached by way of “auto-fetch on a schedule). Is that not the case? Because it seems to me that the feed being slow shouldn’t matter to the plugin if all the data it needs is in the local wp database.

I feel like I’m missing a fundamental point here.

I could use autoposting, but then it wouldn’t link back to the source automagically when clicking on the title, and a bunch of other behavior that I want the shortcode for, and if I remove a feed it could get messy, etc etc.

Another point of contention, is that I’m running most of these feeds through feedburner in an attempt to have google sort out any issues caused by the feeds themselves. What is so special about this feed?