SIte is broken

Hi!

This was fixed in 6.4.1, maybe your update didn’t work well? Please try to reinstall the plugin. If you still have the same issue please check error logs for more information about the error and post it here. Thanks!

Kind regards,
Cusmin support

Thanks for your reply,

What process do I use to reinstall the plugin? Do I re download it and replace the plugin via FTP?

and what happens to all of my settings currently in ADMIN?

Any information will be really helpful

Thanks

… also if it does go wrong again, where do I find the error logs please?

Please make a backup of your DB if something goes wrong. After that, you could delete the plugin from the plugins page (or via FTP) and install it again.

It depends how your error logs are organized on your server. On Apache, they are usually in /var/logs/apache2, you would need to check your php.ini for more information. Probably the easiest method would be enabling WP logs temporary.
https://www.wpbeginner.com/wp-tutorials/how-to-set-up-wordpress-error-logs-in-wp-config/

Hi,

Can you please explain what has happened:

1. as per this post my site showed an error (as previously discussed)
I am using 6.4.1 and it has the fatal error on ag-custom-admin/plugin.php on line 1153
2. To get the site working again I changed the name of the plugin in wp-content/plugins via FTP and the error on the site disappeared! (until I had time a couple of days later to backup the site /database and update it again).
3. a couple of days later after backing everything up, I went back into wp-content/plugins via FTP and noticed the name of the plugin had changed back to its original name but there was NO error showing on the site and the 2nd admin login was working perfect again ! phew!

Can you please tell me what happened and how it was possible that the name of the plugin changed back again.

Thanks

Maybe your plugin update didn’t work well for some reason. 6.4.1 contains the fix for the issue, the previous version was the one that didn’t work. Changing the name of the plugin should disable it. Updating the disabled plugin could change its name, not sure. However, it looks like you have the latest version updated and activated correctly, so everything should be fine.