Replies: 1 comment
-
It would in fact be a great feature, if Craft reads the craft/plugins/ folder on every Settings → Plugins visit, and lists all folders which do not belong to a plugin. That's the only possible user error in the plugin installation process. For everything else I think the plugin developer should be responsible. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If for some reason a plugin won't activate, there has to be a reason. Right now, the reason isn't visible to a user/developer, so we have to guess what's wrong.
Beta Was this translation helpful? Give feedback.
All reactions