Hi, I need some guidance on how to deal with the errors that I saw during installation and while accessing the different pages of the website (see attachment for screenshots):

1. Strict warning: Non-static method view::load_views() should not be called statically in view::load_views() (line 837 of ...views.module)
2. Strict warning: Only variables should be passed by reference in filefield_paths_install() (line 48 of ....filefield_paths.install)
3. Notice: Undefined index: masquerade_users in masquerade_user() (line 387 of ....masquerade.module)

When I go to any page, this error is always displayed: Strict warning: Non-static method view::load_views() should not be called statically in view::load_views() (line 837 of....)

The settings during installation:

1. ELMS v6.x-1.0-alpha5
2. Windows 7 Home Premium (64bit)
3. XAMPP 1.7.7
--PHP 5.3.8
--Apache 2.2.21
--MySQL 5.5.16

4. PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

Comments

btopro’s picture

Version: 6.x-1.0-alpha3 » 6.x-1.0-alpha5

Hmm... did you read the README.txt file about things to place in your settings.php file to ensure errors are squashed? Not sure what's throwing those currently (which is another problem and unfortunate atm ;)).

I have error_reporting(0); in my settings.php file to ensure ALL errors are turned off and was able to install with 128 megs of ram for install. Try removing the database and adding in the error_reporting(0); line at the end of your settings.php file and try installing again.

abebantegui’s picture

I tried the error_reporting(0) and managed install without issue.

If I go load every page of ELMS, here's what I would get:

Strict warning: Non-static method view::load_views() should not be called statically in view::load_views() (line 837 of C:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\views\views.module).
Strict warning: Non-static method view::load() should not be called statically in view::load() (line 879 of C:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\views\views.module).
Strict warning: Declaration of views_handler_argument::init() should be compatible with that of views_handler::init() in views_include_handler() (line 77 of C:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\views\includes\handlers.inc).
Strict warning: Declaration of views_handler_filter::options_validate() should be compatible with that of views_handler::options_validate() in views_include_handler() (line 77 of C:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\views\includes\handlers.inc).
Strict warning: Declaration of views_handler_filter::options_submit() should be compatible with that of views_handler::options_submit() in views_include_handler() (line 77 of C:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\views\includes\handlers.inc).

When I go to the ELMS page immediately after installation this is the error I would see:

· Notice:Undefined index: masquerade_usersinmasquerade_user()(line387ofC:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\masquerade\masquerade.module).
· Notice:Trying to get property of non-objectinog_is_group_admin()(line391ofC:\xampp-1.7.7\htdocs\elms\profiles\elms\modules\contrib\og\og.module).

(see attachment for details)

abebantegui’s picture

StatusFileSize
new34.53 KB

Here is the error that I saw when I went to the home page.

btopro’s picture

is this still happening or this is what DID happen previously? There is a known issue with better formats (my install of it) that I need to fix for the next release. Are these errors showing every page load still? Shouldn't be though may have encountered a max packet error in mysql (silently on install and nice and loud now :)). Might want to look into bumping max_packet (forget exact command) to 10M or at least higher then the default (1).

btopro’s picture

Notices aren't a huge deal, that's something that started in the reporting mechanism of php 5.3 and above. Unfortunately because most are running php 5.3 that's why error reporting needs to be squelched. Going to take awhile to track down, patch and submit patches back to all those community projects for relatively minor issues (sadly). Could always use help there :)

abebantegui’s picture

Thanks for accommodating me.

The error messages (in the attached text file) came from the latest install that i did 30mins ago. And yes the errors are still appearing on each and every page.

I'll try to set the max_packet and start over again.

BTW, I tried to install ELMS on XAMPP 1.7.1 (Apache: 2.2.11, PHP: 5.2.9, MySQL: 5.1.33-community) with no luck. I'm getting this error:

HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

btopro’s picture

hmm.. If error reporting is actually 0 it shouldn't show those messages you are mentioning. Maybe its not responding to it after install. I think its max allowed packet or something and that will help some more hopefully. Sorry for all the issues your having, still some tricky business here with how large the installer is.

abebantegui’s picture

StatusFileSize
new407.13 KB

Here is the config on my latest install:

1. XAMPP 1.7.7
--PHP 5.3.8
--Apache 2.2.21
--MySQL 5.5.16

2. PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

3. MySQL settings:
--max_allowed_packet = 10M

4. settings.php
--error_reporting(0);

The installation process ran into 1 error message at point where its Remaining 15 of 136:

  • Strict warning: Only variables should be passed by reference in filefield_paths_install() (line 48 filefield_paths.install)

When the installation is done Drupal recreates the settings.php and sets it to Read only. Since the settings.php no longer has the error_report(0) clicking on the 'new site' link to view the home page will display a whole bunch of errors.

I added the error_reporting(0) back into the settings.php and the errors went away.

Also, when I was trying to create a course, I ran into this error:

  • HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.
btopro’s picture

can you turn error reporting to E_ALL so that you can send me the 500 error. Also have you upgraded from anything that shipped by default?

abebantegui’s picture

I have not upgraded anything. I'm working on this package: elms-6.x-1.0-alpha5.zip

When I can consistently recreate the 'HTTP Error 500 (Internal Server Error)' I will send you the information. What I have noticed is that if a page or an action takes to long, that'll be the time this error appears.

I can however consistently see the Error 500 if I try to install ELMS on the following configuration settings:

1. ELMS v6.x-1.0-alpha5
2. Windows 7 Home Premium (64bit)
3. XAMPP 1.7.1
--Apache: 2.2.11
--PHP: 5.2.9
--MySQL: 5.1.33

4. PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

5. settings.php
--error_reporting(0);

Basically, I can't install ELMS when the Error 500 appears during the initial stages of the installation process.

abebantegui’s picture

StatusFileSize
new4.68 KB

The Error 500 happens almost anywhere in the website.

Here are log files:

error.log

php_error_log (I don't think it has errors that was due actions during the creation of a course and others. The errors, based on the time stamp, are specific during the installation process)

btopro’s picture

hmm... as if it's not completing something during install and that that is screwing other stuff up downstream possibly? I haven't tried installing via XAMPP not that I'm pointing the blame there, just haven't. Can you try bumping php version to 5.3+ w/ same requirements for install and see what happens?

abebantegui’s picture

I can't install ELMS if my config is:

1. XAMPP 1.7.1
--Apache: 2.2.11
--PHP: 5.2.9
--MySQL: 5.1.33

2. PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

3. settings.php
--error_reporting(0);

My installation right now where the Error 500 appears:

1. XAMPP 1.7.7
--PHP 5.3.8
--Apache 2.2.21
--MySQL 5.5.16

2. PHP settings:
--display_errors Off
--memory_limit 256M
--max_execution_time 300

3. MySQL settings:
--max_allowed_packet = 10M

4. settings.php
--error_reporting(0);

btopro’s picture

can you get to the watchdog and see if the error is being stored when you do try to create a course? Also tell drupal to print messages to the screen if it's not set to it currently. 500 can be more or less anything. Also see if you can get to the reports page that tells you all the php / mysql settings as that info would be useful to see if the values you are reporting as being set match up with what drupal is claiming they are.

btopro’s picture

Version: 6.x-1.0-alpha5 » 6.x-1.x-dev
Status: Active » Fixed

a ton of work has been put into correcting these issue sin Alpha 6 which will be out next week

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.