CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2022-08-25T21:41:06Zhttps://lab.civicrm.org/dev/core/-/issues/3711Permissions reset on upgrade or configuration change2022-08-25T21:41:06ZAdam WoodPermissions reset on upgrade or configuration changeApplies to CiviCRM running on Joomla.
The permission "See CiviCRM is installed" keeps resetting by itself. This definitely occurs whenever CiviCRM is upgraded (issue observed up to and including 5.50.4) and/or an extension is installed,...Applies to CiviCRM running on Joomla.
The permission "See CiviCRM is installed" keeps resetting by itself. This definitely occurs whenever CiviCRM is upgraded (issue observed up to and including 5.50.4) and/or an extension is installed, enabled/disabled, updated etc, and may occur at other times. I cannot discern the pattern!
This means that CiviCRM disappears from the 'Components' administrator menu unless you are logged in as Super Administrator.
Since CiviGrant was migrated to an extension, the same issue now applies to "access CiviGrant", "edit grants" and "delete in CiviGrant" - I have to keep re-applying these after each upgrade.https://lab.civicrm.org/dev/core/-/issues/2607How to handle removed files2023-12-15T15:29:01Zaydunsaidan.saunders@squiffle.ukHow to handle removed filesSee [this SE question](https://civicrm.stackexchange.com/questions/39531/database-upgrade-script-failing-call-to-undefined-method-crm-upgrade-incrementa/39546#39546)
A file was removed from the installation tarball but [the Joomla upgr...See [this SE question](https://civicrm.stackexchange.com/questions/39531/database-upgrade-script-failing-call-to-undefined-method-crm-upgrade-incrementa/39546#39546)
A file was removed from the installation tarball but [the Joomla upgrade process](https://docs.civicrm.org/sysadmin/en/latest/upgrade/joomla/#install-the-extension) installs into existing directories meaning the 'removed' file was still present. In this case, it caused the upgrade to fail and will cause problems for any Joomla upgrades following the documented method.
More generally, the same problem applies to any files no longer included in releases.
Some possibilities:
- in the release notes say that files have been removed so don't follow the normal upgrade process
- add an upgrade step that removes old files (but note this problem occurred early in the upgrade process)
- change the upgrade instructions for Joomla