Permissions for some modules are getting added as unpublished?

[gornycreative]

Hi all,

I don't know if this is an issue with RockMigrations or the modules->install() function or if something else is going on - perhaps there is just old module config stuff getting in the way.

I have been using RockMigrations to install modules and several (for example, Dashboard and PageProtector) will add the permissions to the permissions area but they are getting added as unpublished.

I think I ran into this with custom Admin Actions too? It doesn't happen with every module.

From what I can see there isn't anything RockMigrations is doing that should interfere - it seems to just call modules->install('module').

It isn't possible to add unpublished permissions to a role which interferes with other migration scripts. I'm just wondering if permissions pages can have their status set like regular pages or is there something else weird going on?

Anyone else run into this?

[gornycreative]

The common denominator seems to be that the modules in question include both a populated 'permission' and a 'permissions' key/value in the module $info array. This includes a few older modules of Ryan's (ProcessFileEditor) - on the actual permissions menu/page list they are struck through/unpublished. 2049 Status code in the DB.

 

[gornycreative]

I can mitigate it via the API/migrate() so I guess it isn't an issue.

I did find that RockMigrations doesn't take existing page titles into account when updating data so I will make an issue in RM for that. 

[bernhard]

@gornycreative have you seen https://github.com/baumrock/RockMigrations/issues/50 ? Or was that you posting the issue? ? 

[gornycreative]

9 hours ago, bernhard said:

@gornycreative have you seen https://github.com/baumrock/RockMigrations/issues/50 ? Or was that you posting the issue? ? 

That's me - I rebranded.