No, without access to WP Admin you would need to rename the folder, but as you have no access to the filesystem this option is not feasible either. The only remaining option is to connect to the database directly, assuming you know the login details from wp-config.php and the database is configured to allow this. … Read more
3,840 cronjobs with no action!
Running xDebug and NPM at the same time?
wp-includes/general-template.php:2102 is the function wp_admin_css(). On the login page this function is called in login_header(). Your theme or some plugin trys to send an HTTP header after that, probably during the actions login_enqueue_scripts or login_head. wp-includes/option.php on:569 is in function wp_user_settings(); a cookie is set here. Cookies are HTTP headers, so that cannot work when … Read more
They recommend putting it into the wp-config.php file. You can read more about it from the codex Editing wp-config It is quite a long document but the error info is found at 2.15 Configure Error Logging
Any messages you are seeing with the debug output should be resolved. These often point to holes in the current logic within your theme. If your goal is to submit the theme to the WordPress Theme Directory you have to resolve any PHP errors, warnings, or notices for the theme to be approved. Themes must … Read more
This could be output a ton of different places and ways, but judging on what you re saying, and that you can’t see anything in your header.php, check your theme functions.php. Look for something along the lines of this: dirname(__FILE__); pathinfo(__FILE__, PATHINFO_FILENAME); SCRIPT_FILENAME If no luck still, check index.php and then check mu-plugins folder for … Read more
IMHO WP_DEBUG allows to enable display of notices during development. If you look at the core file default-constants.php you see this : if ( !defined(‘WP_DEBUG’) ) define( ‘WP_DEBUG’, false ); So I don’t see why you should set it to false again in wp-config.php. Regarding your issue just delete the line, WP_DEBUG should never be … Read more
It is not necessary to delete it but if you want to save your space then you can delete it. Actually when we turn on the debugger then debug.log file created. It contains the warnings and errors of the code. May be your development team have renamed it with debug.log.old. You can delete it or … Read more
debug.log is exactly what it sounds – it’s just a file that contains log information for debugging purposes. You can easily delete it and without any fear. But… Debugging should not be turned on on production site – it’s a security problem. If your debug.log file is so big, then your site has many problems. … Read more