This plugin has been marked as retired. It is recommended that you no longer use it.
Donate
I’ve spent a lot of time writing this code and supporting it. If you derive some benefit from this code, please consider showing your gratitute in a more tangible
way. Thanks!
I have received $0 this month for my coding efforts.
bugfixes, minor feature enhancements, and a couple of database speedups. There is also a minor security fix. If you experiencing Server 500 errors (or anything related to 302) in the admin screen after you have upgrade into 2.0.5, please download this plugin. Need help on “how to upgrade?”. Visit here or here [IMG ] Have fun with Wordpress. I aslo finish make new style scheme for k2. This new style is called “Shade Of Dusk”. Hope you gonna like it
Until then you may want to upgrade your installation. 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. [IMG]Copyright 2006 Ajay – On the Road called Life!. This Feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is
fixes so nothing super exiting to report on. I have also done some house cleaning on the site. added some colourful mini icons (I’m going to post soon on were to get a bunch) removed some clutter and tweaked some other things. There is a 2.0.5 Tune-up Plugin.
support forums, it appears it has some issues that will impact some upgraders (302 Found messages). To start a new tradition, Mark has released a 2.0.5 Tuneup plugin, continuing in the vein of the famous 2.0.3 tuneup plugin. Must be something about odd numbered releases. *grin* If curious about what’s changed or looking for a package of just the changed files, see this post by same Mark, different blog. The dev blog announcement mentions security fixes as well,
ve found a solution to the problem which apparently, was caused by some code fro the upcoming WordPress 2.1 which inadvertently made made it back into 2.05. There are two ways to resolve the issue, one is by using the following plugin: http://txfx.net/code/wordpress/wordpress-tuneup/wordpress-205-tuneup/ Now, while that is a quick and easy fix, it’s not for me, because calling a plugin to fix a bug requires extra work on behalf of WordPress and we all like our blogs to run as quick as possible don
længere efter deres filnavne. Det var da nu alligevel på tide! Der er indtil videre kun fundet en enkelt fejl i den nye udgave, men hvis du er en af de forholdsvis få, der bruger FastCGI, vil du blive en glad blogger, hvis du sørger for at hente Tempus Fugits WP 2.0.5 Tuneup, så dine redirects virker igen. Og til sidst en lille kuriøsitet. For føste gang nogensinde er en udgivelse ikke opkaldt efter en jazz-legende, men i stedet efter en af hovedudviklernes nyfødte søn,
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. Fixing this error is some what easy, for it’s fixable just by installing a plugin, below are the step to fix this error. Download this plugin. Upload it to your WordPress plugins folder. Activate the plugin. However if you get an error message after logging in to your admin panel and cannot click the Plugins tab, just type “{WPDIR}/wp-admin/plugins.php”
Seit dem bekomme ich immer bei neuen Posts einen Fehler 500 — Internal Server Error! Der Post wird zwar in die Datenbank geschrieben und funktioniert auch anstandslos — die dauernden Fehlermeldungen sind aber mehr als nervig… Das PlugIn “žwordpress 2.0.5 tuneup” hat keine Besserung gebracht! Weiß jemand von Euch, was da faul ist?
released to the world. This latest release consists mainly of minor bugfixes, minor feature enhancements, and a couple of database speedups. There is also a minor security fix. There is a known bug related to sites running under FastCGI, but a workaround is available in the form of a plugin. Upgrading is painless, so hop to it!
Jeg har haft et par abstinensdage, som endte med en backup af databasen, sletning af alle gamle wordpress-filer og upload af den nyeste version. Blot for at blive ramt af ‘500 Internal Server Error’-syndromet. [IMG 500.jpg] Der findes en plugin
Server 500 Errors on their blogs. Mark Jaquith, a contributing developer for WordPress, points that it is only a small minority of people that is affected, and the problem can be fixed with a plugin. “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
Well, I guess that if it can go wrong it will, and it sure did go wrong for me. There can a problem when you upgrade, but fortunately there is a way to get aruound this error. A plugin called Wordpress 2.0.5 Tuneup fixes this bug that actually is not a WordPress bug but rather a PHP bug. If PHP is run under FastCGI then there is a big chance that you will get a Server 500 error, or a 302 redirect. But whatever error you get this little plugin does the trick!
Recent Delicious WordPress 2.0.5 Tuneup [ Tempus Fugit | TxFx.net ] Wordpress Theme Toolkit « planetOzh xkcd – A webcomic of romance, sarcasm, math, and language – By Randall Munroe Use Gmail as your universal email account – Lifehacker BlogF1 – Your Regular Blog and Guide to Formula One » Circuits
Efter installationen er det ned af bakke og sÃ¥ er det bare at gÃ¥ i gang med selve skriveriet, designet og alle de smarte plugin’s man kan forestille sig. Til tri9ty.com er der brugt følgende: WordPress 2.0 Cat2Tag v2.0 WordPress Heat Map WordPress 2.0.5 TuneUp Den store bonus er, at jeg fremover bare skal bruge internetadgang samt en browser for at kunne opdatere hele siden. Dette burde unægteligt resultere i en del flere opdateringer fremover. Et absolut anbefalelsesværdigt produkt (ogsÃ¥ til
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
smidt lige i masken. Jeg var tilsyneladende blevet en del af en minoritet. Men sÃ¥ er det rart, at gode rÃ¥d er dyre gratis pÃ¥ internettet. SÃ¥ skulle du blive ramt af samme problem, kan du gøre følgende: Som det første skal du hente og uploade dette plugin, hvorefter du skal aktivere det under fanebladet “Plugins” i din administrationsdel. Skulle du fÃ¥ fejlmeddelelsen netop efter at have logget ind, og derfor ikke kan vælge “Plugins”, kan du skrive
(9 days since its release – that’s slow going for me!). Thanks to Mark for the changed files zip, it’s really helpful, and for the heads-up about Error 500s – I did have the problem, but the supplied tune-up plugin took care of it. Thanks!
500 Internal Server error messages after upgrading to WordPress v2.0.5. 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
ve decided to stick with the older version. I hope the WordPress team releases the 2.0.6 version wityh this bug fixed soon so I will wait for it. Anyway for those who have experienced these errors, you can tune-up your WordPress using this plugin. Some users report success upon installing this plugin.
After 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 little annoyance. Upload it, activate it and you’re free from this small bug. Posted in Websites | No Comments »
Na enig researchwerk van uw hoofdredacteur is Wordpress foutloos draaiend. De fout blijkt een bug in Wordpress 2.0.5 en is te verhelpen met WordPress 2.0.5 Tuneup, hier te downloaden.
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. Ich hab das Plugin installiert, seitdem funktioniert das WP einwandfrei. thx.
bloggen ikke ser bekendt ud, sÃ¥ er det fordi WordPress (der ellers er the shit, pÃ¥ den gode mÃ¥de, naturligvis) med den seneste opdatering 2.0.5 tilsyneladende har lavet noget, der diplomatisk sagt ikke er en udelt succes, først mÃ¥tte jeg finde et bug fix plugin for at slippe for mærkelige fejlmeddelelsessider hver gang jeg gjorde noget i mit adminpanel. Sidenhen spiller den sÃ¥ tilsyneladende ikke med mit tema, da jeg kun fÃ¥r titlen + overskriften pÃ¥ den seneste post – og intet andet
Hvis du dog alligevel får fejlen, bedes du skrive en kommentar til dette indlæg, så jeg kan se nærmere på det. // Er du selv blogger? Med WP 2.0.5, med samme problem? her er linket til det plugin jeg hentede, sammen med en guide: WP 2.0.5 tuneup plugin
. Et skifte der gerne skulle resultere i, at siden bliver nemmere at administrerer. Wordpress er kendt for at være nem at installere, men jeg havde dog store problemer med “Page not found”. Heldigvis kunne et lille plugin klare problematikken. ekrajb.dk – Blog og hjemmeside…
Download the danish version of the blog (the english version did not work 4me) (Available here) Follow the general installation guideline (should be obvious [IMG ] ) Make sure to install the following plugin: 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. I do belive that the english(standard) version of wordpress does work at
username and password you received in your mail (hint: its the username and password that belong to mysql) Leave localhost as it is. Personally I decided to change the table_prefix slightly. Rename …sample to config.php 3. Get hold of the plugin: wordpress-205-tuneup and put the plugin into the directory wordpress/wp-content/plugins 4. Upload your wordpress folder to your website. Personally I would keep the wordpress folder for tidiness’ sake, and not upload all the small wp files directly into your root
This release intended for those who’s having problem with their wordpress 2.0.5 installation such as 500 server error, 302 found, etc (although there’s special fix for that problem available for download from here) .. especially for those who’s running their wordpress installation under FastCGI server or running PHP 5.2 (i don’t experience this problem because my host is running PHPSuExec not FastCGI) ..
There is a small bug in wp-redirect() in WordPress 2.0.5 This 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 bug is: “Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to
Wordpress 2.0 heeft op sommige webhosts blijkbaar enkele problemen met “posten” en doorverwijzen naar andere pagina’s. Na wat googelen kwam ik terecht bij een WordPress 2.0.5 Tuneup plugin. Deze plugin verhelpt het “Document has moved” probleem en laat ook heel wat andere dingen vlotter verlopen! Mocht je ooit hetzelfde probleem hebben, denk dan eens aan mij
schweigt sich dazu gar in seinen Supportforen aus, betroffene Benutzer sollten doch bitte ihren jeweiligen Hoster kontaktieren, 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 doch noch Wunder zu geschehen. Bad Company
Got fixed the error with wordpress with a plugin WordPress Tuneup so that was nice and easy… seems all the site is working now… Default, Site | Comments (0)
trouble retrieving the data to WordPress, so I decided to upgrade to the latest version, 2.0.5. I did a fresh install to a blank database, imported the data, turned the necessary plug-ins off then on, then loaded a couple new plug-ins: WP-Cache2 and WordPress 2.0.5 Tuneup. The cache plug-in should cut down on MySQL usage since the most viewed pages will be loaded into a cache and stored as static files. The tuneup plug-in fixes an error 500 bug that cropped up in the latest release of WordPress.
’s the link for version 2.0.6 Update: Installed, and works flawlessly. It even fixes the 404 error which some bloggers experiense every time they post or edit etc. Before 2.0.6, you had to install this fix to make it work. Just for that one, it’s worth upgrading.
bugfixes, minor feature enhancements, and a couple of database speedups. There is also a minor security fix. If you experiencing Server 500 errors (or anything related to 302) in the admin screen after you have upgrade into 2.0.5, please download this plugin. Need help on “how to upgrade?”. Visit here or here [IMG
] Have fun with Wordpress. I aslo finish make new style scheme for k2. This new style is called “Shade Of Dusk”. Hope you gonna like it
Until then you may want to upgrade your installation. 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. [IMG]Copyright 2006 Ajay – On the Road called Life!. This Feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is
fixes so nothing super exiting to report on. I have also done some house cleaning on the site. added some colourful mini icons (I’m going to post soon on were to get a bunch) removed some clutter and tweaked some other things. There is a 2.0.5 Tune-up Plugin.
support forums, it appears it has some issues that will impact some upgraders (302 Found messages). To start a new tradition, Mark has released a 2.0.5 Tuneup plugin, continuing in the vein of the famous 2.0.3 tuneup plugin. Must be something about odd numbered releases. *grin* If curious about what’s changed or looking for a package of just the changed files, see this post by same Mark, different blog. The dev blog announcement mentions security fixes as well,
ve found a solution to the problem which apparently, was caused by some code fro the upcoming WordPress 2.1 which inadvertently made made it back into 2.05. There are two ways to resolve the issue, one is by using the following plugin: http://txfx.net/code/wordpress/wordpress-tuneup/wordpress-205-tuneup/ Now, while that is a quick and easy fix, it’s not for me, because calling a plugin to fix a bug requires extra work on behalf of WordPress and we all like our blogs to run as quick as possible don
længere efter deres filnavne. Det var da nu alligevel på tide! Der er indtil videre kun fundet en enkelt fejl i den nye udgave, men hvis du er en af de forholdsvis få, der bruger FastCGI, vil du blive en glad blogger, hvis du sørger for at hente Tempus Fugits WP 2.0.5 Tuneup, så dine redirects virker igen. Og til sidst en lille kuriøsitet. For føste gang nogensinde er en udgivelse ikke opkaldt efter en jazz-legende, men i stedet efter en af hovedudviklernes nyfødte søn,
2.0.5 Tune Up – but it still ain’t working – anyone else having problems? admin section» Blogging» front page» Misc.» Tech» tune up» wordpress»
Hoy en la mañana decidà borrar todo el blog de prueba, borrar sus tablas de la base de datos y realizar una instalación “en limpio”, y el problema persistió. Solo que esta vez si encontré respuestas: La instalación de este Plugin resolverá el problema del 302 found, sin que el usuario tenga que tocar el código fuente del Wordpress. También existe una solución modificando una lÃnea en uno de los archivos del sistema. Espero que si alguien tiene este problema, les ayude un
happened). List of changes here. Apparently, there’s a new problem when running on a server with FastCGI installed: it may give a 500 error in some cases. If that’s your situation, there’s a workaround. Copyright © 2006 The Tlog
happened). List of changes here. Apparently, there’s a new problem when running on a server with FastCGI installed: it may give a 500 error in some cases. If that’s your situation, there’s aworkaround. fastcgi, wordpressCopyright © 2007 The Tlog
WordPress 2.0.5 Tuneup [ Tempus Fugit | TxFx.net ]
ØŒ النسخة العربية جاهزة للتØÙ…يل من ØµÙØØ© التØÙ…يل. Ù…Ù„Ø§ØØ¸Ø©: إذا ظهرت لك رسالة الخطأ “500 Internal Server Error” Ùقم بإستخدام Ø¥Ø¶Ø§ÙØ© WordPress 2.0.5 Tuneup.
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. Fixing this error is some what easy, for it’s fixable just by installing a plugin, below are the step to fix this error. Download this plugin. Upload it to your WordPress plugins folder. Activate the plugin. However if you get an error message after logging in to your admin panel and cannot click the Plugins tab, just type “{WPDIR}/wp-admin/plugins.php”
الطريقة ليست معقدة؛ تجدونها Ù…ÙØµÙ„Ø© ÙÙŠ موسوعة البرنامج: Upgrading WordPress. إذا واجهتم، بعد الترقية، مشكلة الـ (Server 500 error) ÙØ¥Ù† الØÙ„ ÙÙŠ تركيب Ø§Ù„Ø¥Ø¶Ø§ÙØ© WordPress 2.0.5 Tuneup. إكتساØ: الآن وصل عدد الأصوات Ø§Ù„Ù…Ù…Ù†ÙˆØØ© لهذه المدونة ÙÙŠ مسابقة TheBOBs مئتي صوت. نصÙها على الأقل من طر٠زوار الموقع المغربي
Seit dem bekomme ich immer bei neuen Posts einen Fehler 500 — Internal Server Error! Der Post wird zwar in die Datenbank geschrieben und funktioniert auch anstandslos — die dauernden Fehlermeldungen sind aber mehr als nervig… Das PlugIn “žwordpress 2.0.5 tuneup” hat keine Besserung gebracht! Weiß jemand von Euch, was da faul ist?
WordPress 2.0.5 Tuneup
» WordPress 2.0.5 Tuneup [ Tempus Fugit | TxFx.net ]
released to the world. This latest release consists mainly of minor bugfixes, minor feature enhancements, and a couple of database speedups. There is also a minor security fix. There is a known bug related to sites running under FastCGI, but a workaround is available in the form of a plugin. Upgrading is painless, so hop to it!
Jeg har haft et par abstinensdage, som endte med en backup af databasen, sletning af alle gamle wordpress-filer og upload af den nyeste version. Blot for at blive ramt af ‘500 Internal Server Error’-syndromet. [IMG 500.jpg] Der findes en plugin
Server 500 Errors on their blogs. Mark Jaquith, a contributing developer for WordPress, points that it is only a small minority of people that is affected, and the problem can be fixed with a plugin. “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
Well, I guess that if it can go wrong it will, and it sure did go wrong for me. There can a problem when you upgrade, but fortunately there is a way to get aruound this error. A plugin called Wordpress 2.0.5 Tuneup fixes this bug that actually is not a WordPress bug but rather a PHP bug. If PHP is run under FastCGI then there is a big chance that you will get a Server 500 error, or a 302 redirect. But whatever error you get this little plugin does the trick!
Recent Delicious WordPress 2.0.5 Tuneup [ Tempus Fugit | TxFx.net ] Wordpress Theme Toolkit « planetOzh xkcd – A webcomic of romance, sarcasm, math, and language – By Randall Munroe Use Gmail as your universal email account – Lifehacker BlogF1 – Your Regular Blog and Guide to Formula One » Circuits
Efter installationen er det ned af bakke og sÃ¥ er det bare at gÃ¥ i gang med selve skriveriet, designet og alle de smarte plugin’s man kan forestille sig. Til tri9ty.com er der brugt følgende: WordPress 2.0 Cat2Tag v2.0 WordPress Heat Map WordPress 2.0.5 TuneUp Den store bonus er, at jeg fremover bare skal bruge internetadgang samt en browser for at kunne opdatere hele siden. Dette burde unægteligt resultere i en del flere opdateringer fremover. Et absolut anbefalelsesværdigt produkt (ogsÃ¥ til
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
smidt lige i masken. Jeg var tilsyneladende blevet en del af en minoritet. Men sÃ¥ er det rart, at gode rÃ¥d er dyre gratis pÃ¥ internettet. SÃ¥ skulle du blive ramt af samme problem, kan du gøre følgende: Som det første skal du hente og uploade dette plugin, hvorefter du skal aktivere det under fanebladet “Plugins” i din administrationsdel. Skulle du fÃ¥ fejlmeddelelsen netop efter at have logget ind, og derfor ikke kan vælge “Plugins”, kan du skrive
(9 days since its release – that’s slow going for me!). Thanks to Mark for the changed files zip, it’s really helpful, and for the heads-up about Error 500s – I did have the problem, but the supplied tune-up plugin took care of it. Thanks!
500 Internal Server error messages after upgrading to WordPress v2.0.5. 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
ve decided to stick with the older version. I hope the WordPress team releases the 2.0.6 version wityh this bug fixed soon so I will wait for it. Anyway for those who have experienced these errors, you can tune-up your WordPress using this plugin. Some users report success upon installing this plugin.
After 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 little annoyance. Upload it, activate it and you’re free from this small bug. Posted in Websites | No Comments »
Na enig researchwerk van uw hoofdredacteur is Wordpress foutloos draaiend. De fout blijkt een bug in Wordpress 2.0.5 en is te verhelpen met WordPress 2.0.5 Tuneup, hier te downloaden.
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. Ich hab das Plugin installiert, seitdem funktioniert das WP einwandfrei. thx.
bloggen ikke ser bekendt ud, sÃ¥ er det fordi WordPress (der ellers er the shit, pÃ¥ den gode mÃ¥de, naturligvis) med den seneste opdatering 2.0.5 tilsyneladende har lavet noget, der diplomatisk sagt ikke er en udelt succes, først mÃ¥tte jeg finde et bug fix plugin for at slippe for mærkelige fejlmeddelelsessider hver gang jeg gjorde noget i mit adminpanel. Sidenhen spiller den sÃ¥ tilsyneladende ikke med mit tema, da jeg kun fÃ¥r titlen + overskriften pÃ¥ den seneste post – og intet andet
Hvis du dog alligevel får fejlen, bedes du skrive en kommentar til dette indlæg, så jeg kan se nærmere på det. // Er du selv blogger? Med WP 2.0.5, med samme problem? her er linket til det plugin jeg hentede, sammen med en guide: WP 2.0.5 tuneup plugin
. Et skifte der gerne skulle resultere i, at siden bliver nemmere at administrerer. Wordpress er kendt for at være nem at installere, men jeg havde dog store problemer med “Page not found”. Heldigvis kunne et lille plugin klare problematikken. ekrajb.dk – Blog og hjemmeside…
Download the danish version of the blog (the english version did not work 4me) (Available here) Follow the general installation guideline (should be obvious [IMG
] ) Make sure to install the following plugin: 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. I do belive that the english(standard) version of wordpress does work at
username and password you received in your mail (hint: its the username and password that belong to mysql) Leave localhost as it is. Personally I decided to change the table_prefix slightly. Rename …sample to config.php 3. Get hold of the plugin: wordpress-205-tuneup and put the plugin into the directory wordpress/wp-content/plugins 4. Upload your wordpress folder to your website. Personally I would keep the wordpress folder for tidiness’ sake, and not upload all the small wp files directly into your root
This release intended for those who’s having problem with their wordpress 2.0.5 installation such as 500 server error, 302 found, etc (although there’s special fix for that problem available for download from here) .. especially for those who’s running their wordpress installation under FastCGI server or running PHP 5.2 (i don’t experience this problem because my host is running PHPSuExec not FastCGI) ..
There is a small bug in wp-redirect() in WordPress 2.0.5 This 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 bug is: “Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to
Wordpress 2.0 heeft op sommige webhosts blijkbaar enkele problemen met “posten” en doorverwijzen naar andere pagina’s. Na wat googelen kwam ik terecht bij een WordPress 2.0.5 Tuneup plugin. Deze plugin verhelpt het “Document has moved” probleem en laat ook heel wat andere dingen vlotter verlopen! Mocht je ooit hetzelfde probleem hebben, denk dan eens aan mij
schweigt sich dazu gar in seinen Supportforen aus, betroffene Benutzer sollten doch bitte ihren jeweiligen Hoster kontaktieren, 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 doch noch Wunder zu geschehen. Bad Company
t figure this out faster. I also discovered an issue with WP 2.0.5 that caused WordPress to ask me for confirmations for some things; it turns out this is related to FastCGI and can be fixed with the WordPress 2.0.5 Tuneup plugin. [IMG] © Amanita.net – Advertise with us!
Got fixed the error with wordpress with a plugin WordPress Tuneup so that was nice and easy… seems all the site is working now… Default, Site | Comments (0)
trouble retrieving the data to WordPress, so I decided to upgrade to the latest version, 2.0.5. I did a fresh install to a blank database, imported the data, turned the necessary plug-ins off then on, then loaded a couple new plug-ins: WP-Cache2 and WordPress 2.0.5 Tuneup. The cache plug-in should cut down on MySQL usage since the most viewed pages will be loaded into a cache and stored as static files. The tuneup plug-in fixes an error 500 bug that cropped up in the latest release of WordPress.
WordPress 2.0.5 Tuneup [ Tempus Fugit | TxFx.net ]
’s the link for version 2.0.6 Update: Installed, and works flawlessly. It even fixes the 404 error which some bloggers experiense every time they post or edit etc. Before 2.0.6, you had to install this fix to make it work. Just for that one, it’s worth upgrading.
WordPress Tuneup [ Tempus Fugit | TxFx.net ]
Visit
Plugin Status Stable Author Mark Jaquith Version 0.1 Plugin HomeVisitAuthor Homepage Visit Download Visit Plugin License N/A Description : Fixes bugs in WordPress 2.0.5 (more…)
I need the latest version of Tuneup:WordPress 3.3.3 Tuneup.
Is there a 2.3.3 tuneup for me to download since my blog is 2.3.3 version, Thanks
WordPress 3.3.3 Tuneup. “Additionally, a 500 Internal Server Error