• 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!
  • 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.

Issue comment interpreted

creale

New Pleskian
Hi,

I'm on a Hosting resseler plan by OVH...

And i had transfer one of my website, but on this server the commented line of my code are interpreted !

My browser write me an error on a commented line of my code. and when i delete those commented lines the process go right until next problem.

Any idea of what's wrong with my plesk configuration ? ( the basic ovh configuration by the way)

Thank you
 
What exactly do you mean by "commented line of code"? Could you give an example, please?
 
the php line which are commented, like : /* My code line */

My 298 line is in a commented bloc of code, and i have this error :
Parse error: syntax error, unexpected 'endif' (T_ENDIF) in /.../header.php on line 298
 
Hard to say, why that is happening. The underlying error must be different, e.g. PHP short open tags might be turned of, yet used in the code. It is very likely a simply php.ini configuration issue or actually a code error, e.g. the opener of the PHP code might be mis-formatted or the character set might be wrong. I'd also suggest to check the first bytes of the file, maybe additional bytes were added before the first opener, leading to a misinterpretation of following code. Very unlikely a Plesk issue or a PHP library issue.
 
Ok thank you for your quick answer ... i will check ....

You have to know that this website works perfectly on another ovh hosting :(

I will take a look and i willl tell you
 
Hi creale,

You have to know that this website works perfectly on another ovh hosting
... only because you have different "error reporting" or "display_errors" settings in your domain specific PHP - settings, it doesn't mean, that your code has no mistakes. :p

I strongly assume, that when you compare your PHP-handlers and the settings "error_reporting" and "display_errors" in each corresponding php.ini, you will notice differences. :)
 
Back
Top