@na3s – what exactly did you have to do to get beta 3 to work? The database schema between beta 2 and beta 3 actually should be exactly the same… :/
Thread Starter
na3s
(@na3s)
None of the beta’s have ever worked for me! I remember at one point it did work, at the very beginning. but then things started going haywire, the pool wouldn’t load, errors, and YARPP not returning any posts. How do I uninstall YARPP So I can reinstall!!!! I do not have access to phpmyadmin on this server and I reallllly don’t feel like navigating sql in SSH. 🙂
Thread Starter
na3s
(@na3s)
I did go back and forth between the stable build and the beta… This is possibly what caused DB corruption.
@na3s – there isn’t really any “corruption” that’s possible… what happens if you have the “build cache on the fly” option on? It’s at the very bottom of the options… do you get related posts then?
Thread Starter
na3s
(@na3s)
Hey mitcho, well not corruption, just errors. See below. Any uninstall in the near future? Client is on a tough server that doesn’t allow me to connect to SSH and doesn’t have PhpMyAdmin… should I start writing an uninstall?
[Wed Feb 18 10:08:29 2009] [error] [client 209.125.40.68] WordPress database error Duplicate key name ‘yarpp_title’ for query ALTER TABLE wp_5knalt_posts ADD FULLTEXT yarpp_title ( post_title) made by require_once, do_action, call_user_func_array, yarpp_upgrade_check, referer: http://thenatureofexistence.com/wp-login.php?redirect_to=http%3A%2F%2Fthenatureofexistence.com%2Fwp-admin%2Fedit-pages.php
[Wed Feb 18 10:08:29 2009] [error] [client 209.125.40.68] WordPress database error Duplicate key name ‘yarpp_content’ for query ALTER TABLE wp_5knalt_posts ADD FULLTEXT yarpp_content ( post_content) made by require_once, do_action, call_user_func_array, yarpp_upgrade_check, referer: http://thenatureofexistence.com/wp-login.php?redirect_to=http%3A%2F%2Fthenatureofexistence.com%2Fwp-admin%2Fedit-pages.php
I was having the same problem with with the YARRP database error message. I have corrected the problem on my sites and this may help others who are struggling with the same error.
1. Are you using an alternate prefix in your MySQL database (something other than wp_?)
2. If so, check to see if these two files: (prefix)_yarrp_keyword_Cache
and (prefix)_yarrp_related_Cache have different file prefixes (example: cg_yarrp_keyword_cache and wp_yarrp_related_cache) in MySQL.
In my case, the Keyword Cache had my custom prefix and the Related Cache had the wp_ prefix.
I renamed the Related Cache file (changed the wp_ prefix to match my Keyword Cache prefix and all is working fine.
I hope this helps someone out there. I’m just glad to have the “GREAT” tool working on all my sites.
Mike Gerow
DailyKnowledgeTree.com
@mginformatics – Mike, thank you so much for sharing your experience! I know there was an earlier beta with this type of bug, though I’m not sure if this is the same issue that @na3s is having, though…
Thread Starter
na3s
(@na3s)
Hmmm… What should I do mitcho? My deadline is rapidly approaching. Guess I’m going to write up an uninstall function for ya, in my opinion, every plug-in needs one. I’ll reply if I have any questions.
I personally think these errors occured from some backwards compatibility and the fact that I was going back and forth between plugins, it is obviously an edge case scenario. I am using the most recent version, and problem still occurs. If you get any ideas of what could help, let me know.
I have the same problem. And I can’t fix it no matter what I try. I’ve tried deleting the plugin, deleting the databases for yarpp, doing all of it over and over again and it still gives me the database error. It worked fine, for about an hour after I installed it, then it went loco. It could be about that “magic button” I pressed… I have no idea what it did, to be honest. I just felt like clicking it… though it worked fine even after that… it just stopped working at some random point… I guess I was modifying the template to my needs when it happened. I’m using beta 6. What should I do, how could I get rid of the problem?
Or does it literally mean it can’t be fixed? 😀
@ragnaripea – what magic button is this?
There is an issue with some “could not be fixed” errors, although if YARPP is displaying related posts for you correctly, there is no real issue… for some reason sometimes it can’t detect that the database setup is correct.
What exactly is the error text that you get?
