Maybe debugging a file can work around the problem:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false ); // não mostrar na tela
define( 'WP_DEBUG_LOG', true ); // escrever debug em um arquivo
@ini_set('display_errors',0);
With the constant WP_DEBUG_LOG
active, debug will be generated in the file /wp-content/debug.log
. This constant is used to see Ajax or wp-cron errors that are not shown on the screen while running the site.
Some time ago, I made a plugin to view that file directly in the Wordpress backend.
If even using the direct debug to a file your website still doesn’t work because of these constants, then you should search your server’s error logs to see if there are any hints of what’s really going on. This solution I present is just an alternative to circumvent the actual error (WP_DEGUB conflict with your server), I did a quick search and found nothing related.
Out of curiosity, did you get a solution or did you find the problem?
– brasofilo
Your answer helped me because I used it as a reference to find another answer that could help me. Only now I can’t remember how I solved it, I remember I based on your answer.
– Diego Souza
If at some point I bump into the solution again, it would be nice to have it registered here. Thanks!
– brasofilo