ManagerManager Configuration Chunk changed with 1.0.2 upgrade

I thought it might be worth pointing out that when upgrading to 1.0.2 the ManagerManager plugin Configuration Chunk is set to mm_demo_rules. This occurs even if you already have the plugin set to utilize another, existing chunk.

If you use ManagerManager like I do it is not readily apparent since most of the plugin settings affect users with roles other than at a Super Admin level and you must re-configure the Configuration Chunk after the upgrade.

Okay, this has reared it’s head again for me.

My original solution to this problem was to leave my ManagerManager configuration in mm_demo_rules since the upgrade was overwriting the location of the configuration chunk. Well, apparently it also overwrites the mm_demo_rules chunk back to it’s original state, which caused all of the ManagerManager config files to be overwritten.

Is this the best way to be handling this?

When you upgraded, did you clear the checkbox for the chunk on the installed elements options page?

I guess I didn’t, didn’t realize that it was there.

I just ran another upgrade and even if you uncheck that box the plugin will still be reset to mm_demo_rules during the upgrade process.