I did not expect this and it caused some confusion for me. Suddenly none of my rules seemed to work as it reverts to the example chunk.
Not sure where to report this. Please move the thread accordingly.
I could be wrong, but when installing the upgrade there is an option not to upgrade ManagerManager as well as any other extra that has changed since the previous version. I tend to untick any ’extra’ which I’ve configured different from the default setting and then manually upgrade having backed up the previous version.
That’s one option, but a more reliable method is to rename anything you change. That way it will be untouched by any upgrades. You should always do this with Tpl chunks. Renaming them allows you to upgrade the snippet or plugin (which you really should do) without losing your work.
Don’t get my wrong, I did rename the chunk and it didn’t get overwritten. What I mean is it resets my plugin configuration values.
I.e. the reference to the chunkname gets reset as well as my jquery path, my settings for: yes/no load in frontend etc. etc.
Quote from: MrDutchy at Jan 31, 2011, 07:56 AM
Don’t get my wrong, I did rename the chunk and it didn’t get overwritten. What I mean is it resets my plugin configuration values.
I.e. the reference to the chunkname gets reset as well as my jquery path, my settings for: yes/no load in frontend etc. etc.
I see. It probably shouldn’t do that. In Revo, you could create a property set. I don’t know if there’s a way to protect them in Evo.
-
☆ A M B ☆
- 24,524 Posts
I just upgraded a local MODx installation, and my MM configuration is not changed. Did your upgrade include a newer version of MM? In that case, the old version will be disabled, and the newer (enabled) version will have the default configuration settings.
-
MODX Staff
- 730 Posts
I’ve filed an improvement ticket for this
http://bugs.modx.com/issues/3732
If anyone has any ideas or questions on this issue, I encourage you to discuss it there.
Thanks!
