The last few hours were a bit of a journey… trying to find a WordPress related-posts plugin that didn’t need the database’s wp_posts table to be in MyISAM isn’t an easy task.
I did finally find one, though it’s got it’s own mix of pros and cons to it. It’s called nrelate. I’ll assume that if you made your way here, you’ve spent some time looking at other plugins (you know, the ones that won’t work with your InnoDB tables), so I’ll break down a few of the differences you’ll find, because nrelate is drastically different in some ways.
nrelate vs YARPP and Contextual Related Posts
How they work:
nrelate is essentially a service that runs on another server. The nrelate plugin that you install inserts some javascript into your pages, and sends a request to the nrelate servers asking them to scan your website. Over the course of a few hours, the nrelate servers visit/index your website, put the information together, and come up with “related posts” for your pages. From then on, when a visitor loads your webpage the javascript on your pages has the visitors browser pull your “related posts” from nrelate’s servers. That might all sound a bit complicated, but in many ways it’s similar to Adsense (for those who run an Adsense plugin). Except that instead of displaying ads, it’s displaying your related posts.
YARPP and CRP on the other hand are typical plugins. They reside on your own server, literally scan your database, do their fancy magic on your web host, and provide the “related posts” via the plugin itself.
I won’t go into all the differences, but I’ll give a few pros and cons to dump out some info while trying to help you decide whether it’s worth a look.
Just before I get started, note that if you’re using CRP it will work with InnoDB as long as you’re using MySQL 5.6 or higher (version 5.6.4 supports the FULLTEXT search in InnoDB that’s been keeping these related posts plugins from working). In fact, looking at the php it looks like if you’re using MySQL 5.6 or higher, the plugin will just go on ahead and convert your wp_posts table to InnoDB. And if you’re using an earlier version of MySQL, it will go ahead and convert your wp_posts table to MyISAM.
All without telling you.
Pretty ballzy imo.
continue reading…
Recent Comments