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

Forwarded to devs Links to files in logs from subdomain result File Editor error

josephGW

New Pleskian
Username:

TITLE

Bug with file editor from logs in subdomain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

ubuntu 20.04.3 - Plesk Obsidian 18.0.40 update 1

PROBLEM DESCRIPTION

Hello Devs !

Thanks for your answer
I do still have the same problem with ubuntu 20.04.3 - Plesk Obsidian 18.0.40, latest updates.

I thunks it was resolved but nope, it's ok for other kind of files like html but not php.

You'll see it in the screenshot of the log and the error.

Thanks

STEPS TO REPRODUCE

When i have an error shown from xdebug in logs and i want to click to the link for the file to see where is the error it tells me that the file wasn't find in that place.

ACTUAL RESULT

the file wasn't find in that place

EXPECTED RESULT

opening of php file in file explorer

ANY ADDITIONAL INFORMATION

Original forum post where bug where confirmed with screenshot : Issue - Bug with file editor from logs in subdomain

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Is there any news on this bug?
I noticed it's still present in .49 and it still causes some (minor) inconvenience.
 
There seem to be more implications and things to be taken into consideration. The issue is still open any may be resolved in a future update, but there is no ETA yet.
 
Back
Top