Those constants do different things. The WP_DISABLE_FATAL_ERROR_HANDLER constant is for disabling the new fatal error recovery feature introduced in WordPress 5.2. This new feature ensures that fatal errors from plugins don’t lock you out of your site, and that front-end users get some kind of “technical difficulties” message, rather than a white screen. The WP_DEBUG … Read more
There’s not one if you didn’t set one up. The codex has a good example of how to do this. <?php @ini_set(‘log_errors’,’On’); @ini_set(‘display_errors’,’Off’); @ini_set(‘error_log’,’/home/example.com/logs/php_error.log’); /** * This will log all errors notices and warnings to a file called debug.log in * wp-content (if Apache does not have write permission, you may need to create * … Read more
It could be that a plugin which blocks I.P addresses or Countries is causing this. Otherwise it maybe a setting in a security plugin has caused this. Seems the message is a custom one. Otherwise it could be something coded into a .htaccess file.
get_term can return a WP_Error object in addition to a falsy value for term not found or an actual term row. You fix this, by adding an additional check: if (!$term) { continue; } Becomes: if (!$term || is_wp_error($term)) { continue; } You should also do this above the get_term_link call. $term = get_term($value, $fieldSettings[‘taxonomy’]); … Read more
This is probably caused by a PHP fatal error occurs while saving the post. The error source is one of your plugins or the current theme, so to troubleshoot, follow these steps: Try to enable the debug log and take a look at the log (usually in: wp-content/debug.log) to see if you can find the … Read more
EDIT I have rewritten your complete shortcode. I’ve tested the code from my original answer, and with your code combined, the output was a bit unexpected. Major modifications I’ve removed category and replaced it with a tax_query (see WP_Query). The reason is, a tax_query can be used for build-in categories and for custom taxonomies, and … Read more
You were right Toscho, it is a plugin called ‘better WP-Security’ I did a search for ‘418’ as suggested in the files I had backed up via ftp and found this: $bwpsmemlimit = (int) ini_get( ‘memory_limit’ ) //if they’re locked out or banned die if ( ( $bwpsoptions[‘id_enabled’] == 1 ||$bwpsoptions[‘ll_enabled’] == 1 ) && … Read more
Whoever wrote your theme didn’t bother to verify the existence of array keys before using them. The error is happening because the key album_tracks_metabox_nonce doesn’t exist in the $_POST array. The line likely should be: if ( !isset($_POST[‘album_tracks_metabox_nonce’]) || !wp_verify_nonce($_POST[‘album_tracks_metabox_nonce’], ‘album_tracks_metabox’) ) { // whatever is in the if condition, likely `return` }
Your functions.php file is outputting instead of returning something, on line 519. Can you post whatever code/functions are around Line 519? EDIT: You have a syntax error in your cpt_Search_category_Filter() function. You have a couple stray semi-colons after closing braces. Change this: function cpt_Search_category_Filter($query) { $post_type = array(‘post’,’business_sold’); if ($query->is_search || $query->is_category) { $query->set(‘post_type’, $post_type); … Read more
The error you are getting is quite specific and tells you exactly what is wrong. Also debug errors are off topic here. Your real issue here is adding an image to the first post only, which you can accomplish with the build-in loop counter $current_post that starts at 0, so the first post will be … Read more