• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Invalid characters and page sets (very important!)

D

dedi

Guest
Well, on my installation I had some troubles when I choose Italian language.
Since by default the translation of a title of a page in Business page set contains an hyphen ( ' ), when I changed the title of the page set, it crashed 'cause probably is missing addslashes somewhere. So I had to manually edit the lang.php file and the template file, removing the ( ' ).

So I went to the swsoft demo and saw that there's a js alert that verify the input preventing the use of ( ' ). So I was wondering why my installation (last patched version) doesn't have at least this js (in the hope swsoft will soon release a patch with addslashes on every input field).

Do other users have same problem? (pay attention, If you haven't that js your page set management page will crash and the wizard too, until you'll manually remove or escape that ( ' )).
 
Errata corrige: not hyphen, but apostrophe

How is possible that there's no reply to this post?
With this bug, if you have a demo running, it can be crashed each time a user change the title of a page, using an apostrophe.

Thanks, Paolo
 
We had an issue and sw-soft told us to put the following in a .htaccess file for our client with the issue;

AddDefaultCharset UTF-8
 
Back
Top