Module Loader does not show installed or uploaded extensions

[bstonehill]

I'm running SugarCRM CE 5.1RC on WinXP Pro and when I go to module loader none of the installed extensions are displayed and if I upload any they do not show up either. I have run the quick repair utility which had no effect.

Please help!

[DragonflyMaster]

I'm running SugarCRM CE 5.1RC on WinXP Pro and when I go to module loader none of the installed extensions are displayed and if I upload any they do not show up either. I have run the quick repair utility which had no effect.

Please help!

Maybe you deleted the cache?

[bstonehill]

Hmmm...I just installed it Thursday. If I did wouldn't it restore it when I restarted Apache?

[bstonehill]

Okay, I found what broke it but I can't figure out how to fix it. I created a custom module in modulebuilder and if I deploy it or export it and load it through module builder it causes me to not be able to use any installed extensions and causes me to not be able to see installed or uploaded extensions, therefore I can neither uninstall or install any modules. I was hoping maybe if I played around with the installed modules data in mysql I could get it to come back but I can't even find where it's stored. I know it's stored in a database because the modules I had installed when I created a mysql backup imported with all the records.

[DragonflyMaster]

Hmmm...I just installed it Thursday. If I did wouldn't it restore it when I restarted Apache?

I was talking about Sugar's cache, that has nothing to do with Apache.

[DragonflyMaster]

Okay, I found what broke it but I can't figure out how to fix it. I created a custom module in modulebuilder and if I deploy it or export it and load it through module builder it causes me to not be able to use any installed extensions and causes me to not be able to see installed or uploaded extensions, therefore I can neither uninstall or install any modules. I was hoping maybe if I played around with the installed modules data in mysql I could get it to come back but I can't even find where it's stored. I know it's stored in a database because the modules I had installed when I created a mysql backup imported with all the records.

In this case, a thing you can do is to go inside cache folder and remove the folders created when you uploaded your module.
Then in MySQL you can remove tables named after your module.
NOTE: a file backup and a db backup are raccomended before performing these tasks.

[bstonehill]

Thanks. I ended up installing a fresh copy of sugar and just re-creating the module in module builder again, then deployed it. This seems to work fine as long as the module is originally built in that instances module builder and deployed. If I publish and load it through module loader or import the module builder project then deploy it it breaks. Hopefully I won't break it again down the road but at least I know where to go to try to fix it, I couldn't seem to find where the installed extensions were kept.

Thanks again!

[GVSupport]

Hi!
I have the save problem. You said that to reinstall Sugar and then it worked? What version are you using? What exactly did you do?

Thanks

[DragonflyMaster]

If I publish and load it through module loader or import the module builder project then deploy it it breaks.

Did you try this on the same instance or in a new one?
My experience says exporting a module in a Sugar instance and importing the module in a different Sugar instance works (I'm referring to Sugar CE 5.0x)

[chaos0815]

Seems I just experienced the same thing (using 5.1RC1):

• import a previously exported custom module using ModuleLoader
• deploy the imported custom module via ModuleBuilder
• => custom module is deployed, but at the same time disappears from ModuleBuilder.

Un- and reinstalling module, and still it doesn't show up in ModuleBuilder. I first have to remove the package and upload it again.

My current workaround: create a copy of the imported module and deploy that. Seems like ModuleBuilder keeps 'nativ' (as in 'not imported') modules after deploy.

Feature or bug?