Skip to content

Don't post an error when the theming product name isn't set yet - #2881

Merged
enoch85 merged 1 commit into
mainfrom
fix/theming-product-name-false-alarm
Nov 2, 2026
Merged

enoch85 merged 1 commit into
mainfrom
fix/theming-product-name-false-alarm

Conversation

@enoch85

@enoch85 enoch85 commented Nov 2, 2026

Copy link
Copy Markdown
Member

A new install posts "Sorry but something went wrong" to the admin, with occ config:app:get theming productName failed.

config:app:get exits with 1 if the key doesn't exist, and on a new install it doesn't yet. nextcloud_occ then runs check_command, which posts the notification. It only ends the $(...) subshell, so the install carries on and sets the name on the next line. The read now uses nextcloud_occ_no_check, in the install and in the update.

Also fixes a comment in nextcloud-startup-script.sh that still said the pool is imported with UUID.

Tested with a fake occ that exits 1 for that key, not on a full install: the old line posts one notification and the new line posts none, and both go on to set the name. The original notification was seen on a real install.

occ config:app:get exits with 1 if the key doesn't exist, so on a new install
check_command told the admin that something went wrong. It only ended the
subshell, and the name was set on the next line. Use nextcloud_occ_no_check for
the read.

Also fix a comment that still said the pool is imported with UUID.
@enoch85
enoch85 marked this pull request as ready for review November 2, 2026 08:42
@enoch85
enoch85 merged commit 1e3e285 into main Nov 2, 2026
11 of 12 checks passed
@enoch85
enoch85 deleted the fix/theming-product-name-false-alarm branch November 2, 2026 08:42
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