[solved] HTTP 500 and white screen of death

ciwclass
Thu, 01/16/2014 - 22:56
Forums
Support
Hello, Thank you for the taking the initiative to develop Opigno. As an eLearning Developer I am very excited of this possibility. I am able to install Opigno, and the modules needed. However, as soon as I try to enable the modules in Drupal's module manger, I get HTTP 500, or blank white screens. I have uninstalled and reinstalled Drupal and the modules many times to figure out how to handle this. I am new to Drupal, but to lower the possibility of the HTTP 500, I have been paying attention to the listed "module requirements" prior to enabling individual modules. Is there an action plan in which order to enable Opigno's list of module components (with checkmarks), and its other required modules that need to be installed? What am I missing here? A video tutorial will be extremely helpful. Please forgive the novice questions. Kindly refer me to any reading materials I need. Thanks again.
Profile picture for user James Aparicio
James Aparicio
Fri, 01/17/2014 - 09:38

Hi ciwclass,

Hi ciwclass, Thank you for your interest in opigno. What server are you running it on? What do you see under Reports -> Recent log messages? Try raising your php memory_limit to 256M. Best regards
ciwclass

In reply to by James Aparicio

Fri, 01/17/2014 - 15:46

Hi James,

Hi James, My memory was already been increased to 256MB in php.ini (memory_limit = 256M). My web hosting company is HostMonster.com. After I enable Opigno Module, white screen of death appears, so I can't do anything else. Running a report is not possible after I lose access to the site. Clicking the back button won't do me any good either. Below is the order of what I do: 1 - Installed Drupal 2 - Installed modules (Opigno modules, and the missing ones including Panels, Adavnced_help, Context, Migrate, Message/Message Notify, Realname, Xautoload, Chart, and Signup) 3 - Carefully tried enabling the modules, based on their requirements; making sure I get "greens" in the module manager. However, HTTP 500, and white screens happen consistently in step 3, while enabling the modules. Probably because I miss a required/prerequisite module! Please correct me if I'm wrong, but I thought that Opigno modules should be enabled first before expecting to use them. If this is more like a Drupal challenge in enabling the modules, is there any recommended reading for it? Thanks again.
Profile picture for user James Aparicio
James Aparicio
Fri, 01/17/2014 - 15:58

Hi ciwclass,

Hi ciwclass, What do you mean by missing ones? Opigno ships already with some core modules. We have an app manager, on the top menu, after you install opigno. From there you can select other opigno modules that do not come pre installed. We choose not to install all the modules because not everyone will need them. We think it is better this way. If you do not install any other than opigno modules do you have this problem? If not it is one of the "missing" ones that is causing this problem. Try enabling them 1 at a time. And see which one is giving you the error. Also you should look in your apache logs. Our documentation is at http://www.opigno.org/en/documentation. You installed Drupal and not Opigno_LMS? Best regards
ciwclass

In reply to by James Aparicio

Fri, 01/17/2014 - 21:01

Hello again,

Hello again, Drupal and Opigno_LMS are both installed. Can I access the Opigno screen right after the Opigno_LMS installation? If yes, how? After the Module installation, I thought I had to go to the Module manager, and manually enable Opigno and its componets. I have provided a screenshot of missing modules, which appear in "missing" red text here: http://university-x.com/images/Missing_Modules.png So, the main question is after Opigno module installation, where do I go to see that application on my screen? Cheers...
ciwclass
Fri, 01/17/2014 - 21:08

I'll be happy to provide you

I'll be happy to provide you with an admin login, if that's preferable. If that's OK please send an email to [email protected] Thanks again...
Profile picture for user James Aparicio
James Aparicio
Mon, 01/20/2014 - 09:48

Hi ciwclass,

Hi ciwclass, I do not understand what do you mean by drupal and opigno_lms are both installed. Opigno Lms is a distribution, not a module. It seems that you are installing Drupal and then trying to activate opigno. You should install the distribution. Best regards
wadmiraal
Mon, 01/20/2014 - 10:10

Hello ciwclass.

Hello ciwclass. Does your hosting provider allow you to turn on error displays ? Do you have access to a `php.ini` file ? If so, can you search for the line `display_errors` and turn it `On` ? Or, otherwise, can you try adding this to your `sites/default/settings.php` file: `ini_set('display_errors', 'on');` ? A WSOD is usually a Fatal Error, which must result in some kind of error message.
ciwclass

In reply to by James Aparicio

Mon, 01/20/2014 - 16:55

Hi James,

Hi James, Thank you for pointing that out. Being new to Drupal, I had no idea what a Drupal distribution meant! This time, I deleted everything, and used Opigno_LMS distribution to install from scratch. Everything worked fine, and as expected this time. :) My mistake was to install standard Drupal first, then add Opigno_LMS on top of the existing core Drupal, which created all kinds of problems such as HTTP 500, and white screen of deaths! I can't wait to start creating some courses. Thanks again for this wonderful oppertunity. Keep up the good work. Cheers...
ciwclass

In reply to by wadmiraal

Mon, 01/20/2014 - 16:58

Thanks wadmiraal; problem was

Thanks wadmiraal; problem was solved by installing the Opigno_LMS distribution only. I was installing both standard core Drupal and the Opigno_LMS distribution! Big mistake eh!