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.
Forwarded to devs WordPress's Add New (Post & Page) Pages are messed up
- Thread starter 3antarNet
- Start date
Hello, @3antarNet. Thank for the report. I was able to reproduce the issue and determine that the same is caused by ModSecurity and more specifically the rule with ID 942430. I have forwarded the report to our team for further investigation and I will update you as soon as I have more details. For the time being, please exclude the rule in ModSecurity's configuration and you should be able to normally add posts/pages.
Our team confirmed the reported behavior as a bug with ID EXTWPTOOLK-12255. A fix will be released in the upcoming Plesk updates. You may observe our Change log here.
The issue is caused because during "Recommended installation" the rule set configured in ModSecurity by default is "OWASP". The workaround is either excluding the rule following the instructions in my previous message or to change the rule set from Tools & Settings > Web Application Firewall (ModSecurity) to "Atomic Standard".
We would like to thank you once again to bring that issue to our attention.
The issue is caused because during "Recommended installation" the rule set configured in ModSecurity by default is "OWASP". The workaround is either excluding the rule following the instructions in my previous message or to change the rule set from Tools & Settings > Web Application Firewall (ModSecurity) to "Atomic Standard".
We would like to thank you once again to bring that issue to our attention.
Last edited:
Thank you so much, @Sebahat.hadzhi! 
Excluding the rule solved the problem. However, I'm encountering another issue that happened both before and after excluding the rule:
When I try to crop an uploaded image on the image editing page, after I select the area to crop and click "Apply Crop," I receive this error:
"Could not load the preview image. Please reload the page and try again."
Here's a video to show:
Again, this is on a fresh install, nothing has been installed like plugins or themes.
Excluding the rule solved the problem. However, I'm encountering another issue that happened both before and after excluding the rule:
When I try to crop an uploaded image on the image editing page, after I select the area to crop and click "Apply Crop," I receive this error:
"Could not load the preview image. Please reload the page and try again."
Here's a video to show:
Again, this is on a fresh install, nothing has been installed like plugins or themes.
Sorry for double posting, but after I changed the rule set from Tools & Settings > Web Application Firewall (ModSecurity) to "Atomic Standard" as you suggested in your last post, it actually solved the image cropping issue.
Sorry I missed that part in your post. And once again, thank you so much!
Sorry I missed that part in your post. And once again, thank you so much!
Thank you for the feedback. I will inform our developers for that issue as well. I am glad to hear you were able to sort it out by changing the rule set.
Similar threads
