• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue JS files require <script> tags to format properly this causes a syntax error when included.

Sam Dean

New Pleskian
Current specs/versions
CPU Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (2 core(s))
Version Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
OS CentOS Linux 7.4.1708 (Core)

The code editor treats *.js files as if they were *.html files. So when writing js you get horrible auto tabbing and line breaks and it can't style variables correctly.
upload_2018-4-12_11-10-49.png

if you add "<script> tags it works fine. However including a *.js file with <script> tags will give you a syntax error and the file won't be included.

Adding <script> tags is a temporary fix while editing but is not ideal.

Sam
 
Adding "//<script>" at the start and "//</script>" at the end does resolve this issue.
The code editor see's the "//" as characters as HTML to print out to the display and then the <script> tags properly format the document.
Then when the file is properly interpreted as JS in the browser or else where the "//" comment out the <script> tags.

Sam
 
Back
Top