Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
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....