Can't add or remove plugins since 1.8.0
See original GitHub issueHi
After an upgrade from 1.7.5 to 1.8.0, I can’t deal with plugins anymore from the plugin manager into the admin panel.
Each time I try to add or remove a plugin I got that error message:
An error occurred while uninstalling the ep_activepads
ENOENT: no such file or directory, rename '/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame' -> '/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192'
And that error into the log which says the same things
{ [Error: ENOENT: no such file or directory, rename '/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame' -> '/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192']
cause:
{ Error: ENOENT: no such file or directory, rename '/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame' -> '/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192'
errno: -2,
code: 'ENOENT',
syscall: 'rename',
path:
'/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame',
dest:
'/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192' },
errno: -2,
code: 'ENOENT',
syscall: 'rename',
path:
'/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame',
dest:
'/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192' }
Error: ENOENT: no such file or directory, rename '/var/www/etherpad_mypads/node_modules/.staging/ep_etherpad-lite-629fb491/node_modules/@babel/code-frame' -> '/var/www/etherpad_mypads/node_modules/.staging/@babel/code-frame-525bc192'
And indeed, the plugin activepads is still there.
I do not have this directory node_modules/.staging
, but if I add it, I have the same error and the directory is removed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Unable to remove old plugins in ES 6.2.0 with elasticsearch ...
As a workaround, you can downgrade to 6.1.3, remove the plugins, upgrade, and reinstall your plugins. I know this is terrible, but this...
Read more >Maven plugins can not be found in IntelliJ - Stack Overflow
Show activity on this post. Run a Force re-import from the maven tool window. If that does not work, Invalidate your caches (File...
Read more >I cannot install/uninstall/update plugins, update OctoPrint, or ...
A fix is available and will be released with OctoPrint 1.8.0. In the meantime please downgrade pip to 21.3.1 which still works fine...
Read more >How to Uninstall WordPress Plugins Cleanly - YouTube
In today's video, we'll learn how to uninstall WordPress plugins cleanly. ... Your browser can't play this video. Learn more. Switch camera.
Read more >1613696 – yum-plugin-remove-with-leaves does not work any ...
Description of problem: yum erase --remove-leaves <package-name> fail to remove dependencies. Version-Release number of selected component (if applicable): 1.1.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@maniackcrudelis I suggest you read back through this thread.
I provided debug steps to isolate the problem, you refused to do them.
We provide free software and free support, saying “Next time I have an issue with your app, I won’t forget to not ask…” is not how I expect people in our community to behave when we have tried our best to help you.
It sounds like when you used the tarball it didn’t overwrite your
src/package-lock.json
and that’s expected behavior. Look at the docs, they clearly state how to install and maintain a site. You took a route (of using the tarball) which may seem sane/sensible but has this exact caveat where the update route is somewhat different (running up to 1.8).You will notice that https://github.com/ether/etherpad-lite/blob/develop/src/package-lock.json is included in the develop branch so if you followed the docs you wouldn’t of had this problem. Moving forward we will have better support for file based upgrades and I can only apologize that we didn’t have the foresight to think people would do installations that didn’t follow our documentation. We forget not everyone is a developer and prefers Github over downloading .tar.gz so our bad on that 💃
So please, follow the docs, be polite and let us try to help you. Gracias!
Thanks for the support… Next time I have an issue with your app, I won’t forget to not ask…
For those who have that issue, apparently to remove
src/package-lock.json
solve the problem.