Skip to content

stop installing the issuetemplate app - #2859

Merged
enoch85 merged 2 commits into
mainfrom
fix/remove-issuetemplate
Sep 26, 2026
Merged

enoch85 merged 2 commits into
mainfrom
fix/remove-issuetemplate

Conversation

@enoch85

@enoch85 enoch85 commented Sep 26, 2026

Copy link
Copy Markdown
Member

Provisioning mode tries to install the issuetemplate app on every new VM, and it fails: App "Issue Template" cannot be installed because it is not compatible with this version of the server.

Root cause: issuetemplate is abandoned. The last release (0.7.0, 2020) supports Nextcloud up to 20 and calls APIs that are gone in Nextcloud 35 (e.g. OC_Util::addScript, OC_App::getAppInfo). The installer's max-version sed workaround doesn't help, and if it did, the app would break the admin settings.

Fix: remove IssueTemplate from the provisioning choice, the checklist and the case.

Existing installs: not affected. apps/pico_cms.sh still disables the app on old VMs that have it.

Verified: fresh install of this branch on an Ubuntu 26.04 test container: no issuetemplate attempt in the log, and the other provisioning apps are installed and owned by www-data.

🤖 AI (if applicable)

  • The content of this PR was partly or fully generated using AI

Assisted-by: ClaudeCode:claude-opus-5-5

The last issuetemplate release (0.7.0, 2020) supports Nextcloud up to 20
and calls APIs that are gone in Nextcloud 35. Provisioning mode always
selected it and the max-version workaround fails, so the install only
logged "cannot be installed because it is not compatible". If the
workaround worked, the app would break the admin settings.
@enoch85
enoch85 merged commit bf4d805 into main Sep 26, 2026
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant