Misc. issues with upgrade to 3.6.0

[glibdud]

I'm rebuilding our intranet server, at which time we're upgrading to version 3.6.0 of eFront. We're currently trying to work through a few issues. The upgrade path was 3.5.3 -> 3.5.5 -> 3.6.0 (build 6152). We're running Apache 2.2.10, PHP 5.2.6, and mysqld 5.0.67.

All of the issues described below started after the 3.5.5 -> 3.6.0 step of the upgrade (they were not present in the 3.5.3 or 3.5.5 versions). Also, browser caches were cleared a number of times to eliminate that as an issue.

Issue 1: Whitescreens in place of reports.
Many of our reports are returning nothing but blank white screens. For example, when logged in as an admin on the Control Panel, clicking Reports->User Reports and selecting a user, after thinking for a second, the main frame (everything but the sidebar) goes white. No errors or anything, just white. This happens with both Firefox 3.6 and IE7.
Update: Increasing the PHP memory_limit option from 128MB to 256MB solved Issue 1... thanks to skippybosco for helping me work it out.

Issue 2: Can't sort by column in IE7.
Again logged in as admin, if going to, for example, Lessons->Courses (also Lessons->Categories), click on a column header to sort by that column doesn't do anything. A javascript error is generated:

Code: Select all

Line: 274
Char: 10
Error: Object doesn't support this property or method
Code: 0
URL: http://172.24.0.175:8080/efront/www/administrator.php?ctg=courses

This issue only exists in IE7... Firefox 3.6 works as expected.

Issue 3: Can't assign selected courses to a user group
As admin, in Users->User Groups, editing a group and going to "Group courses"; when checking a few courses and clicking "Assign selected courses to group users", nothing happens. This is very similar to Issue 2 in that it doesn't happen in Firefox, and it generates a javascript error:

Code: Select all

Line: 229
Char: 1
Error: Object doesn't support this property or method
Code: 0
URL: http://172.24.0.175:8080/efront/www/administrator.php?ctg=user_groups&edit_user_group=13

Issues 2 and 3 are similar, if not identical, to this issue:
viewtopic.php?f=1&t=1803

Will provide any info I can. This is an internal server, not accessible from the internet, or I'd set up a login for troubleshooting. If it comes to that, I can talk to my netadmin and see if we can work something out, but if we can work on resolving these without jumping through that particular hoop, that would be preferable. Thanks!

-Dave Murphy

[skippybosco]

Logged on as admin, if you go to the Maintenance Page, are there any warnings or errors?

What theme are you using and have you edited it in any way?

A couple of things that I would try:

1) Reuploading the 3.6 files. Preferable to upload the .zip file and unzip locally on the server to avoid any skipped files or corruption during transfer.

2) Unzipping 3.6 to a clean directory and migrating the content specifics from your existing installation (efront\www\content\*) and configuration (efront\libraries\configuration.php) to your new clean efront directory and rerun the upgrade process.

[glibdud]

Thanks for the response.

Logged on as admin, if you go to the Maintenance Page, are there any warnings or errors?

Only warning are for SOAP libraries, and some missing languages.

What theme are you using and have you edited it in any way?

Default, no changes.

A couple of things that I would try:

1) Reuploading the 3.6 files. Preferable to upload the .zip file and unzip locally on the server to avoid any skipped files or corruption during transfer.

2) Unzipping 3.6 to a clean directory and migrating the content specifics from your existing installation (efront\www\content\*) and configuration (efront\libraries\configuration.php) to your new clean efront directory and rerun the upgrade process.

Done. All issues remain.

[skippybosco]

out of curiosity, if you install a fresh install of 3.6 with no migration of your existing data or configuration do you see the same problems?

[glibdud]

out of curiosity, if you install a fresh install of 3.6 with no migration of your existing data or configuration do you see the same problems?

Heh, you read my mind. I was just in the process of testing that. Issue 1 (the whitescreens) goes away on a clean no-data install, but Issues 2 and 3 remain.

[skippybosco]

it's late here and heading to bed soon.. a couple of options to try (hopefully others chime in as well)

1) Download the latest SVN copy of the install as there were a number of recent IE7 related changes:

http://www.efrontlearning.net/download/svn.html

2) Is upgrading to IE8 an option for you?

[glibdud]

1) Download the latest SVN copy of the install as there were a number of recent IE7 related changes:

Alas, no luck (build 6235).

2) Is upgrading to IE8 an option for you?

Not as a solution. Our standard isn't going to be changing anytime soon. If it would help troubleshooting, I could get it installed on a machine to test.

[glibdud]

Any more ideas from anyone? Any more data I can gather?

[skippybosco]

I wasn't able to reproduce what you are seeing in my virtual environment (running Windows XP and IE7)..

That being said, the issue you list all indicate that you are seeing the issues when logged on as admin. Do you see the issue performing professor or student related tasks?

[glibdud]

That being said, the issue you list all indicate that you are seeing the issues when logged on as admin. Do you see the issue performing professor or student related tasks?

The whitescreens, yes. For example, logged into a student and going to Tools->Reports returns a whitescreen. I'm not sure where to test something like the other issues as Professor/Student.

I was kind of hoping one of the devs would chime in on the similarity between Issues 2 and 3 and the linked previous thread. I can see what was changed to fix that one, but I don't see an obvious way to apply it to these.

Also, I'm kind of curious if anyone else is running eFront on 64-bit Linux, and if they had to jump through any particular hoops. I had some issues getting eFront happy with the PHP:Zip module in SLES10, but for this SLES11 install it seemed happy with everything out of the box (at least at install-time). This may be a question to throw in the general forum...