• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

PPWSE image browser paths ERROR

M

multimediahouse

Guest
Running Plesk 8.3 and Plesk Professional Web Site Editor. I have this annoying problem: when customers use the Insert Image button and browse to an image from a subdirectory, PPWSE makes an absolute path to the image file. Even a faulty one, at that. For example:

http://domain.tld/httpdocs/images/myimage.jpg

Does anyone know if there is a way to modify this behaviour, or are we stuck asking customers to manually remove the "http://domain.tld/httpdocs/" part? Kind of defeats the purpose of having the image browsing feature...
 
Please start by posting in the correct forum. This is the Plesk announcements forum.
 
You must log in or register to reply here.

Similar threads

C
Resolved Error 500 after changing from temporary .plesk.page to a real domain
Replies
2
Views
4K
celebrir
C
I
Question media sync error on woocommerce
Replies
0
Views
3K
ilfriz80
I
D
Input How to run Magento 2 on Plesk Obsidian 18 without Docker
Replies
8
Views
13K
Isolde
I
Denis Gomes Franco
Issue Path error in Amazon S3 extension to Backblaze B2
Replies
12
Views
7K
Denis Gomes Franco
Denis Gomes Franco
Monty
Resolved [PPP-53248] nginx not returning 404 for non-existing files larger than 1023 bytes
Replies
5
Views
5K
Nik G
N
Back
Top