Module Loader Blank

[tekg]

Hello,

Having a problem with my module loader. I loaded a bunch of modules (6+) but now when I load it the screen is just blank (shows no modules installed) and it will not connect to the sugarexchange network. I don't think this is a permissions problem as it was working, it just all of a sudden stopped. I also reset the permissions manually to be sure. The last module I installed was Max if that helps. Everything is working fine in Sugar, exceptthe Trainings module that is giving an error for assigning to users but it works anyways. Any help that could be lent would be great, and I've gone over wiki + forum search.

[Moore]

I am having the same issue. I am attempting to get LDAP authentication setup with sugar using IIS 6.0, sugar 4.5.1e, and Windows Server 2003. I have sugar up and running but when I go to the module loader from the administration page, all I see is the shell and the header, there is no content visible. Perhaps I am looking in the wrong place to configure the LDAP module, but I can't seem to find anything else. If anyone knows what is going on or could point me in the right direction I would greatly appreciate it.

thanks
~David

[Moore]

Issue was resolved by rolling back to PHP version 5.1.4

[tekg]

Interesting.... did you always have blank module pages or did it come after you installed many modules? Mine was working but then it didn't. Interestingly, when I upgraded to 451e it showed all the modules and module page was working for the update section, but the regular modules page was still blank. The upgrade appeared to make things better as I get my sugar login info screen back but stilol modules appear blank, it says version not supported and will not log into sugar network (or load modules manually).

[Moore]

I had always had blank module pages, as well as some other pages that weren't displaying correctly. Once I rolled back to 5.1.4 everything worked fine.

[tekg]

interesting, I may give this a go but in my particular case (LAMP stack) I seem to think this isn't the answer. Good posts tho

[Chet0012]

I had this same problem - the rollback to 5.1.4 fixed the problem - and quite honestly.. I think it fixed quite a few other things as well that I did not perceive as broken at the time.. It also feels like performance is a bit better as well.