Issue PHP Composer - missing

[ViaHosting]

Once I put the composer.json file at /httpdocs
and the Plesk GUI found the file, it stores this information.

If I delete /.composer folder and /httpdocs/composer.json ,
the PHP Composer Extension gives an error.



How do I clean this information in Plesk to force extension to rescan domain ?

 

[littlefrog]

here we are 4 years later - no rescan function yet. has cost me many hours of development time trying to create a workaround when this happens.

 

[Peter Debik]

As you already saw on Ability to trigger folder rescan for Composer only eight users voted for it during three years. It is just not so popular, so other features which have many more votes have been chosen for development first.

 

[littlefrog]

as someone who builds saas companies and owns one myself, you and i both know that it is extremely unreliable to use a voting systems like this to determine the direction of software. i have used plesk 20 years and not once has the 3 owners ever reached out to me asking about features i struggle with or would like to see done.
That is the approach we use and have found huge success with it. I bet you less than 1% of plesk admins even know about the poll system.

 

[amstec]

This is needed. Does anyone know what a work around is?

 

[trobie]

This worked for me.

How to change in the PHP Composer extension the path of the composer.json file? - Support Cases from Plesk Knowledge Base

How to change in the PHP Composer extension the path of the composer.json file? - Support Cases - Plesk Knowledge Base

www.plesk.com

 

[littlefrog]

Yes, that works if it has already scanned your website and sees that there are multiple folders with a composer.json file.
If you have scanned and then add a folder with a composer.json file there is no way to have the website rescan for composer.json