Plugin Support
Yurii
(@yuriinalivaiko)
Hello @cari18
Ultimate Member is compatible with WordPress version 6.9. It is tested with both 6.9 and 6.9.1.
This may be because of a conflict with the third-party plugin or the theme. We need more information to resolve this issue.
Can you please get error details from the debug.log file? This is a file where WordPress collects detailed information about all issues if a debug log is enabled. Follow instructions in this article to enable logging: How to enable debug logging. Are there “PHP Fatal error” or “PHP Warning” records in the log? Please send us error details from the log.
Please also look at the browser console. This problem may be because of the JavaScript error. Open the browser developer tools (press the “F12” key in the Chrome or Firefox browser) and go to the “Console” tab. Reload the page and reproduce an error. Are there errors in the console?
Regards
Thread Starter
cari18
(@cari18)
Thank you Yurii to help finding out this issue.
I activate logging but none PHP error was found there.
On the other hand there are errors in console.
Do you understand what does this means?
Plugin Support
Yurii
(@yuriinalivaiko)
Hi @cari18
The PHP file post.php is loaded as the JavaScript file. This is a serious mistake. This should never happen. PHP and JavaScript have different syntax. Trying to use a PHP file as a JS file will inevitably result in an error.
You should investigate why the post.php file is loaded as a script and fix this. Try to update all outdated plugins. Try to make a conflict test to narrow down the problem.
Regards
Thread Starter
cari18
(@cari18)
Thanks a lot Yurii for your feedback.
The problem stemmed from certain core scripts that were interfering with Gutenberg’s proper functioning. These scripts have been disabled in the functions.php file.
add_action(‘current_screen’, function( $screen ) {
if ( function_exists(‘use_block_editor_for_post_type’) ) {
if ( isset($screen->post_type) && use_block_editor_for_post_type($screen->post_type) ) {
remove_all_filters(‘script_loader_tag’);
}
}
});
It seems to be a bug in Ultimate Member. Do you agree with that?
Plugin Support
Yurii
(@yuriinalivaiko)
Hi @cari18
This does not explain why the PHP file is loaded as a script. Ultimate Member does not add callbacks to the script_loader_tag filter.
But I see another problem. You use the script_loader_tag filter wrong. This filter is not intended to disable scripts. See description of the script_loader_tag hook here: https://developer.wordpress.org/reference/hooks/script_loader_tag/. If you want to disable specific scripts you should use the wp_deregister_script or wp_dequeue_script function.
Furthermore, it is not recommended to use the remove_all_filters function. This is too rough and uncontrollable. Use the remove_filter function instead. With this function you can specify a callback you want to remove.
So, don’t use a code like remove_all_filters(‘script_loader_tag’).
Regards
Thread Starter
cari18
(@cari18)
Yes I agree, I’ll transfer you remarks to the developers that support us.
I would like to inform Ultimate Member developers about this issue but as we use the free version we cant post any question to them 😒.
Plugin Support
Yurii
(@yuriinalivaiko)
Hi @cari18
An error shown on the screenshot you attached (https://docs.google.com/document/d/1ZvSM_OzHItiLkiKzkShLmTa29f8Y9aZZ/edit) can not appear because of the Ultimate Member plugin. This error occurs because of another plugin or issues in your custom code. We can’t influence this.
Regards
Thread Starter
cari18
(@cari18)
Ok Yurii we’ll investigate in this direction.
Thznk you
