500 Error installing 2.3

I did some investigation (prior to finding this support topic) and found similar results with commenting out lines 11 to 13 of taxonomy.php. I took it a little further and added a var_dump($wp_taxonomies) after the assignment lines to see if the assignments were working or not.

With this additional line in the code, it magically started working properly (no 500 errors) with none of the lines commented out. I tried replacing this with an echo “Test” (also with a couple other strings) to see if just outputting some text resolved the issue but I was back to the 500 errors.

I also tried changing this to var_dump(“”) which also seems to resolve the problem… if you don’t mind the string(0) “” at the top of every page.

I have not yet tried moving the var_dump line elsewhere.

I am using PHP version 5.1.5 and MySQL 4.1.20 on Apache 2.0.52 with eHosting.ca.

After doing some google searches I stumbled onto the fact that output_buffering is set to 4096 on my host and wondering if this is related (I think var_dump may interact with this somehow and resolves the issue).

I am reasonably good at the programming side but don’t know much about configuration. I think I can override the php.ini setting for output_buffering in a .htaccess file but could use some direction as to how to do this so I can test if this resolves the issue.

I know very few people who can run v2.3. I can’t upgrade ANY of my blogs past v2.2.2 becuase of this 500 Server error. And that’s on different server configs.

That is such nonsense. I JUST upgraded 3 blogs on 3 different hosts to 2.3.2 with NO ill effects. I JUST installed a fresh copy of 2.3.2 to another host.

This is a support site, not a “hey my wordpress blog kicks ass” web site. The posts here are going to reflect problems NOT successful installs and upgrades.

Some million odd ppl use wordpress, and I DONT see a million odd posts saying that their blogs are broke.

Normal people with normal hosts that provide the normal requirements dont have issues.

Ive upgraded AND/OR installed WP 2.3.2 on a small orange, godaddy, hostgator, and bluehost, ALL within the last week.

Learn to use some common sense when you write.

Hi there, i just have moved to another hosting and also have the SAME issue, they have Suhosin patch installed that blocks the taxonomy.php memory usage and generates that 500 error. Also Suhosin guys said this:

FreeBSD PHP2.5.1 version is buggy and needs to be updated to FreeBSD PHP2.5.1_2

They told me to add this lines to my .htaccess file:

zend.ze1_compatibility_mode Off
php_value memory_limit 32M

And IT WORKED!!!

I hope that this may help you.

Regards
ThePhoenixBird

OK… I had this same 500 issue with upgrading from 2.2.x to 2.3.x before, and got so frustrated, I dropped it and stayed 2.2.x

So here I am again with a new build of 2.3.3 and I still cannot get either an upgrade or raw install to work.

I have expanded the memory requirements for php via htaccess, which does nothing. I still get the 500 error.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

# php_flag display_errors on
php_value memory_limit 16M

As per phpinfo(), my server is running:

FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE #0:

mySQL:

Server version: 4.0.26

As others have had, I have no access to the raw log files, as this is a shared hosting account. The logs I see are just access logs, and give no reason as to the error.

Now, I realize this is a server issue, as my local Macintosh displays the correct screens via HyperEdit, (macs render php almost natively) but what could possibly be preventing it from working correctly on a unix server? Does mySQL have to be a newer version?

Any help/guidance is appreciated, as I would like to keep up with the most current builds. I have a number of other websites that need to be taken to current builds.

#UPDATE:

ThePhoenixBird’s solution above works. In my first try of it, I did not bump the memory to 32M, but left it at 16M, which in turn I still got the same error.

So, if you are running on Linux and getting these errors, I would definitely try inserting

zend.ze1_compatibility_mode Off
php_value memory_limit 32M

into your .htaccess file and see if that resolves it. It appears to have solved my issues.

PhoenixBird’s solution does work for me too, but there was a mistake in the .hraccess code. The “zend.ze1_compatibility_mode” directive is a PHP Flag. Therefore, you need to specify the “php_flag” instruction before it.

The proper .htaccess directives should look like:

php_flag zend.ze1_compatibility_mode Off
php_value memory_limit 32M

I’ve been struggling with the .htaccess options with no success. In fact adding the two lines exactly as they are listed above was throwing “500 Internal Server Error” even for something as simple as phpinfo()!

The two lines to be added to .htaccess should be:

php_value memory_limit 32M
php_flag zend.ze1_compatibility_mode Off

OldWebGeek – you’ve hit the nail on the head! :o)

Just realized that you’ve already pointed this out. I am so glad it has finally fixed the problems I was struggling with for weeks now.

That did the trick, one problem though: The wordpress install appended #BEGIN WordPress onto the end of the last line in .htaccess, breaking a php_value line and resulting in more 500’s, which might show in error.log as database object missing errors – on a fresh install with blank db tables, nothing has been populated yet.

Kent, can you test this fix and see if it sorts you out, then the thread can be declared solved. MichaelH, what needs to be done to get a patch into WordPress that updates the .htaccess write from:
#BEGIN WordPress

#END WordPress

to (at least):

#BEGIN WordPress
php_flag zend.ze1_compatibility_mode Off

#END WordPress

?

Hi!

I found a more hackier solution that fixed it for me before I read the whole thread.
I directly edited the taconomy.php

In lines 11 to 13 I took out the (object) casts.

$wp_taxonomies['category'] = array(...);
$wp_taxonomies['post_tag'] = array(...);
$wp_taxonomies['link_category'] = array(...);

And in the function get_taxonomy( $taxonomy ) I added the (object) cast again in line 68:

return (object)$wp_taxonomies[$taxonomy];

So far I didn’t notice any errors. But I didn’t test every part of wordpress after changing. So use with caution!