Turns out it’s an issue with “WooCommerce Multilingual & Multicurrency” plugin which is related to WMPL. WMPL is having big issues right now with their products and probably are fixing them at this moment. For example a lot of developers had problems with “WPML String Translation” plugin which caused critical error for websites.
The answer is in the error message – it’s the ‘bbp-style-pack’ plugin. Temporarily rename that plugin folder (in the wp-content/plugins folder) to disable it. Then, after you log in as admin, check the plugin version to see if it is current. It current, delete the plugin – you don’t need that hassle.
I think you can try with this code below. function childtheme_enqueue_styles() { wp_enqueue_style( ‘parent-style’, get_template_directory_uri() . ‘/style.css’, array(), wp_get_theme()->parent()->get(‘Version’) ); wp_enqueue_style( ‘child-style’, get_stylesheet_uri(), array( ‘parent-style’ ), wp_get_theme()->get(‘Version’) // Note you must provide a version into the child theme ); } add_action( ‘wp_enqueue_scripts’, ‘childtheme_enqueue_styles’ );
Something, I do not know what, is resetting my global error_reporting(E_ALL) level to a higher level, thus hiding the errors. Explicitly adding the lower error_reporting in files in question helps show the error.
All pages duplicated like a mirror with critical errors
You can check this: $api_endpoint=”https://url_to_API”; $api_args = array( ‘method’ => ‘GET’, ‘headers’ => array( ‘Accept’ => ‘application/json’, ‘any’ => ‘other’ ) ); $queries = array( ‘your_query’ => 1, ‘another_query’ => 5, ); $api_endpoint = add_query_arg( $queries, $api_endpoint ); $response = wp_remote_request( $api_endpoint, $api_args ); $response_code = wp_remote_retrieve_response_code( $response ) $data = json_decode( wp_remote_retrieve_body( $response ), … Read more
PHP warning $post->ID is null
WordPress Customizer not loading
PHP warning: Undefined array key 2 in feed.php
WordPress error handling is pretty good, but you do need to do a little work to shape this to your needs: I can tell you that the most simple set-up I know is to log errors to the wp-content/debug.log file – using the following set-up in wp-config.php: define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); … Read more