#3975 closed Task (fixed)
Update the UPGRADE.txt in next release
| Reported by: | Purus | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Elgg 1.8.1 |
| Component: | Documentation | Version: | 1.8 |
| Severity: | minor | Keywords: | |
| Cc: | brett@… | Difficulty: |
Description
Hi Team,
Please update the Uprade.txt file in the next final release so that it mentions to remove the profile mod folder before the upgrade.
And also a note to disable all the plug-ins before the upgrade will be better.
These instructions will be helpful for the new users who have started using ELGG.
Change History (8)
comment:1 Changed 20 months ago by brettp
comment:2 Changed 20 months ago by cash
We completely restructured the profile plugin and moved some of the code into core. There is at least one view in the old plugin that overrides a view in core now.
comment:3 Changed 20 months ago by Purus
@brettp: As Cash mentioned, there are some unwanted files in the old profile plugin, which is causing issues in the activity wall.
comment:4 Changed 20 months ago by brettp
Alright. We can add this to the "directories to delete" in UPGRADE.txt. Are there others? Do we want to list all the bundled plugins?
comment:5 Changed 20 months ago by Purus
Thanks. I am sure about the Profile folder and the Pages folder. Not sure about other folders, unless we get some other issues that we got before for these 2 folders.
comment:6 Changed 19 months ago by cash
- Component changed from Core to Documentation
- Milestone changed from Needs Review to Elgg 1.8.1
comment:7 Changed 19 months ago by Brett Profitt
- Resolution set to fixed
- Status changed from new to closed
Fixes #3975. Added mod/profile to the list of dirs to remove for an upgrade.
Changeset: 6ab68776c9ac5a44e7b3494a75ba09a522596be9
comment:8 Changed 19 months ago by Brett Profitt
Fixes #3975. Added mod/profile to the list of dirs to remove for an upgrade.
Changeset: 6ab68776c9ac5a44e7b3494a75ba09a522596be9
Why do you need to remove the profile plugin to upgrade? Also, you don't want to disable all plugins during an upgrade because the upgrade process triggers plugin-specific upgrades.