Support » Plugin: Yet Another Related Posts Plugin (YARPP) » [Plugin: Yet Another Related Posts Plugin] No related posts When Post Published or Updated

Viewing 15 replies - 16 through 30 (of 37 total)
  • This is a page with no related posts however, if the YARPP is flushed, there will be related posts, as threshold is at 3, so all related PDF articles would come up.

    W3TC uses the cache.php file included with WordPress, which is poor compared to Ryan Boren’s plugin.

    I was solving a related post refresh problem in the post loop, but you are using the sidebar widget, so the solution is different. I may have solved that problem, but I’ll need you to test it to be sure.

    In the cache-postmeta.php file inside the clear function I added the following lines starting at line 152:

    wp_cache_delete('is_cached_'.$id, 'yarpp');

    I also updated the fixed file link below to now include class-cache.php, cache-tables.php, and cache-postmeta.php. This fix is for YARPP Version 3.5.1.

    Let me know if this works for you.

    Nop, still no luck. The test page with the no related posts ( still doesn’t show no results.
    What I find really amusing is that on Mitcho’s slides he says whenever Yarpp is called other than with the template, those calls are not cached. Then why the related at the bottom of the post doesn’t show up, as they are called through custom code? (this is the call <?php if (function_exists(‘related_posts’))related_posts(array(‘limit’ => 2,’template’=> ‘yarpp-fim-post.php’)); ?>)

    I will have to look at this later to see if I can hunt down and test the sidebar widget code to refresh it. I’ll post the solution when it is ready.

    My solution at the moment is to bypass the cache of YARPP and let W3TC and memcache to cache the DB queries. Certainly not the best solution, but yet, it is working.

    I’ve stopped using YARPP altogether because it adds a FULLTEXT KEY to the posts table if the storage engine is MyISAM. MySQL now uses InnoDB as the default storage engine, because it is so much faster and more efficient, but it doesn’t allow for the inefficient FULLTEXT KEY to be used. Since I have switched everything over to InnoDB I am writing a new related posts plugin that will replicate the great results YARPP gets, without the horrible overhead, issues with the cache, and can be used with either the InnoDB or MyISAM storage engine.

    I will only be releasing the new plugin on my blog when it is completed.

    That is awesome, looking forward to see your plugin =D
    nRelate is also a great inspiration for many blogs, as it provides really awesome customization and outsources the relatedness.

    Even running with no cache the plugin still runs and yet it doesn’t show any results!
    You can guess in my server graph when were the two moments I turned on YARPP with no cache.

    Can’t wait to see your work Todd.

    This plugin is not working, some related posts shows and some not. RSS ‘related posts’ lost too.

    This plugin seems abandoned.

    My Related posts in the RSS is working canal blues. Yet most of the wordpress related post don’t because of some bad cache behavior.
    I recommend nRelate meanwhile Todd doesn’t releases a similar plugin but up to date.

    Thanks for all the details here. @dentvil: if you’re using an aggressive page cache and/or query cache, bypassing the YARPP cache is indeed reasonable. I assume you figured out how you can specify this using YARPP_CACHE_TYPE?

    Then why the related at the bottom of the post doesn’t show up, as they are called through custom code? (this is the call <?php if (function_exists(‘related_posts’))related_posts(array(‘limit’ => 2,’template’=> ‘yarpp-fim-post.php’)); ?>)

    It does cache this, because it’s actually smarter than just not caching if you specify options. Only options which change the calculation of the algorithm make it bypass the cache. If it’s just limiting the number of results or using another template, it’ll still cache the regular results.

    @toddlahman, thanks for your detailed suggestions for fixing this. I hope to integrate your changes quickly. The link you had before seems down. Could you summarize what you changed in those three files?

    Finally, for all of you: there was an independent issue with non-MyISAM tables, which may be affecting some of you. This is fixed in the latest dev version. I encourage you to check it out:

    I looked through all my code to figure out what all changes are necessary to fix the incompatibility with object caching, and I’ve made the changes in 3.5.2b3. Please test it and let me know if it fixes your issues. Hopefully it does. Thanks again!

    Thanks for the effort mitcho. I have tried and it seems the issue is still there. I can reproduce it by flushing the cache with experiments, clearing all caches with w3tc and then trying to display the page as non-admin.
    It helps, but doesn’t solve entirely, if I flush YARPPs cache, build it, then clear the w3tc cache. This way, most posts have related articles, but some don’t (random, no pattern recognized).

    What apparently has been fixed it the call for both related, where one would show related posts and another wouldn’t. Here is a page in which you can check it out (right sidebar and before breadcrumbs Como usar Google+.

    Thanks for sharing and trying anyway.

    @dentvii, so previously having two displays was broken for you? And that’s fixed now? Well, that’s an improvement at least. If that’s true, and there are other bugs which have been fixed, so I may push out this release. As long as it hasn’t made anything worse. 🙂

    I’m going to have to set up an environment with W3TC with the appropriate options. Do you just use W3TC or is W3TC interacting with something like XCache or APC or memcached?

    @mitcho I don’t really know if it is fixed now due to your change or due to some changes I had made on W3TC. I was previously using W3TC with page cache on Memcached, but it wasn’t really caching for some bug, so YARPP was just showing bellow the post, not on the sidebar (lower in code, 2nd call). Now it is serving disk cache for pages and everything else is memcached.

    So I guess it is fixed, but can’t really tell cause I changed other variables.
    Page cache is disk
    Others – Memcached.

Viewing 15 replies - 16 through 30 (of 37 total)
  • The topic ‘[Plugin: Yet Another Related Posts Plugin] No related posts When Post Published or Updated’ is closed to new replies.