-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add mjs to upgrade guide for admins #11429
Comments
I think you meant add it here: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_28.html (for the admin guide not dev guide) Since there's already a small note about in in the NC27 upgrade guide we can probably lift that as a base: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_27.html Maybe expand it a bit too - to make it clear it's applicable for those not using the .htaccess approach too? Maybe even add a note about common symptoms (e.g. activity and logreader sections not functioning) P.S. This is mostly out of scope, but made me think of it: Maybe we should also consider adding a "Commonly Reported Problems" section in the manual that we can update throughout the release cycle. The timeless (evergreen) items here could move to a permanent FAQ section while the release specific ones not get carried forward. |
This proposed PR could help too... at least as long as the setup checks never end up requiring |
I do not think we need this in the 28 update guide as it was introduced in 27 and already included in the update guide, so we would copy it from 27 to 28? |
Ah right, the admin docs are better suited. I followed the link on the old GitHub admin&dev issue which lead to the developer docs only. Hmm, the entry for NC27 is probably a little too small/unclear, referring to Nginx config only. This was not an issue with NC27, but with NC28 this change is just mandatory for all webserver setups which do not use |
Thanks for helping improve our documentation!
Nextcloud 27 added support for
mjs
and with Nextcloud 28, some core components started to make use of it. This was a breaking change for webserver setups without Apache2 or when not making use of.htaccess
, since requests to those files were rewritten toindex.php
. It would be beneficial to add a hint for admins to the upgrade guide of the docs: https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.htmlNotes
Protip: If you want to help move things along (or just help out in other ways too) here are some suggestions:
The text was updated successfully, but these errors were encountered: