Jump to content
  • 0

White Page In Modules Available Screen


EidolonHost

Question

And I have indeed enabled blesta error reporting... but that's not even showing up.

 

Same for php.ini's display_error issue. It's... odd, not getting any output at all. Not even view source gives me anything.

 

I'm not sure what happened here but modules installed shows the following to be installed:

 

BuycPanel

InterWorx Control Panel

Namecheap

Blesta Universal Module

 

Should I reupload the modules section to try overwriting the files or...?

Link to comment
Share on other sites

12 answers to this question

Recommended Posts

  • 0

You might receive a 500 internal server error if you have a fatal error or syntax error in the code that is unparseable. If it only affects modules, then my guess is one of the modules is causing it. You can remove all of the module directories from /components/models/ and see if the problem goes away. Then add them one-by-one until you discover the module that is causing the problem.

Link to comment
Share on other sites

  • 0

What did you do before that happened? It sounds like something is missing or a module / plugin is broken and conflicting.

 

I'm not entirely sure. I might've been messing with the live chat plugin... but I honestly am not sure because I hadn't played with it recently.

 

Edit: That is to say, I installed a few different modules and uninstalled them when I realized I wouldn't be needing them but it was fine in the available screen... at least, when I left it. /edit

 

Any way to find out what happened to my poor Blesta install? heh

Link to comment
Share on other sites

  • 0

You change any files? I would recommend re-uploading all original files for the exact same version.

 

A white page usually indicates an error, enabling error reporting in /config/blesta.php should show something, if not it may be suppressed or there may be a separate issue. Check your web server logs, is it showing anything other than a 200 response when you load that page?

Link to comment
Share on other sites

  • 0

You change any files? I would recommend re-uploading all original files for the exact same version.

 

A white page usually indicates an error, enabling error reporting in /config/blesta.php should show something, if not it may be suppressed or there may be a separate issue. Check your web server logs, is it showing anything other than a 200 response when you load that page?

 

Erm... that might be it. >_>

 

I was editing the structure.pdt to sync the header and footer... but I don't know if that might have had anything to do with it.

 

Web server logs... AH, here it is:

 

200.76.91.109 - - [06/Mar/2015:20:45:56 +0000] "GET /billing/index.php/admin/settings/company/modules/available/ HTTP/1.0" 500 378 "http://eidolonhost.com/billing/index.php/admin/settings/company/automation/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36"

 

Odd. It seems to be... redirecting? Or something similar.

Link to comment
Share on other sites

  • 0

So correcting the paths and the like didn't seem to fix the issue. 

 

I'll note that Plugins > Available works just fine but not Modules > Available.

 

I'm not entirely sure what else I can do to correct this issue, so far. I do see that instead of the usual 200 code... it's a 500 code, which means something is triggering an internal server error.

 

Welp. Time to look at where it's at to find the ISE...

Link to comment
Share on other sites

  • 0

You might receive a 500 internal server error if you have a fatal error or syntax error in the code that is unparseable. If it only affects modules, then my guess is one of the modules is causing it. You can remove all of the module directories from /components/models/ and see if the problem goes away. Then add them one-by-one until you discover the module that is causing the problem.

 

That did the trick, it gave me access back.

 

Alright, time to do this, one by one. We only had 5 modules activated at the time. InterWorx, Namecheap, cPanel, SolusVM and BuycPanel. We'll see which one did it. I'll report back as soon as I find out what the offending module was doing.

Link to comment
Share on other sites

  • 0

Interesting. Hard to tell what went wrong then, but glad it's working for you now.

 

Yeah... I basically rm -rf'd the modules directory, unzipped the blesta zip that I still had when I initially set up Blesta (3.4.0-3.4.2 I think it was) and moved the appropriate directory back into place and chown'd to the owner of the account.

 

Didn't change permissions or anything but... after moving that stuff into place, it worked A-OK perfectly. Permissions issue, I suspect. Either way, your solution did the trick.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...