That message is a result of your server throwing a 503 error and the WordPress Heartbeat API catching that error. See https://core.trac.wordpress.org/ticket/25660 for the background on the fix that WordPress introduced to save offline edits. Things to check on your computer are if WAMP is actually running when you’re getting this message (check the status … Read more
Ok, I think I have an idea what is going on. The list of notices to display is retrieved by get_settings_errors() ( source ). This function reads notices from global $wp_settings_errors unless there is settings_errors transient set, which trumps global var. When settings are saved there is check for no setting errors and if so … Read more
WordPress by default hide errors for ajax request call. This can be confirmed from the source file wp-includes/load.php#L352, here: if ( defined( ‘XMLRPC_REQUEST’ ) || defined( ‘REST_REQUEST’ ) || ( defined( ‘WP_INSTALLING’ ) && WP_INSTALLING ) || wp_doing_ajax() ) { @ini_set( ‘display_errors’, 0 ); } See the function wp_doing_ajax() is being used in the conditional … Read more
As mmm stated: in which file appears the first notice? Wherever the notice is mentioning the location of this deprecated function (path/to/some/file.php), you would insert the following just below the <?php tag which starts off the file: error_reporting(0); I’ve tried the above functions you mentioned and inserted them in my wp-config.php when I experience something … Read more
Where (or if) errors are logged is dependent on your php configuration. You can control some of this via your WordPress wp-config.php file. See Configure Error Logging in Editing wp-config.php.
Remove the ‘fastcgi_intercept_errors’ argument from you configuration. It’s unnecessary since ‘error_page’ declares 404 errors, which should be handled by index.php, which will trigger PHP-FPM to handle it, and WordPress to present your theme’s 404 page. It seems counter-intuitive, but ‘fastcgi_intercept_errors’ is actually causing PHP not to handle the error page.
You’re probably talking about theming wp_die(), which is the function that produces those grey error pages with a white box of text in them. For a plugin solution, you could try this plugin, which says it does what you want. Not sure about version support though–it says it only works up to 3.1.4. For a … Read more
Change line 93 from add_filter(‘manage_posts_custom_column’, ‘manage_posts_custom_column’); to add_filter(‘manage_posts_custom_column’, ‘manage_posts_custom_column’, 10, 2); The fourth argument specifies how many arguments the function manage_posts_custom_column accepts (one by default). Codex: add_filter()
Answering my own question: As suggested by WebElaine I created a completely new block to fix the problem. To make this task easier, I used create-guten-block by Ahmad Awais, which is pretty easy to set up. In init.php I made sure to enqueue my JavaScript and extra CSS for the frontend. This should be straight … Read more
First do not use 777, change it back to 755. Second you need to add the proper group permissions most likely to the same that Apache is running under. To find that out try: ps aux | grep apache You will see the Apache user group on the left. Now change your WordPress folder to … Read more