-
-
Notifications
You must be signed in to change notification settings - Fork 672
force installation of Issue Template #2099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Teste and works
|
@juliushaertl I don't know if there's a reason for not fixing this in core(?), but this works as a workaround to get it enabled. Please advice. |
|
@enoch85 As an advice: I suppose |
|
Aah, true, didn't know that |
need to be able to change info.xml, and the `--force` option installs and enables it with the wrong "compatibility".
|
But, it didn't work. :/ |
Strange, thats excactly the usecase it was implemented for... |
Maybe a bug, or it simply doesn't allow enabling when info.xml is wrong? |
|
Don't know... See nextcloud/server#26252 for the PR |
|
I'll merge this for now. |
|
Just tried the force option myself. nextcloud_occ app:install --force --keep-disabled issuetemplate
nextcloud_occ app:enable issuetemplate --force |
Tested and works