Hi @aloarch,
It’s odd that the issue still exists even after a conflict test. Did you try switching the theme to a default WordPress theme during the test?
Enabling Debug mode should help to have a better idea regarding what might be causing it.
To enable debug mode, open your wp-config.php file located in your root directory, and look for define(‘WP_DEBUG’, false);. Change it to:
define('WP_DEBUG', true);
In order to enable the error logging to a file on the server you need to add:
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
define( 'SCRIPT_DEBUG', true );
After making the above changes, please try to replicate the issue once again. This will cause the related errors to get saved to a debug.log log file inside the /wp-content/ directory.
You can check the debug.log file and see whether it provides more details regarding the error.
If you aren’t sure on how to check the debug.log file, you can share the file in the next reply via Google Drive, Dropbox or any such cloud services so that we could check the logs further if needed.
You can find more details about debugging here.
Please let us know how that goes, have a nice day.
Kind Regards,
Nithin