Some WordPress 2.0.5 users reporting Server 500 error
If you are part of the small minority of WP users seeing 500 error messages (or anything about 302) after upgrading to WordPress 2.0.5, listen up.
First, download this plugin, upload it to your wp-content/plugins/ directory and activate it by going to the “Plugins” menu and clicking “Activate” next to the “WordPress 2.0.5 Tuneup” listing. If you get the error message after logging in and thus cannot click the “Plugins” tab, manually type {WPDIR}/wp-admin/plugins.php into your address bar.
Second, that was my fault. Very sorry about that. This bug was reported for WordPress 2.1 on Trac, and it slipped my mind that the same change had gone into 2.0.5
The good news is that it’s a small minority of people that is affected, and the problem can be fixed with a plugin. I’m not sure if this means a version 2.0.5.1 will be coming out… I’ll discuss it with Matt and Ryan. Please let me know if the plugin fixes the issue for you, and spread the word to other affected people, if it does! If you see anyone recommending that people stay on 2.0.4, point them to this post. 2.0.4 has security issues, so staying on that version would be very foolish.
[...] Some WordPress 2.0.5 users reporting Server 500 error [...]
[...] Update2: IF you are one of the few with the 302/500 error please visit this site: http://markjaquith.wordpress.com/2006/10/28/some-wordpress-205-users-reporting-server-500-error/ [...]
[...] Nachträglich: Für einige Leute dürfte das hier sehr nützlich sein, mir hat es auch zwei Fehler weggezaubert. Du kannst deine Meinung sagen oder trackbackeren von deinem eigenen Blog. RSS 2.0 [...]
[...] Update: It has been reported that some users are facing a “Server 500 error” after upgrading. If you face this problem, you will need to install the WordPress 2.0.5 Tuneup plugin. I believe this will be fixed in the next version. [...]
Reinstalled wordpress - but I get a blank screen on the logon page(and even when I go to veiw site also). Would the above plugin fix this fault?
Is it possible to create an online form using wordpress???
[...] Some WordPress 2.0.5 users reporting Server 500 error Mark Jaquith puts in a fix if you’re getting Server 500 errors. It’s a bug that’s fixed in WP 2.1, but it also effects 2.0.5, so you’ll need the fix if it’s happening. (tags: bugs wordpress plugins) [...]
[...] WordPress 2.0.5 Release，下午昇級完後並沒有什麼特別的問題，看了看大部分是修正bug。不過在Some WordPress 2.0.5 users reporting Server 500 error提到可能發生的問題與解法。有碰到出一下聲吧，雖然我覺得他的解法好機車XD [...]
[...] Oh, and for some WordPress 2.0.5 users reporting Server 500 error after upgrading, check Mark Jaquith’s post and fix here: Some WordPress 2.0.5 users reporting Server 500 error These icons link to social bookmarking sites where readers can share and discover new web pages. [...]
[...] Downloaded the changed-file-zip from this site and upgraded to the newest version. You won’t notice anything I guess [...]
your fix worked for me, many thanks!!
[...] WordPress 2.0.5 causes a 500-Internal Server Error for some users, but Mark Jaquith has a tune-up plug-in to correct it. [...]
[...] UPDATE Steve e gli altri ragazzi di WordPress-it hanno pubblicato la traduzione, in alcuni casi pare si verifichi un errore 500 dopo l’aggiornamento, nel caso capitasse anche a voi potete installare questo plugin. [...]
Isn’t it possible to fix the bug now so that people who haven’t upgraded yet won’t be affected?
Not with the same version number. Very bad practice to change something without changing the version number.
[...] Ok, I’ve just upgraded to WordPress 2.0.5 and have switched back on the plugins and changed back to my theme (which, incidentally, I think is in need of a change) and it all seems to be working. A few people have reported some problems so I’m ready to use this plugin just in case but all being well, I’m hoping I won’t need to… RSS feed for comments on this post TrackBack URI [...]
OK. I’ve learned something. Version numbers . . .
Forgive my commentary.
But that was one hell of an issue which “slipped” your mind.
Please consider reissuing this update as opposed to only relying on a plug-in as it is the more professional and secure thing to do. WordPress should never rely on quick fixes. Microsoft implements the same strategy with Explorer and look at how many problems they constantly have with hackers and script kiddies.
This plugin worked for me, on my wordpress install (earwicker.net). Thanks.
[...] WordPress 2.0.5 released three days ago, while most of the WordPress user are now writing their blog with peace of mind, some of them are having the server 500 error. According to Mark Jaquith, it’s due to the bug that was reported for WordPress 2.1. [...]
i also got the 500 error, the plug in fixed it. thanks a lot.
[...] Falls du durch Zufall auf Seite gekommen bist weil du bei Google “WordPress 2.0.5 500 Internal Error” oder sowas eingegeben hast: ja! Bei einigen gibt es wohl ein Problem mit dem 2.0.5 Upgrade. Mark Jaquith hat allerdings ein Plug-In geschrieben, welches das Problem behebt. Es wird vermutlich kein 2.0.5.1 Update geben. Das Plug-In findet ihr auf Mark’s Homepage. [...]
I’ve upgraded mine but didn’t get server 500 error message. Is there any possibility this error will come out in the future if I’m not using this plugin?
[...] En esta nota, salida muy poco después del lanzamiento de la nueva versión de WordPress, Mark Jaquith hace referencia a un mensaje de “Server 500 error” en algunos usuarios – según él muy pocos – luego de efectuar la actualización. Para solventarlo, se pone a la disposición un plugin y los pasos para su instalación. Al parecer el error se le deslizó a Mark al confundir un bug reportado en la futura versión 2.1 y creyó que un cambio similar se había realizado en la 2.0.5. En el mismo post Mark señala que no está seguro si se hará necesaria una versión 2.0.5.1, por lo que tendrá que discutir con Matt y Ryan. Aquí está el enlace a la nota de Mark con las instrucciones y el plugin. bitácoras , blogs , internet , open source , software , software libre , web logs , wordpress [...]
[...] 일부 워드프레스 이용자들은 2.0.5로 업데이트를 하면 500 Internal Server 에러가 발생할 수 있습니다. 이 문제를 해결하려면 server 500 error fix를 참고하십시오. [...]
[...] Bei einigen Usern kann es vorkommen das sie einen Sever 500 Error bekommen. Auch hierzu hat sich Mark Jaquith geäußert und stellt eine Lösung parat. Ebenfalls nachzulesen auf seiner Homepage. [...]
[...] edButtons[edButtons.length] = new edButton(’ed_code’,'code’,”,”,’c'); No Comments | Comments RSS Feed Post a Comment Name: [...]
Thanks for the fix. AOK now.
zef, no currently the problem is believed to only affect people running PHP as fastcgi
Reissuing the update with the same version number is a bad idea. People who have already downloaded it won’t know which version they have. That leads to confusion. If the software changes, the version number should change too.
There’s no security issue here. It’s a PHP bug that WordPress will have to work around.
Unfortunately, the change that caused this problem was needed for another group of people (another very small minority). So one group needs the change, or WP is broken, and for another group the change breaks WP. We obviously want a solution that works for both of them (and of course continues to work for the vast majority unaffected by these issues) but it’s a tricky issue, and there isn’t an immediately obvious solution. So the plugin is here for the small amount of people who are having a problem, so their blogs at least work (and have the security updates in 2.0.5) until we can come up with a solution that works for all server setups.
If you are one of the people affected, we’d appreciate it if you’d speak up on the wp-testers list so we can work with you to develop that solution.
Right On! Fixed the error I was having. Sweet!
[...] If you just upgraded to WordPress 2.0.5 like I did and are getting a Server 500 Error (i.e. When you Activate your Plugins you get a ‘File Not Found’ error) You’ll need to install the plugin WordPress 2.0.5 Tuneup which solves the problem. Just follow their instructions and activate it. You’ll come up with the same error again when activating but all should be good after that. [...]
hi mark…
i haven’t upgrading my 2.0.4 to 2.0.5 cause of this bug…
why don’t u relelease the fix with WP 2.0.5.1 for example?? so the people don’t get worry to upgrading their wordpress to 2.0.5 to fix the security issues that u mentioned before.
oh,and I have no bug issues with my 2.0.4
anyway…thanks mark!!!
[...] Como nota adicional, algunos usuarios de WordPress han tenido problemas con mensajes de “500 Internal Server Error” después de actualizar a la version 2.0.5. Existe un fix para este error, se puede encontrar en el blog de Mark Jaquith. [...]
okeyyy…
i have upgrading my WP to 2.0.5
it works fine…with your plugins of course
I have tried everything suggested. I am still not able to access the plugins page to activate it. What do I do?
why i can’t publish my post??
all works fine….but after i finish writing and click publish, it’s fine..
but there’s no new post in my blog??what’s wrong??i’ve already upgraded to 2.0.5 and install your plugins
Because the change that caused this problem was needed for other people. We could just revert, but then they’d be having problems again. We need to find a solution that works for both groups of people before releasing a new version. That’s why I released this plugin… I didn’t want people to be forced to stay back on 2.0.4 in the interim.
I don’t know what issue you’re having with publishing posts, but if it persists with all plugins disabled, you should file a ticket on Trac. Be specific about your setup and the steps to reproduce.
You can edit
wp-includes/pluggable-functions.phpLine 268 is:
status_header($status); // This causes problems on IISDisable this by placing two forward slashes in front of that line, like so:
// status_header($status); // This causes problems on IISThat is the same change that my plugin makes.
Erm…. May I suggest that you have a quick release of the next version 2.0.6 to have this bug fix. Though it may be minor, but users would prefer not to experience hiccups like this.
Cheers!
sorry…i can publishing my posts now.
i del the wp-cache-config.php and it’s all done!!
thx mark
[...] Etter oppgradering til WP 2.0.5 fikk jeg stadig “Server 500 error”. Det irriterte meg, og jeg søkte litt rundt og fant ut at det var flere med dette problemet. Løsningen fant jeg heldigvis her. [...]
[...] Related Links: - WordPress 2.0.5 Ronan - Changes in WordPress 2.0.5 - WordPress 2.0.5 Upgrade: changed files ZIP, changes diff, changed files list - Some WordPress 2.0.5 users reporting Server 500 error [...]
Hey Mark,
Just a question, but what, exactly, is causing this error? I was having the same issue for a plug-in I wanted to activate and my ISP could not give me a straight answer (they’re worthless, in fact).
I’d appreciate any insight into what’s happening.
After upgrading from 204 to 205 wordpress seems to work as usually, but every time I try to change or delete an existing post I get the 500 internal server error. Installed your plugin but it still don’t work. Had the same error when upgrading from 203 to 204 and fixed it by deleting all files in the cache directory without any additional changes to wordpress files. This time it won’t help. What else can I do?
[...] Investigando un poco sobre el tema he encontrado la explicación: Al parecer, el error se les coló a los desarrolladores de este CMS al intentar resolver un bug que realmente había sido reportado para la futura versión 2.1. Rápidamente han puesto a disposición de los usuarios un plugin y los pasos que hay que seguir para su instalación. Lo podéis encontrar aquí. [...]
The causes of 500 errors are too numerous to list, so it’s likely that the reason for this one is not the reason for the one you were having.
Tobais, same goes for you. It sounds like you may have a permissions issue. I’d contact your host about that.
Thanks for the plugin. I’ve found this plugin (or the fix to pluggable-functions) was needed for new installations of 2.0.5 on http://www.yahoo.com and http://www.cendant.com hosted accounts.
Thanks for this plug-in! I was one of the random people having this issue, and the plug-in took care of it right away.
[...] Laut dem Beitrag mit dem Titel Some WordPress 2.0.5 users reporting Server 500 error kann bei einer, lt. Mark, kleinen Anzahl Installationen ein Serverfehler mit der Nummer 500 auftauchen. Im genannten Artikel findet sich ein Plugin, mit dem sich die Situation beheben lässt. [...]
Your fix worked for me, thx.
Many thanks! Server 500 error solved with your plugin.
[...] Ps. don’t forget to download and install this plugins to fix the bug issues comes from this WP versions. [...]
The Plugin fix almost all errors.
But the feedburner from orderedlist.com plugin still doesn’t work.
[...] Nachdem ich nun den 500er-Error mit dem WordPress 2.05 Tuneup -Plugin behoben habe, haben sich fast alle meine Probleme in Luft aufgelöst. Von meinen Schwierigkeiten mit dem Feedburner-Plugin von orderedlist.com mal abgesehen. Dafür werde ich wohl noch eine Weile suchen müssen. [...]
[...] Terug naar 2.04 is dan een optie (waar die database backups al niet goed voor zijn), maar je kunt ook gebruik maken van een plugin die naar aanleiding van dit probleem is geschreven. Mark Jaquith beschrijft in zijn weblog exact de stappen die je moet ondernemen om het probleem op te lossen. [...]
[...] Mark on WordPress: Some WordPress 2.0.5 users reporting Server 500 error [...]
[...] Der Fehler ist auf einen Bug zurückzuführen, der versehentlich in der neuen Version nicht behoben wurde. Möglicherweise wird es deshalb ein 2.0.5.1-Release geben. Wer von dem Fehler betroffen ist, kann mittels eine Plugins Abhilfe schaffen. Das Plugin gibt es im Blog von WordPress-Entwickler Mark [...]
[...] Unos cuantos usuarios han sufrido un mensaje de error “500 Internal Server” tras actualizar a 2.0.5. Para resolver ese problema hay un plugin en Mark on WordPress. [...]
[...] I forbindelse med en stning af WordPress for en god ven lb jeg ind i et uventet problem. Mit semi-nrdede, personlige rekordforsg i hidtil hurtigste opstning af WordPress rg direkte i vasken, da jeg fik en ‘Server 500 error’ fejl-meddelse smidt lige i masken. Jeg var tilsyneladende blevet en del af en minoritet (hvad i hede hule helv…!). Men s er det rart, at gode rd er dyre gratis p internettet. S skulle du blive ramt af samme problem, kan du gre flgende: [...]
[...] Mark on WordPress - Server 500 error fix [...]
i’m still getting the error. I actually had it already before the 2.0.5 upgrade. turned of al the plugins except this one, still get the error. For example: when I save the edit of a link the 500 internal server error returns. Also with a plugin to generate google sitemaps, if i try to make a sitemap it returns me the %@*# error :S
has it something to do with the chmod on the ftp server? or an mysql configuration? I have no clue what is causing this error. i’m going to search for my server error logs if there are an :S
@outlaw_wolf,
That’s the same plug-in I’m having problems with.
@Mark,
I’m betting that the Feedburner plug-in and this recent WordPress update problem have a lot in common, considering they’re both causing a “302 Found” error (the 500 internal server error is cursory).
[...] | Trackback | Listen Article Bookmark at: | Del.icio.us | Furl | Spurl | Blinklist | Simpy | NewsVine [...]
hi mark…sometime i get this if i want to login to my WP.
Warning: Cannot modify header information - headers already sent by (output started at /home/ekowanz/public_html/wp-config.php:24) in /home/ekowanz/public_html/wp-content/plugins/wordpress-2.0.5-tuneup.php on line 25
but sometime not!!
u know why??
and i just moved my server…
[...] Tritt im Admin-Bereich von WordPress 2.05 auf und kann mittels dieses Tips (mit Hilfe eines Plugins) behoben werden. [...]
yes; all my friends asked me this problem, thanks for the solution…
ekowanz,
you need to download the file… not copy-paste. Left-click the big honkin’ “Download” button.
[...] Nach dem Upload der neuen Dateien musste ich allerdings Feststellen, dass ein nicht unbekannter Fehler auftauchte, der mir u.a. auch den Zugang zum Backend verwehrte. Zum Glück fand ich auf Bloggemeyer einen Link zu einem Workaround-Plugin, mit Hilfe dessen WordPress mit einigem Nachdruck wieder funktionierte . [...]
Hi,
I feel stupid…I’m I missing something??
When I type http://ronsrace.nl/wp-admin/plugins.php nothing happens
I can not go into the dashboard section (500 error)
Hope tohear from you!
Ron
A couple of questions:
Can I apply this plugin even if I haven’t seen an error without ill effects?
Where would I see the errors, as a visitor or on admin pages?
[...] Echter verschillen de MySQL versies waarmee backups gemaakt kunnen worden en ge-restored. Tja, en dan is er echt niemand thuis! Zelfredzaam en veel Googelen. Blijkt er ook nog een bug in WordPress 2.05 te zitten. Je raad het al; 3 dagen alles uit de kast halen om mijn data te redden. Helaas zijn er een aantal reacties verloren gegaan. That’s life! [...]
[...] But it didn’t work in the first place, I couldn’t get to my admin section. So i tried this plugin for the 500 (or 302) error page. That didn’t work either. [...]
[...] This bug (#36705) broke the recent WordPress upgrade to 2.0.5 for some people (running fastcgi). There’s a WordPress plug-in by one of WP’s authors that fixes the issue. Unfortunately, there isn’t an easy fix that fixes the problem for all people. If you want to know why, you need to read the discussion of the braindead bug. [...]
[...] As I experienced no problems with this upgrade (especially not the server 500 error), I’ll go ahead and upgrade my main blog as soon as I can. [...]
[...] Also, some WordPress users after upgrading to version 2.0.5 have experienced Server 500 errors. If you are one of these unfortunate users, check out Mark Jaquith’s blog for a plug-in that should fix this known problem. [...]
Ron,
See this comment.
James,
If you’re not having problems, I wouldn’t apply the plugin. You’d see the issues on the admin pages, in multiple places. It would be pretty hard to miss.
I can’t get to plugins.php or even the wp-admin directory at all.
2.0.5 is quite useless, and going back to 2.0.4 gave me “your database is out of date” error and I don’t want to re-run the upgrade..
How can I fix this without the plug in since I can’t activate it.
How did this go through QA? Sheesh..
Spent the whole of yesterday evening trying to troubleshoot Internal Server Errors generated by the back-end after upgrading to 2.0.5.
Tride the plug-in and It is all fine now.
Thanks you very much.
JD
I have upgraded from 2.o4 to 2.05. When trying to rebuild the database I get the internal error. I loaded the plugin. When entering {WPDIR}/wp-admin/plugins.php in the adressbar I get the same message that my database is out of date. What should I do????
EDIT
Extra Info: I tried the method you described in post nr. 20 but it does not work.
The error log reports the following error:
[Thu Nov 16 21:51:47 2006] [error] [client 62.194.176.101] mod_security: Access denied with code 500. Pattern match “!/imp/login\\.php” at HEADER(”Referer”
[id "300018"] [rev "3"] [msg "Generic PHP code injection protection via ARGS"] [severity "CRITICAL"] [hostname "voordedraad.nl"] [uri "/WordPress/wp-admin/upgrade.php?step=1&backto=http://voordedraad.nl/WordPress/wp-admin/"] [unique_id "a3pRoH8AAAEAAARkyBkAAAAU"]
Problem resolved!
When I came back the next dat, the whole thing worked! Computer had been turned off. Only Arne’s sitemap generator gives me the Internal error.
Cheers, Berend
The plugin work for my site Thanks!!!
I install today on my hosting site, from scratch, WordPress 2.0.5 and noticed the 500 internal server errors too. After install the WordPress 2.0.5 Tuneup fix, I have now by default the 500 internal server error. I can’t even login as wp-admin (500 internal server error)
Empty database, install.php (again) and finally the fix, solves my problem
[...] Ich hatte nach dem Installieren von WordPress das Problem, das ich immer einen “Internal Server Error 500″ im Adminbereich bekommen habe. Ich hab mich also ein bisschen schlau gemacht und ein Patch - Plugin dafür gefunden … gugst du hier bzw. gleich dort. [...]
Wonderful! This plug-in also solved the problems on my blog. Thanks!
[...] There is a plug-in, however, which is supposed to take care of this. So if anyone happens to be on WordPress 2.0.5, and is running into this problem, here’s the fix. « NeiA_7 [...]
I tried posting this at the site with the plugin but there was an error so i will post it here:
Thanks for this! I was banging my head against the wall trying to access WP’s dashboard when hosting with Yahoo.
So, for anyone who is using Yahoo web hosting and is getting the following error:
The document has moved here.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
This solved it.
The trick is, since you can’t access the dashboard, you can’t activate the plugin. so i had to go into phpMyAdmin and add the following line to my wp-options > active_plugins row.
i:0;s:26:”wordpress-2.0.5-tuneup.php”;
Add that to the end right before the last bracket ‘}’. you’ll need to change the 0 to the correct number. just look for the last ‘i:’ in that line and look at the number after it. add one and change 0 to that number.
if you don’t have any plugins installed, you need to enter this:
a:1:{i:0;s:26:”wordpress-2.0.5-tuneup.php”;}
hope that helps
eric
[...] I found a link in the wordpress forums to a plugin fix that can be found here [...]
[...] Nun nachdem ich endlich Zeit gefunden habe und ermitteln konnte warum ich das backend vom blog nicht mehr nutzen konnte, will ich mal nachtragen was so in der vergangenen Woche passiert ist. [...]
[...] Por seguridad, es mejor borrar los ficheros /wp-admin/upgrade.php y /wp-admin/install.php, después de la actualización. He leido en Blogpocket que algunos usuarios han sufrido un mensaje de error 500 Internal Server tras actualizar a 2.0.5. Para resolver ese problema hay un plugin en Mark on WordPress. [...]
Heads up for anyone affected by this bug. I’ve put fixes into the SVN repository for
/trunk/and/branches/2.0/Testing would be appreciated! Be sure to remove the tuneup plugin and revert any changes you made to WP core. Let me know how it goes![...] There is a fix (that doesn’t work for me) that might solve some upgrade issues. It takes the form of a plugin for WP and can be found here. [...]
[...] Only happens to a few users apparently (sod’s law that I’d be one of them) so I’ve got to download a plugin from here and then run it. Then I can reinstall Spam Karma (I hope) and stop getting spam comments from being sent to me. Will do it tomorrow night pre-pub quiz as off to see James Pond in Chicken Royale at t’cinema
[...]
Hi,
I just did the update and I did not get any error. But I moved the plugin to my plugin directory, just in case. However I cannot see it at all in the list of plugins!
Is this the wrong place to ask this question? Anybody else faced this issue?
I’m wondering if all the problems I’ve been getting with WordPress can be fixed with this plugin. I am planning to set up the blog on a different host and kept getting the 500 errors and can’t log in. And sometimes when I do log in, when I’m supposed to be in the dashboard, I still see my main page. Is this going to fix that?
Also, it seems to be so terribly slow to update. Could this also fix that as well? I’ve been scratching my head since I wasn’t sure if it was my new host or whatever.
Looks like I still have it and the dashboard doesn’t load the dashboard and I’m getting my main page. Sigh. I can’t seem to figure this out. Grr.
[...] 同樣是修正一些 bugs，主要是有些人回報說在某些使用 PHP 5.2 或者拿 FastCGI 來跑 PHP 的 hosting 上面會得到 500 的錯誤訊息。當然，這個之前已經有使用 plugin 的方式修正。 [...]
I’m trying to update wordpress from 1.5.2 to 2.0.5 and i get error 500.
Plugin doesn’t work for me, because i’m not be able to open any page without getting this error.
I also tried to enable plugin in 1.5.2 and upgrade to 2.0.5 without deactivate the plugin, but it doesn’t work.
To all people who have had issues with 2.0.5: try the 2.0.6 beta release!
In my main blog, is not a goog idea to try beta release…
Argh!!! I think I’m getting this error thing. I have installed the plug-in fix, but everything’s still the same.
Here’s what’s happening - I have two feeds: a worpress feed and a feedburner feed. The feedburner feed, I think, is getting the 500 error - in bloglines, it shows a red exclamation point, and the error states that “The feed does not appear to exist. This can be caused by the feed URL being incorrect, or it can be caused by a configuration issue with the server hosting the feed.”.
The wordpress feed just doesn’t seem to be doing much - in bloglines and in google reader, my most recent post is not appearing. Two people using netvibes as their aggregator DID receive my latest post.
So I’m really confused. Help!!!!!!!!!!!!!!!
I’m also having problems with feeds when I activate this plugin…
The server error goes away, but there is a feed parsing error. Seems that there is extra white space in the xml declaration. Most of the site works without this plugin, so i’m leaving it disabled so feeds work…
Hopefully this will be fixed in 2.1?
trish stratus topless
http://myblog.es/trish-stratus
[...] Download: wordpress-2.0.5-tuneup.php.gz Original post: 500 server error fix plugin（中国用户可能会访问不了） Bookmark to: [...]
[...] В деяких користувачів WP можуть мати 500 Internal Server error повідомлення після оновлення до 2.0.5. Для того щоб виправити цей помилку перейдіть сюди: server 500 error fix [...]
My problem was solved as well. Tnx for the fix.
This plugin fixed it for me too - my web host is running PHP 5 as a CGI application and would throw back 302/500 errors until I installed the plugin. All works just fine now. Thanks
M.
I had that problem I fixed with the plug in, but my feeds still deliver the 500 Error! check:
http://www.thewiredblog.com/?feed=rss2
I´m using Yahoo as a hosting.
What´s the problem?
Somewhat late I know - but it was only now that I (a) got round to upgrading to 2.0.5 and (b) working out why it didn’t work
Having found that the 302 errors I was seeing went away after reverting to “PHP4 Apache module mode” from “PHP4 FastCGI mode”, I (fortunately) found your plugin, which meant I avoided having to decide whether to downgrade my WordPress version, or continue to run without the benefits of FastCGI.
Thanks again Mark.
[...] bitte, der kümmere sich darum, danke. Helfen tat mir schließlich dieser Thread, der mich über ein weiteres Blog zu WordPress 2.0.5 Tuneup führte. Und siehe da, es funktioniert sogar. Hin und wieder scheinen [...]
[...] changes are under the hood in the way of security fixes, plus there shouldn’t be a need with Mark Jaquith’s plugin for those that were having server 500 problems with WordPress [...]
it worked. thanks
Hi you said what to do if you get the error message after you log in but i get it before.
http://mkwebtravel.com/blog/wp-admin/
I have BluHost so i went into my blog folder through there and uploaded the plugin into the right folder : /www/blog/wp-content/plugins
but now i am at a total loss as to what to do and i have been reading comments for hours and found nothing helpful.
If you have any ideas please let me know. Thank you for your help and expertise.
Sincerely,
MK
I also have the Problem, with the 500. So I downloaded the plugin and loaded it up again. I tried to aktivate it, but i can’t enter any pages of my wordpress. So I changed the file pluggable-funktions.php as u said. But it is still not working. Help me please!!
I just realised, that I already installed the 2.0.6 Version. So how can I still get this Problem?? It always appears first, after I have been in Settings and PErmalinks. I also changed the link appearance once. Could this be the Prob??
I still get this 500 error, even with version 2.0.7.
There are many different reasons someone might get that error. Best to hit up the support forums or file a bug report.
For the past week or so i’ve been having a 503 error when trying to log or view my url
http://twobrothersandasister.com
When i contacted my provider they said there are too many process being executed so that’s the thing that is causing these error.
Not sure if this is a DoS attack or anything like that ( read in wordpress thread ) but i am running spamkarma, bad behaviour and spam karma…
I haven’t done any major changes except for the header image but that was on New Year…
if anyone have any ideas, appreciate the help…cause im going crazy
[...] I now have my blog back from the bleeding 500/302 black hole, let the noise begin! Aside part deux: Go Kenya Go!, now that’s what i call a spanking! (and [...]
[...] Blake在IRC上頭提到這一篇，先note起來，希望不要再出現500 Error了，再出現一次我就要去裝plugin了 >” [...]
[...] There is a fix (that doesn’t work for me) that might solve some upgrade issues. It takes the form of a plugin for WP and can be found here. [...]
[a href="deneme.com"]sdfdfsdf[/a]
[...] having updated WordPress to version 2.0.5, you can find some Error 500 (or 302) when writing new posts (you’ll fortunately not lose any content). Mark Jaquith wrote a simple plug-in to fix this [...]
[...] hear that it may be fixable using this plugin, but I need to do some testing first. Related [...]
Thanks for the plugin, it worked a treat on my blog … it took me quite some time finding the fix, now I have I’m over the moon.The 500 error only occured when adding new blog posts in my case. Thanks again.
[...] is easily fixed with a plugin. You can read more about it here. You will see an HTTP 302 status code and the actual error message you will get when you see this [...]
[...] Unos cuantos usuarios han sufrido un mensaje de error “500 Internal Server” tras actualizar a 2.0.5. Para resolver ese problema hay un plugin en Mark on WordPress. [...]
Your fix worked perfectly, many thanks!!
[...] Unos cuantos usuarios han sufrido un mensaje de error “500 Internal Server” tras actualizar a 2.0.5. Para resolver ese problema hay un plugin en Mark on WordPress. [...]
[...] was giving me all kinds of class_snoopy.php errors this morning. I downloaded & installed a fix plugin & all seems to be working better [...]
I followed these editing instructions:
wp-includes/pluggable-functions.php
Line 268 is:
status_header($status); // This causes problems on IIS
Disable this by placing two forward slashes in front of that line, like so:
// status_header($status); // This causes problems on IIS
After I added the two forward slashes, I saved and closed http://ftp. Now when I look at that code again in ftp it is completely blank. Is that a problem? I’m not sure I’ve done anything positive here…please advise. Little worried I may have messed something up, though the site seems to be okay thus far.
My other site didn’t fair as well…I uploaded the plugin and got a 500 error upon trying to write a new post. Then I manually changed the code in the pluggable.php (not pluggable-functions.php) adding the two forward slashes and I ended up with a white screen on the new post page. It would load the top portion of the new post page quickly, but it couldn’t seem to finish the bottom of the post page…it would white out the bottom portion, though there was no error code.
Hello,
I am using linux server. I am facing problem as follows
whenever I am login using WordPress username and
Password. I can’t even veiw the site from within WordPress.
How to fix this problem?
Mak
very interesting, but I don’t agree with you
Idetrorce