Hi,



I have spent the last few days struggling with a problem I am thinking must be a fairly major bug but am not sure.



I have a 5.6.2 installation with 4 portals. I wanted to use the core shop module for one of these portals (to test as a much as anything as I have never used this module before) and because I don't want it available to the other 3 portals I set it as a premium module and unassigned it for each of the 3 other portals. Nothing unusual in this as far as I can see.



I then discover when working on one of the 3 portals I didn't want the shop module available for that I can't add any modules (the module list drop down is greyed out on the ribbon bar). After some digging I discover that all module permissions have been removed from all portals and regardless of whether the module was flagged as a premium module or not no portal has permissions to add any module at all.



I am really getting concerned by this stage and go straight to the database and discover that at least 2 tables, the PortalDesktopModules and DesktopModulePermissions tables are empty except for permissions allowing the shop modules on the single portal I had assigned them to. How can assigning/unassigning premium modules erase permissions for all modules even core modules?



Has anyone come across this behaviour before or can anyone suggest how I can reconstruct the necessary tables to give permissions back to all the core modules that would normally appear in the add module drop-down list?



Thanks

Thanks for the reply Sebastian. I had already started down that track and discovered what I think is even weirder behaviour.



I found I can re-enable permissions on a module by module basis by using the following process:

- go to Host > Extensions

- click the edit link beside the module you want to enable

- the edit page shows 2 select lists for assigned and unassigned both of which are empty regardless of whether the module is flagged as premium or not

- even though the select box is empty if you click the double right arrow the page reloads and all the portals appear in the unassigned box

- select all portals listed and click the double right arrow again and the page reloads again and all the portals appear in the assigned list

- repeat the process for each module you want to be able to add to a page for any portal



To me this seems very strange behaviour and I would be surprised if it works this way by design, how would anyone know to click the double right arrow to get the portal names to appear, especially when this section is labelled as premium module assignment/unassignment. If I had to guess I would say that the onclick handler for those arrows is calling the wrong stored procedure but I haven't got time to verify that.

II just experienced the same bug. Did you get it reported? (Rushing to fix the issue before I leave town)