A tela branca da morte do WordPress é um dos erros mais comuns do WordPress. Também é um erro frustrante porque não há mensagem e você fica bloqueado no WordPress.
Outro problema com o erro da tela branca da morte é que, às vezes, ele afeta apenas uma determinada parte do seu site. Por exemplo, talvez você só veja a tela branca da morte dentro da área de administração do WordPress, enquanto todo o resto funciona bem. Em outros casos, pode ser que ela apareça somente em um post específico.
Neste artigo, mostraremos como corrigir a tela branca da morte do WordPress, analisando diferentes soluções.
Observação: antes de fazer qualquer alteração em seu site, certifique-se de ter um backup do site do WordPress. Se você não tiver acesso à área de administração, consulte nosso guia sobre como criar manualmente um backup do banco de dados do WordPress.
Por que você vê a tela branca da morte no WordPress?
Na maioria das vezes, quando você vê uma tela branca da morte ao tentar visitar seu site do WordPress, isso significa que um script em seu site esgotou o limite de memória.
O script que não responde é eliminado pelo servidor de hospedagem do WordPress ou simplesmente atinge o tempo limite. É por isso que nenhuma mensagem de erro real é gerada, e você vê apenas uma tela branca em branco.
No entanto, às vezes, você pode ver uma mensagem de erro.
Por exemplo, você pode ver uma mensagem de erro crítico em vez de uma página em branco.
Não importa se você está vendo uma tela em branco ou a mensagem “Houve um erro crítico no seu site”, o erro é o mesmo.
Esse erro também pode ocorrer devido a um tema ou plug-in mal codificado instalado em seu site. Às vezes, isso pode ocorrer se houver um problema com seu servidor de hospedagem na Web.
Como o erro de tela branca pode ser causado por vários fatores, é necessária uma solução de problemas metódica para corrigi-lo. Aqui estão as etapas que você deve tentar:
- Check Whether the Problem Happens on Your Other Sites
- Fix the White Screen Error With WordPress Recovery Mode
- Increase the Memory Limit
- Fix the White Screen Error by Disabling All Plugins
- Activate the Default Theme
- Enable Debug Mode to Catch Errors in WordPress
- Clear the WordPress Cache
- Fix the White Screen Error for Longer Articles
Tutorial em vídeo
Se você preferir instruções por escrito, continue lendo.
1. Verifique se o problema ocorre em seus outros sites
Se você tiver outros sites WordPress instalados na mesma conta de hospedagem, comece verificando se o problema também está ocorrendo em outros sites.
Se for, esse é um forte indicador de que há algo errado com seu serviço de hospedagem WordPress. Esse pode ser um problema temporário que afeta o serviço e você precisa entrar em contato com o suporte para obter mais ajuda.
Por outro lado, se o problema estiver ocorrendo somente em um site ou em uma parte específica desse site, você saberá que o problema está nesse site específico.
2. Corrigir o erro de tela branca com o modo de recuperação do WordPress
Se o erro da tela branca da morte for causado por um plug-in ou tema do WordPress, o WordPress poderá detectá-lo.
O novo recurso de proteção contra erros fatais introduzido no WordPress 5.2 pode, às vezes, detectar o erro, de modo que talvez você nem veja uma tela branca. Em vez disso, você verá uma mensagem informando que o site está com dificuldades técnicas.
O WordPress também enviará um e-mail sobre o problema para seu endereço de e-mail de administrador.
O e-mail terá o assunto “Seu site está passando por um problema técnico”.
Essa mensagem de e-mail indicará o plug-in ou o tema que está causando o erro e também conterá um link especial.
Esse link permitirá que você faça login no modo de recuperação do WordPress e desative o plug-in com defeito.
No entanto, se estiver vendo a tela branca da morte sem nenhuma opção de e-mail ou modo de recuperação, será necessário corrigir o erro manualmente.
3. Aumentar o limite de memória
Normalmente, esse erro ocorre porque um script esgotou a memória do servidor da Web e foi encerrado no meio do processo.
Para corrigir isso, você precisa aumentar a memória PHP disponível para o WordPress. Isso permitirá que o script use mais memória para concluir o trabalho que deveria fazer.
Você precisará editar o arquivo wp-config.php em seu site do WordPress ou usar um plug-in de snippet de código como o WPCode.
Você pode seguir as instruções em nosso tutorial sobre como aumentar a memória PHP no WordPress.
4. Corrija o erro de tela branca desativando todos os plug-ins
Se o aumento do limite de memória do PHP não ajudar, ou se você tiver um limite de memória alto, como 256M ou 512M, será necessário iniciar a solução de problemas.
Em nossa experiência de solução de problemas, sempre descobrimos que o problema está em um plug-in específico ou em um tema. Vamos em frente e desativar todos os plug-ins.
Se ainda puder acessar o painel de administração do WordPress, basta ir para a página Plugins ” Plugins instalados. Selecione todos os plug-ins instalados e, em seguida, selecione “Deactivate” (Desativar) no menu suspenso “Bulk actions” (Ações em massa).
No entanto, se você não tiver acesso à área de administração do WordPress, precisará desativar todos os plug-ins via FTP.
Primeiro, conecte-se ao seu site WordPress usando um cliente FTP ou o gerenciador de arquivos do seu provedor de hospedagem. Depois de conectado, vá para a pasta wp-content, onde você verá a pasta plugins.
Agora, você precisa clicar com o botão direito do mouse na pasta de plug-ins e selecionar “Renomear”. Você pode renomear a pasta de plug-ins para “plugins-deactivated”.
O WordPress procura uma pasta chamada plugins para carregar todos os plugins. Quando não consegue encontrar a pasta, ele simplesmente desativa todos os plug-ins.
Se isso corrigir o problema, ative um plug-in de cada vez para descobrir a causa do problema. Quando encontrar o plug-in que está causando o problema, você poderá substituí-lo por um alternativo ou relatar o problema aos autores do plug-in.
5. Ativar o tema padrão
Se a solução de problemas do plug-in não resolver o problema, tente substituir o tema ativo por um tema padrão.
Primeiro, conecte-se ao seu site usando um cliente FTP e vá para a pasta /wp-content/themes/. Ela contém todos os temas instalados em seu site.
Clique com o botão direito do mouse para selecionar o tema atual do WordPress e baixá-lo para o computador como um backup.
Em seguida, você precisa excluir o tema atual do seu site.
Basta clicar com o botão direito do mouse na pasta do tema e selecionar “Excluir”. Seu cliente FTP excluirá o tema do seu site.
Agora, se você tiver um tema padrão do WordPress como (Twenty Twenty-Two ou Twenty Twenty-Three) instalado em seu site, o WordPress começará a usá-lo automaticamente como tema padrão.
No entanto, se você não tiver um tema padrão instalado, precisará instalá-lo manualmente usando o FTP.
Se isso corrigir o problema, você deverá examinar o arquivo functions.php do tema. Se houver espaços extras na parte inferior do arquivo, você precisará removê-los e, às vezes, isso resolve o problema.
Se você estiver usando uma função mal codificada no arquivo functions.php do seu tema, isso também poderá causar o erro de tela branca da morte.
Considere a possibilidade de baixar uma nova cópia do tema a partir da fonte e instalá-la manualmente usando FTP.
6. Ativar o modo de depuração para detectar erros no WordPress
Se nada tiver ajudado até agora, a próxima etapa é ativar a depuração no WordPress. Isso manterá registros de erros que lhe permitirão ver que tipo de erros estão sendo emitidos.
Basta adicionar o seguinte código ao seu arquivowp-config.php:
define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );
Depois de adicionar isso, a tela em branco passará a ter erros, avisos e notificações. Eles podem ajudá-lo a determinar a causa raiz.
Se não houver nenhum erro, talvez seja melhor verificar o registro de depuração.
Basta acessar a pasta wp-content em seu site usando um cliente FTP. Lá, você encontrará um novo arquivo debug.log que contém um registro de todos os erros, avisos e advertências.
7. Limpar o cache do WordPress
Às vezes, você pode ter acesso ao back-end, mas o front-end do site apresenta a tela branca da morte.
Isso pode acontecer por causa de um plugin de cache. Nesse caso, basta esvaziar o cache do WordPress.
Consulte nosso guia sobre como limpar o cache no WordPress para obter instruções detalhadas.
8. Corrigir o erro de tela branca para artigos mais longos
Se você tiver uma tela branca da morte somente em uma postagem ou página muito longa, esse método poderá funcionar.
Esse truque basicamente aumenta a capacidade de processamento de texto do PHP, aumentando o limite de recursão e retrocesso. Você pode colar o código a seguir em seu arquivo wp-config.php:
/** Trick for long posts */
ini_set('pcre.recursion_limit',20000000);
ini_set('pcre.backtrack_limit',10000000);
Entendemos que esse é um erro muito frustrante e esperamos que um dos truques acima tenha corrigido o problema para você.
Talvez você também queira ver nosso guia de solução de problemas do WordPress, que ensina as etapas que você deve seguir para detectar e corrigir problemas do WordPress por conta própria, ou nossa seleção de especialistas dos melhores provedores de hospedagem gerenciada do WordPress.
Se você gostou deste artigo, inscreva-se em nosso canal do YouTube para receber tutoriais em vídeo sobre o WordPress. Você também pode nos encontrar no Twitter e no Facebook.
Syed Balkhi says
Hey WPBeginner readers,
Did you know you can win exciting prizes by commenting on WPBeginner?
Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
You can get more details about the contest from here.
Start sharing your thoughts below to stand a chance to win!
Dagoberto says
I need to downgrade 3.9.2 to 3.9.1.
Sylvester Lapisang says
Thanks for the post, deactivated all the plugins and it worked, Zopim Chat was the problem
Robbie Davidson says
Deleting WP Super Cache Plugin solved the problem for me.
wohfab says
It was a crashed functions.php for me (desptie I did not change anything o.o) – THANK YOU SO MUCH!
Aleksandar says
Great tips. In my case (WP v.3.5.1) problem was plugin wp-super-cache. I just delete it and all works ok. I didn’t have time to update and upgrade instalation and plugins.. So maybe this helps.
Chris says
Thanks, both removing plugins and changing themes to default worked for me. but my prob is i can’t activate my plugins. it’ll just open another white screen of death. all plugins.
Hans Haupt says
Thank you so much for your post.
I tried updating my theme and was met with the ‘White Screen of Death’.
I took your advice to delete the problematic theme from the site cPanel and ‘presto’, I was able to log back into wordpress and change the theme to one that works.
Bryan Myers says
Here’s something else to look for- make sure you close out the php tag on the page information block (not sure of it’s real name) at the top of your template page. doh.
Kaveh says
Thank you so much
Your instruction helped me fix my problem
tnx again
bashar says
Thank you so much.. Problem is solve.
Really loving wpbeginner.com
Tommy says
Hey all I had this problem too and found a solution. It seemed to happen from updating from 3.71 to 3.72.
Ok so I tried the following:
rename plugin folder
delete theme
change memory in config file
report errors in config file
I then saw the error:
Parse error: syntax error, unexpected $end in /home/public_html/wp-includes/cron.php on line 247
I checked the cron.php and it looked like loads of the code was cut off because it endee with a comment. So I uploaded a new cron.php file from wordpress and it worked.
I hope this may help others who have this issue.
Thanks
vincent says
Hi, as simpler way is to manually disable all plugins via PhpMyAdmin http://perishablepress.com/quickly-disable-or-enable-all-wordpress-plugins-via-the-database/
Mike says
It’s the first time I write here. In my case, everything is blank, I can’t even log in with
It is still under construction, so I just uploaded a new theme and all went blank.
I know I have to revert the theme to the “twenty twelve”, but how? If I can’t even log in.
any help?! THANK YOU
WPBeginner Support says
Connect to your website using an FTP client, go to /wp-content/themes/ directory and delete the theme you just uploaded. If your webhost offers cPanel, then you can use file manager in cPanel to delete the theme.
Administrador
Jay Lawrence says
Here’s another way to get WSOD! My template, from Yoo Themes, generates a ‘cache’ directory. I accidentally filled the drive with this website causing a zero byte cache file.
root@www:/var/www/wp-content/themes/yoo_vanilla_wp# ls -l cache/
total 32
-rw-r–r– 1 www-data root 25 Mar 13 16:41 index.php
-rw-r–r– 1 www-data www-data 0 Mar 13 16:43 xml-9ae22c153220f9eda980e5ec3b598954.php
Delete the “xml*.php” files in here after you’ve cleaned up your drive … back in business.
That only took a couple hours of hunting – groan.
Ope says
Sorry i deleted the xml.php file but it still came back the moment i refreshed the wp-admin page. yet WSOD persist. Any help. am using a yoo theme too
Michelle says
I have this White Screen on my website, have tried EVERYTHING and nothing working. I cannot access my wordpress login or admin page. It is a new website, so I dont mind wiping it clean and starting again, but I have tried to upload a fresh install of wordpress 3 times and it keeps crashing dreamweaver. Is there any other way I can fix this?? Need help Please
Aamna says
I am a subscriber of your site and my client is also seeing the white screen of death
I have used all the fixes but still no success
What I fell is that I think my clients site’s wp-content has unnecessary folders like
1- backups (files in this folder are ( .htaccess, .backup_running, database_arcproject_co_u.sql)
2-cache
3-uploads(it has many folders of images)
Please tell me what should I do?
Thanx
WPBeginner Support says
First make sure that your client has a backup. If they don’t have a backup then you need to create one now before you make any further changes.
After that you can start deleting the unnecessary files from wp-contents folder. Try deactivating all plugins by renaming the wp-content/plugins folder to wp-content/plugins.old.
Administrador
Aamna says
I have tried disabling the plugins but it didn’t worked.
Anyways how can i take a backup of the site?
WPBeginner Support says
In case you don’t have access to the admin area, you would first need to make a database backup manually. After that you would need to download all the files from the website, using an FTP client.
AJ says
One of the most common causes of whitescreen is white space at the beginning or end of a functions.php file or other php file. Often when cutting and pasting or simply editing code a line break gets in at the top or bottom and bam!!…
Look before the tag at the bottom.
jd says
i did some testing and have uploaded a new theme to the server and have added no limit on the memory and reinstalled the wp to current one. and what i found out to be an issue is with the SQL data base.. when wp tells the SQL server that i have deleted or updated info it seems to keep everything even the deleted items.. NOw the big question what did i do to fix it. well i went to the data base and erased the whole thing and then renamed it back to the same one and went to my site and enter some basic info that showed up .. and BAMMM no white screen i went and turned on the theme and continued my adjustment and creation
Lea says
Hi,
I took over a WP website for a client and I logged in once, updated the pluggins and since then, I can’t enter the Admin section of WP nor see the website. White screen of death indeed, for both.
I have read in the comments part above that someone had the same issue, which you directed to the article “Locked out of WordPress admin area.” Unfortunately, in that article, you direct the person with a White screen of Death to the “How To fix the WorldPress White screen of death” article, which is this topic here.
So… I am a beginner to WP and I am lost. + my client hasn’t had a website for the past 24 hours.
I would really appreciate some help or re-direction to a tutorial/article that tell me how to actually access my admin page !
Thanks a lot in advance.
Lea
Dum says
Renaming wp super cache plugin directory in “Plugins” folder resoved the issue
abdul aziz says
Brother !!!!!!!!!! Really Thank you, it was theme problem , can you suggest me how to fix this problem with same theme???
Abdul Azzi says
i have followed all steps……… but still having same error..
please suggest me what i should have to do ???
Boby says
Hey, my WordPress page only can visit by me (admin), when i logout, the homepage is white screen. please help
WPBeginner Support says
Try switching to a default theme like twenty thirteen or twenty fourteen. If this does not solve your problem, then disable all installed plugins. Also update your permalinks.
Administrador
Darlo says
Tried to update my blog today and had problems (was using WordPress app for android). Had considered it to be an app problem and reinstalled it before considering to actually check the site (something I should really have done in hindsight). As I have more than one blog hosted on the same site (the other being fine) I started to get panicky. After diving into a net-cafe I managed to find this trouble shooting guide and now I’m back online.
Thank you.
Lark says
I’m working with the Roots theme. Turned on the computer and had a white page. Had no memory of what I had done a few weeks before. Replacing the custom theme with the default theme and then undoing changes to scripts.php and widgets.php worked for me. Wow, simple solution, but sometimes it’s quite hard to see simple troubleshooting through the panic… Thanks so much!
Claudia says
Great help. 1000 Thanks
My issue resolved.
Ian says
Thank you. I thought I’d lost everything.
Cesar Pietri says
Thanks,
It was a great help
In my case solve rename the plugins folder.
Lois Wakeman says
Another cause that I just found (WSOD in site and backend) after upgrade.
Manual upgrade via FTP was interrupted by a lost connection and somehow a file got missed.
I used your helpful instructions to turn on debugging having ruled out themes and plugins as problems, which allowed me to trace the offending file and upload it. Voila!
soeb says
Thanx it was a great help..!
In my case it was functions.php file.
Rhodon says
I had to activate the debug mode, and this is my error:
Warning: require_once(ABSPATHwp-admin/includes/dashboard.php): failed to open stream: No such file or directory in /var/www/domains/rhodon.nl/www/wp-admin/index.php on line 13 Fatal error: require_once(): Failed opening required ‘ABSPATHwp-admin/includes/dashboard.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /var/www/domains/rhodon.nl/www/wp-admin/index.php on line 13
How can I solve this?
Rhodon
Junior says
I had to use the edit phpMyAdmin fix to finally get it to work. Editing the database is never fun but your clear instructions made it easy. THANKS!!!
Thomas says
It was the blank lines in functions.php
Thanks so much!
Finally read it in the comments.
JohnLionFlow says
Same here! Removed the blank lines in my theme’s functions.php file and it worked.
earthora says
I had the white screen on everything, front and backend, was starting to panic. I removed the last blank line in functions.php and I’m all back up and running. How would it get there? I’ve never opened it on this installation?
Christal says
I was able to get out of the “white screen of death” by changing my file name from plugins to plugins-temp, but then my site had reverted back to the old theme, and when I reverted to my new theme (which was installed about a month ago), all of my plugins and widgets were gone! It’s a very basic theme with all of the customizations gone! How do I recover all of this??
Niné says
THANKS A MILLION!!!!
Eric Gitonga says
I had to go into phpMyAdmin and into my MySQL database to drop all the wp-* tables created from a previous WordPress install before I could solve the White Screen of Death problem. It now works just fine.
Ilke says
Hi,
I was very happy with your advice once about a year ago with a white screen on the entire front-page of a wp-website. Unfortunately, this time (and for another site) it doesn’t work so far.
I extended the memory several times (I’m at 512M now) and changed the auto keys, that didn’t help. Now I renamed the plugins-folder to plugins.deactivated, and I get this error message:
Fatal error: Cannot redeclare _1059195956() (previously declared in /public/sites/www.name.nl/wp-includes/version.php:9) in /public/sites/www.name.nl/wp-includes/version.php on line 9.
Any idea what else I can try?
Thanks for sharing all this useful information,
Ilke
WPBeginner Support says
Try renaming your theme’s folder as well. After that you need to download WordPress and upload a fresh copy of themes folder to your site. WordPress will now fall back to default twenty thirteen theme. Let us know if it worked for you.
Administrador
Ilke says
I did rename the current themes folder and uploaded a fresh themes folder from a new wp 3.7 download. Unfortunately, that gives me a white screen altogether on the front as well as the back office and I still receive the same error-message.
With debug set to true in wp-config I got
Notice: WP_User->id was called with an argument that is deprecated since version 2.1
and a few other deprecated notices as well as a notice that wp_enqueue_script and wp_enqueue_style was called incorrectly, which both refer to the functions.php
This is really starting to worry me. Do you happen to have some other advice still?
Best,
Ilke
Ilke says
I also tried renaming the plugins-folder and uploading a fresh one. And I cleared the cache. Still I get the same error-message. Since (with debug set to true on wp-config) I get Notice: undifined index-messages concerning two plugins, should I delete those?
Puja singh says
Hi, I am facing the same blank page problem for my site . I tried most of the mention step
Disable all plugin
Activate the default theme.
increase the memory limit to 128 MB.
but no luck, any help will we appreciated.
suneel says
Life saving tutorial…
Thank u very much
Justin says
Thank you. I seem to get it when I’ve been making lots of updates to my site, then I get locked out and have to wait. A memory issue would make sense. Time to clean out a bunch of unused plugins.
Michael Lambertz says
Another reason can be false permissions… I tried to copy a wordpress directore via unix command cp -R, and after that all copied files weren’t in the group www-data. chgrp www-data wordpress_dir/ -R did it for me
Jacob Worsøe says
I have periodically white screens on both frontend and backend. The white screens occur in a completely random pattern. Are the recommendations the same in my situation or do they only apply to more permanent issues?
Editorial Staff says
Yes. It seems like you’re site is running out of memory because of a process that’s being ran. So the process is the same.
Administrador
Hossein says
thank you soooooooooo much, my problem solved, it was because of blank lines in my functions.php
LC says
I can’t even enter the Admin section of WP. I get the blank page. What should I do?
Editorial Staff says
Read the article.
Administrador
maria says
it does not say how to get into your admin if you are blanked. out
WPBeginner Support says
We have a guide on what to do when you are locked out of WordPress admin area.
Rosie says
Thanks, this was useful. I had the white screen on the live site, but WP admin was fine. I use WP Super Cache and I cleared the cache with no effect, then deactivated all plugins, and when I’d tried everything else I suddenly thought of the expired cached pages.
If you use WP Super Cache you have to delete the expired cache too. That worked right away. Then I set my garbage collection (on the Advanced tab) to hourly instead of daily, to try to prevent it happening again.
Tom B. says
Hello .. thought I might add 2cents,
I’m using WP Super Cache too and often crashed to White Screen. Looked at the wp-config.php file and found they were putting their instructions above the SQL allocation in the script, so I moved them down and added the ‘default Memory Limit’ tweak and now my site http://webinardatabase.com/ smokes!
REF:
First save a unmodified copy of wp-config.php to your HD.
Open your wp-config.php, which is located in the root WordPress directory.
Locate the WP Super Cache code (their code is obvious –three lines- the fourth is a duplicate, but I left it), and move them down (I put mine above the SALTS).
Then add the following line: define(‘WP_MEMORY_LIMIT’, ’64M’);
Just BEFORE the super cache, seemed logical.
And save, check performance.
IDK, I think this is a bug. Made no sense to be allocating cache before opening the SQL database.
Worked for me. Prost! — Thanks Wpbeginner.com
PS: Just noticed the post below, WP Super Cache requires permalinks be set to post name, this error appeared on a fresh install. 2 more cents.
Tom B. says
Follow-up.
Had to kick WP Super Cache to the curb.. too buggy.. Gone with W3 Total Cache.
Lone Watie: We thought about it for a long time, “Endeavor to persevere.” And when we had thought about it long enough, we declared war on the Union.
Union = WP, really is this the answer?!
Tom B. says
Ps: Once the plugin is deleted, return to wp-config and manually remove WPSC lines.
Really, no, really!?!
Glenn "TheeMahn" Cady says
Tom, I would like to personally extend a much deserved thanks.
My wpconfig had define(‘WP_MEMORY_LIMIT’, ’64M’); after supercache, moving it above has closed my “White screen of death issue.” I had been refreshing for months. The site now seems fairly snappy.
Thanks again Tom,
TheeMahn
Jacobus says
Personally I haven’t had this problem, yet, I have the problem that I have to reset my permalinks all the time because of endless redirects. Drives me crazy. Every time I publish a new post on my blog I have to set the permalinks back to standard and then back to post name. Do you know if this is host related or plugin related?
Editorial Staff says
IT definitely sounds like a plugin issue.
Administrador
Manish Anand says
Yep, turning on Debug option helped. It was incomplete uploading of query.php file.
Thanks
Joel Andrew Glovier says
Here’s another suggestion when none of the above works, try flushing your rewrite rules cache.
I had a single page on my site returning as a blank page, and tried almost every solution above, as well as some other things (like installing Debug Bar plugin, etc) to no avail.
I was able to narrow it down to what I assumed to be a premalink issue, however, since the page had been working before, and stopped working; and also because even when I used a different page template it still was not working properly (I had prior to that assumed to had to do with my custom wp_query in that page template).
So I started investigating the WordPress rewrite system, and came to find out WordPress keeps a cache of all the custom page slugs and rewrite rules. (more about that here: http://codex.wordpress.org/Rewrite_API/flush_rules and here: http://codex.wordpress.org/Function_Reference/WP_Rewrite)
I also found that this method is used to flush the rewrite cache:
$wp_rewrite->flush_rules();So I tried just adding it to the second line in my functions.php file, and after one page refresh the page contents showed up again.
IMPORTANT: make sure to remove the method after using it once, as there are some costly performance hits associated with leaving that code in your file. You should only need to use it once to resolve the issue, however.
Editorial Staff says
Saving the permalinks settings again will also flush the rewrite rules from our understanding. Thanks for the suggestion about this
Administrador
Joel Andrew Glovier says
Yeah, but that didn’t work in my case. In fact, normally you don’t even have to save the Permalink settings page, just visit it. But in my case that neither visiting, nor saving, nor chaning to another setting and changing back worked.
But actually I discovered it was something much more obscure, and the flushing was only a temporary band-aid.
Turns out I had a conflict between a page with the title/slug of “team” and a custom post-type with the rewrite slug of “team”. The custom post type ended up winning out, except when I put the rules flush in place, in which case it stopped it from winning out.
But the real reason I was getting the white screen was because when the custom-post type slug was winning out, it was defaulting to rendering the page with the archive.php file, which I had created (as my theme is from scratch), but not put any markup in yet. The file was completely blank, hence my white screen.
Womp womp womp wanhhhhh.
Editorial Staff says
Yup that would do it. We learnt that the hard way by looking at one of our user’s themes.
Christian says
!!IF YOU TRIED EVERYTHING THIS WILL WORKS!!!
Nothing else could even make a change in the BLANK PAGE.
I put that code an recivied a error, after that I removed it and the website was online again!
I was about to broke my laptop hahahha
Jonath Lee says
Whenever you’re testing themes or plugins, always leave a tab for “Themes”. In case of WSOD, you may still able to activate the default twenty eleven themes.
Editorial Staff says
That doesn’t work if your admin is also locked. The next screen will just return a white screen of death too.
Administrador
Jonath Lee says
It could? May be I haven’t reach the Admin Lock level so, I guess we should leave the tab for the phpmyadmin page instead +_+
Johnny says
Damn! Just seen the section in the article about the functions.php file – oops! Oh well it will teach me not to read so quickly!
Johnny says
Another ‘gotcha’ is whitespace below the closing ?> in your functions.php file. I got this once a while back and deleting the whitespace below it solved the problem. This can also cause a white screen after hitting the publish button as well.