Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello,
Can you please test minimal, using a default theme(if applicable) and with all non-WPML and essentials plugins disabled to see if the error persists. If possible make a backup of the site before doing it or test on a staging copy.
In addition to that, I'd like your help enabling the debug mode to help us track the error down, please add the following code to the wp-config.php file:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
After adding the code above, please try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder. If you locate it there, please send us the last lines here in the ticket.
After you send the WP debug logs, we'll analyze them and get back to you with further steps.
If you prefer we can perform those steps for you, for that I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
Once the chat is converted into a ticket it is not possible to return to a chat. You could reach out to us again and ask the agent to transfer the chat to me.
Thank you for sharing the access to the site.
I checked it and I can see that the plugin is enabled at the moment.
Did you manage to fix the issue on your end? If not, what are the steps I can take in order to reproduce it?
Thank you, please let us know.
Mateus
The topic ‘[Closed] Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.