Arch devs, After the 'sodium' issue with the original 28 update, there was a request that we make known Nextcloud issues so if they are packaging related they can be fixed. In today's 28.0.2 update, the "Rescan" option is no longer presented in Admin Settings -> Overview if you have disabled integrity checks in config.php which is routinely needed on update so that the .htaccess file can be rescanned and hash updated if you have installed to a directory under your document root and needed to adjust the caldav/carddav paths in .htaccess. Without the "Rescan" option available, this way of updating the .htaccess hash to remove the warning no longer exists (it still works, you just have to save the Rescan URL before disabling integrity checks and then manually run it even though the Rescan option isn't provided) If this is a packaging issue, it needs to be fixed so the hash update can function without saving/manually running the rescan. It was there and worked fine in 28.0.1, but is gone in 28.0.2. I've also asked for help on the nextcloud forum in case this isn't a packaging issue. Further details in that post: https://help.nextcloud.com/t/nextclout-28-0-2-removes-rescan-option-when-int... -- David C. Rankin, J.D.,P.E.