Module Loader doesn't do anything?!

[jspencer]

I've got a fresh install of 5.0 upgraded to 5.0a fairly customized and I just went to install a simple module I created and found out the Module Loader doesn't work! It comes up and I can browse to my module (I also tried the newest Forums 5.0 module), but after I hit the 'Upload' button the screen refreshes but the module never shows up in either of the 2 big boxes. They are just blank. I tried both Firefox 2.11 and IE7.

There are no errors in the broswer, in the sugar.log file, or in my apache logs. I'm running Ubuntu 6.04 with apache2, mysql5, and php 5 (all updated to latest repositories). Everything else seems to work, and I've got the folders set for 777 permissions. I even tried a fresh install and STILL couldn't load the forums module and got the same thing!

On a related note it also does NOTHING if I click on the 'Install from Sugar' tab (aside from put a dotted box around the tab). I don't really need this part to work yet and I opened another thread about it (seems to be an issue on Sugar's side), but perhaps it's related?

Any ideas?

[jspencer]

Think I kinda figured it out. I just tried it on a Windows 2000 box with IE6 and had the same issue. I noticed that in either version of IE it said "Done" in the lower left but it had the "error" icon. When I clicked on that and viewed details it said there was an "Error; Unterminated String Constant" on some line. So I dumped the page source into my text editor and found out that there was some references to my custom module and the cache folders.

I went to a terminal and sure enough there were several leftover files from my previous upload attempts. Reading between the lines it looked like something in my custom module was breaking module loader. I removed all of the cached files and sure enough, on next try to load the Forums module it worked first time. I then tried to re-load my custom module and it broke the loader again.

Now to figure out why my custom module broke it...

[jspencer]

Looks like it was related to my Package description and readme areas (I suspected as much since that was where the original IE error pointed me in the page source).

In my first attempt to build the module I had used a couple of enters (carrage returns) to separate the text. To fix it I just went back and removed those and made sure the text was all run into one paragraph in each box. Now the module uploaded and installed without issue!

Argh!