• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Forwarded to devs Non-static method ProtectedDirectoryManipulator::updateProtDirectory() cannot be called statically

si458

New Pleskian
Hi All,

im creating a very basic app which lets me create password protected directorys and set user, upload files etc

im using the Plesk XML API

i have working the create passworddirectory, delete passworddirectory, but i cant get the edit passworddirectory to work?

i just keep getting this XML error
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.9.1">
<protected-dir>
<set>
<result>
<status>error</status>
<errcode>1002</errcode>
<errtext>Non-static method ProtectedDirectoryManipulator::updateProtDirectory() cannot be called statically</errtext>
</result>
</set>
</protected-dir>
</packet>

this is my sample xml i sent to the server
<?xml version="1.0" encoding="UTF-8"?>
<packet>
<protected-dir>
<set>
<filter>
<id>149</id>
</filter>
<values>
<name>/bobby</name>
<header>new header</header>
</values>
</set>
</protected-dir>
</packet>
so im not too sure whats going on or what im doing wrong?
the id is the id i retrieve from the <get> to begin with
and in my example the <name> didnt change, only the header

any help would be amazing!

Kindest Regards

Simon
 
@Kaspar does my example above not replicate it on your setup? as thats all ive done to get the error
My mistake, I wrote my previous post to fast. I meant to say that I was actually able to replicate the issue, with the same error as you encountered.
 
Last edited:
Thank you for report, @si458 . I have created internal request for further review and I will follow-up with more details as soon as possible.
 
The behavior was recognized as a bug identified with ID PPPM-15284. At this point, I cannot provide an ETA for the fix. The same will be introduced in one of Plesk's future releases. You can monitor the change log here. Thank you for bringing our attention to the issue.
 
The behavior was recognized as a bug identified with ID PPPM-15284. At this point, I cannot provide an ETA for the fix. The same will be introduced in one of Plesk's future releases. You can monitor the change log here. Thank you for bringing our attention to the issue.
thats wonderful thank you look forward to when its fixed!
its not stopped me writing my app for the moment thankfully as its just an edit, the enduser can just delete and recreate if needs be as a work around haha
 
Back
Top