Error Messages After Updating to WordPress 2.6

Should I try to re-install?

Anyone? Pretty please…

I am getting 500 errors too when I attempt to activate this plugin in WP 2.6:

https://planetozh.com/blog/my-projects/wordpress-plugin-who-sees-ads-control-adsense-display/

And yes, the current version is only for WP 2.5, but it still shouldn’t call up and 500 errors, right?

The errors are limited to the backend and do not affect the frontend at all. I’m guessing that means that the admin PHP file of the plugin causes this error. Not sure where to start looking though – a PHP error log only records PHP errors, which a 500 internal server error is not (it’s an Apache error, in this case).

Why I am adding this to this thread is that these errors not only occur when I activate the plugin, but also in similar cases as desertdiva describes:

– When I write and publish a very long post with multiple images (approx. 50 in this one case), I get a 500 error in the backend but the post is still being published – with comments and pinging switched off (default=on).

– When I then go into editing mode of that long post and hit “Save” immediately without doing any changes, I get the same 500 error.

– When I edit it again and switch the comments and pinging on, then save it, I get yet another 500 error, but the comments are now enabled for this post.

– When I write/publish/edit MUCH shorter posts, everything works smoothly.

Maybe someone has a clue where to start looking?

OK, I said pretty please – surely there are some WordPress wizards who can address this…

I’m joining in.
When I publish a new post, no problem. Editing an existing post causes an internal server error. Deactivated the plugs, same problem.
Someone found a solution yet?

I changed my theme to the default one and the problem disappeared. This is not solving a thing because I really don’t know where to begin correcting my custom theme.

desertdiva: Disable your sitemap plugin.

Basic troubleshooting steps:

1. Switch to the default theme. If the problem goes away, then it is a problem with your theme.

2. Disable all plugins. If the problem goes away, then it is a problem with your plugins. Re-enable the plugins one by one, checking for a return of the problem each time to find the problem plugin(s). Check that your plugins are all up to date.

Thanks – the Google Sitemap plugin was the culpit!

I’m getting a 404 error not found. I updated lest night and now my theme and any other page I try to go to is 404? I don’t want to lose everything that I have posted. Please somebady look at my blog and tell me what you think. junk car blog

OK I found the solution to my problem, but I’m very sure that it isn’t the same for everyone. You could try the same steps I did though, it will only do your WordPress good ??

For me, it was a corrupt database. Error 500s are always kinda hard to track and after spending hours with my hosting support (and they weren’t able to find anything), I decided to take a deep look into my database.

This is what I did.

Step 1:
– I made a complete backup of the database (export). Do this before attempting to do ANY changes. I now even do this before I install any new plugin.
– I looked through all tables in the database (wp_tables-created-by-plugins…) and found a lot of orphans. These were all from plugins that didn’t have an uninstall option (like e.g. CformsII does), so their database entries were all still there.
– In an attempt to clean up the mess a bit, I deleted every orphan table one by one, but only after double-checking that I didn’t use that plugin anymore.
– Then I looked through all rows in the wp_options table. Here also, many many plugins simply add to or change values. I again deleted all orphans here.

> The first effect was that the site loaded a lot faster. But the Backend Errors remained. So I decided to get dirty even more.

Step 2:
– I remembered having installed a Role Manager Plugin, played around with its settings, and removed it later. The plugin had of course changed the default WordPress roles.
– The field in the wp_options table is something like user_roles – I copied that to a TXT file, then I installed a fresh copy of the same WordPress version on a test domain and looked for that exact same field there, copied it also to another TXT file.
– I downloaded https://www.prestosoft.com/edp_examdiff.asp, a small Windows App that compares files. I ran both TXT files through it and sure enough, they weren’t the same.
– So I simply replaced the changed user_roles field with the original one from the fresh WP install.

> This worked for me. It may have been just the user roles alone or maybe something else as well, because I really cleaned up a lot in that database.

So my recommendation is to just look at your database and see what you can find. If you have never worked with MySQL before, just look at it and you’ll see that it’s not too hard to figure out what means what. It’s just like a spreadsheet with rows and columns. Try to remove unnecessary (orphan) tables, fields and values (carefully and always double checking), and see if it works.

Lessons learned:
1) Make regular database backups and make a backup each time before installing a new plugin
2) Keep your house tidy & clean at all times! ??

Hope this helps!