Hi @amakraai,
The plug-in has been tested with the latest version of WordPress. Can you tell me more about What issue are you getting? Can you provide some errors logs when WordPress debug mode is enabled? Have you also tried checking for plug-in conflicts with other plug-ins as well? Look forward to helping you with this. (I’ll mark this thread resolved as per the title – since we have tested to the latest WordPress version and are compatible. I’ll be here to answer your follow up questions and help troubleshoot)
Hi @melliesou
When it broke my site, I saw this:
Warning: This plugin has not been tested with your current version of WordPress.
So I thought that’s why. I’m on WP 5.2
After I updated to WP 5.2 a week ago, I received complaints that people cannot access the plugin to write or read responses to their tickets, as it tells them just “page not found” or a blank page, or even 401 and 500 errors.
So I checked it out and found that my template also sometimes is showing then missing.
I myself could not even access the admin area, and had to rename the folder to deactivate it. That was the only way I could access admin area.
So once inside admin, I renamed the folder back to original, and could deactivate it from admin area.
Once deactivated, my site is accessible without problems. Then I activate the plugin again, everything seems to work, for about a few hours, and all of a sudden, same old same story all over.
Thats when I checked and saw: Warning: This plugin has not been tested with your current version of WordPress. under plugin details, and thought that may be then the problem.
Hi @amakraai,
The “tested with” value in the package isn’t updated to the latest version number; however, your plug-in version has indeed been tested with the latest WordPress. In order to better diagnose the issue you have, please enable debug mode, as well as deactivate all other plug-ins, except for Awesome Support, and the try re-enabling plug-ins one-by-one until you get the error.
Please let me know how that goes, I’ll be here to follow up.
HI @melliesou
Thank you, debug mode showed some errors, I hope I solved correctly, everything looks okay now, thank you
Hello @amakraai,
Glad you found the problem following the debug mode and disabling the other plug-ins. Happy to hear that it’s sorted out.
