Upgrade Docs - More updates to "Cleanup" steps
1 unresolved thread
1 unresolved thread
Follow-up to suggestions from !370 (comment 153581)
Merge request reports
Activity
mentioned in merge request !370 (merged)
140 ``` 141 ```bash 142 cv flush 143 ``` 144 * Re-publish static assets (`*.js`, `*.css`, etc) with `composer` 145 ```bash 146 composer civicrm:publish 147 ``` 133 148 134 ## Ensure that CiviCRM Assets are up to date. 135 136 In some build processes it has been found that the static asses such as css files and js files are not synced between the vendor directory and the active libraries folder. To resolve this system admins should run `composer civicrm:publish` to republish assets such as the menu. See also [dev/core#4754](https://lab.civicrm.org/dev/core/-/issues/4754). 137 149 The above steps should not normally be necessary, but they may help with customized workflows or 150 with unresolved bugs. If you identify a scenario where these steps are necessary, please 151 [report an issue](https://civicrm.org/bug-reporting). (For example, [dev/core#4754](https://lab.civicrm.org/dev/core/-/issues/4754) reports about a scenario with assset publication.) changed this line in version 2 of the diff
added 1 commit
- 30e1d163 - docs/upgrade/drupal8 - Re-unify cleanup steps. Be clearer about what is/isn't necessary
mentioned in commit a733270d
Please register or sign in to reply