Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
WordPress Toolkit issues after upgrade to 12.5.30
- Thread starter webbing
- Start date
I'm glad you've fixed the issue, Michele. However, it means that we won't be able to understand why it has still happened after we've fixed the underlying problem. If, by any chance, you'll encounter this issue again, could you please file a support ticket and let me know its ID via PM? We would really appreciate that since we want WordPress Toolkit to be a great bug-free tool that helps, not hinders, the business of our customers.
@MicheleB,
In order to have a proper benchmark (read: for testing proper functioning of the WPT), you should be aware that some WP plugins can cause errors (of many kinds).
You should verify whether your issue is still present on a "dummy" WP instance, being a WP installation created via the Plesk Panel.
Some of the (minor) issues with respect to WPT are still under investigation, but the scope of investigation can surely not include the (often badly coded) WP plugins.
Please try to reproduce (if possible) the error on a clean, fresh installation of WP.
If you still encounter some problems, you can also start a conversation with me, so we can have a look what the root cause of the problem actually is.
Regards....
@MicheleB,
Nice to hear.
Note that you should be having a look at the responsible php files, which are probably belonging to a specific WP plugin (or multiple plugins).
If the issue can be associated with specific plugins, then you should be aware that a plugin update can result in the issue reoccurring.
You now have a solution to solve the issue, but it is often better to prevent the usage of badly coded plugins (they are in essence a risk, in many aspects).
Regards....
Nice to hear.
Note that you should be having a look at the responsible php files, which are probably belonging to a specific WP plugin (or multiple plugins).
If the issue can be associated with specific plugins, then you should be aware that a plugin update can result in the issue reoccurring.
You now have a solution to solve the issue, but it is often better to prevent the usage of badly coded plugins (they are in essence a risk, in many aspects).
Regards....
