• Resolved ulicgn

    (@ulicgn)


    Hi,

    There is a problem with the caching – I get cache entries in wp_options for every distinct user!

    What i expected:
    if a feed is displayed via shortcode, there should be one transient cache entry for this feed for as long as the “refresh” parameter is set.

    What really happens:
    multiple transient cache entries found in wp-options table for every individual user who requested the page where the shortcode widget is placed.

    Background info:
    i am using the feedzy widget to display a feed without importing it. The shortcode I used is:

    feedzy-rss feeds="....NONPUBLIC-URL...." refresh="10_mins" max="1" feed_title="no" summary="yes" meta="" summarylength="150" thumb="no" error_empty=""

    The feed is a notification RSS which is empty most of the time and has one or two items occasionally. By using error_empty I could manage to display nothing at all if the feed is empty, which is great. ( Although there is a useless empty ul /ul pair ). If there are items in the feed, the feed content shows up. Great!

    However I was wondering why I was seeing different things in different browsers when testing. It turned out that feedzy obviously creates _transient_feed_ items in wp-options for every user/browser, instead of caching a feed globally.

    I would accept a cached item for every combination of shortcode parameters, but it seems as if you use additional user or browser data like cookies and other stuff for calculating the cache ID.

    This is not only inefficient, but also it leads to an unhealthy growth of the options table …

    Regards
    Ulrich

    • This topic was modified 2 years, 3 months ago by ulicgn.
    • This topic was modified 2 years, 3 months ago by ulicgn.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @ulicgn,

    Thanks for choosing Feedzy and sorry for the delayed reply!

    We were able to replicate this behaviour and we’ve forwarded a question to our developers to see if this is the desired behaviour. We’ll come back with a message once we have an update about this.

    Thank you!

    Thread Starter ulicgn

    (@ulicgn)

    Thanks for checking my report. Let me add that , in addition to clogging the wp_options table, this behaviour could lead to being banned from requesting a feed , because ( on a busy site with many users) the source feed will be fetched from the source many times instead just once per refresh period. Also the load time of pages containing the feed will be delayed if the feed is requested from the source for every user individually….
    Regards
    UliCGN

    • This reply was modified 2 years, 3 months ago by ulicgn.
    Plugin Support Vytis

    (@bvytis)

    Thank you @ulicgn,

    We’re still investigating the problem on our end.

    Plugin Support Vytis

    (@bvytis)

    Hi @ulicgn,

    This issue has been fixed with the recent updates. I’m closing the issue but please feel free to comment again or create a new thread if you’re still facing it.

    Thank you!

    Thread Starter ulicgn

    (@ulicgn)

    @bvytis Yes, I followed the issue on github – thanks for the improvement and for letting me know here. I updated to the recend version yesterday. Actually , right now we don’t have any transient entries in the options table, but the feed that we display is currently empty. I will keep an eye on it during the next couple of days. Thanks and best regards,

    Uli

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Caching for widget feeds does not work efficiently’ is closed to new replies.