• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Composer Extension not finding json file on Plesk Obsidian

Ewan M

New Pleskian
I recently upgraded my production server to Obsidian after having upgraded my test server. I want to make use of the composer extension. I find when i create a new "website" the composer extension works fine, scans the directory structure for the composer.json file and then works perfectly.

For websites created on previous version of Plesk the composer extension doesnt seem to be able to locate the json file however the directory structure of the sites is completely unchanged (code based pulled from a github repo). SEE BELOW IMAGE. Any ideas how i can get composer to work for these websites on Obsidian? Creating a new website and migrating things is an absolute last resort for reasons i wont go into.

composer on Obsidian.png
 
Having what I think is a similar issue but with new sites. I'm working on a wordpress plugin that has a dependency I'd like to manage with composer. The compose.json file exists in the plugin folder but I get the same 'no applications were found' message.
 
Back
Top