Support: Error 500

Social forum

Error 500

I get thi error HTTP 500 after creating an activity with autoview (latest X61 version):

http://www.learncognitivetherapy.com/moodle/mod/autoview/view.php?id=4

I click refresh on the left side of the screen with no avail. Nothing happens.

What's the problem? Any thoughts?

Sylvia Buet

Do you get this problem with other AutoView presentations on this server, or is it just this one? If it is just this one, could you post the .avx file here or email it to me.

Can you have a look in the server error log to see if any errors which relate to this page have been recorded.

Also, which version of PHP are you using ?

Permalink | Show parent | Reply

Hi
In the past I have used other versions of autoview and they always worked. This one doesn't and my server is the same.

I have tried to re-install the autoview. I have tried create different presentation. Nothing. When I click on "start editor" just nothing happens. Left white screen always.

if you want I can give you access to my moodle course (it's empty) so, I can create a username and password and see by yourself. What do you think?

I can send you those details to a personal email that you provide me.

Thanks for your help.

Sylvia Buet

Permalink | Show parent | Reply

Hello, that doesn't really answer my question. What I mean is do other pre-existing AutoView presentations on your server still work, or is every AutoView on your server now broken ?

Can you check which version of PHP your server is using, there should be a link in the moodle admin console. AutoView no longer officially supports PHP 4.x, PHP.net made this version obsolete about a year ago. I haven't done anything to explicitly break PHP 4, but AutoView is no longer tested with this version, so some incompatible code might have crept in.

Right now, a username/password for your Moodle isn't going to help much, I need to see the error logs for your server which aren't accessible through the Moodle interface. What you need to do is :

1) Find the error log on your server, you'll probably need full file system access to do this.
2) Open an AutoView presentation so that the error is triggered.
3) Copy and paste the most recent entries in the error log onto this forum thread.

Permalink | Show parent | Reply

Hello Tim
I got you the error logs from the website and the php version of my server (which is not 4).

Let's see if you make sense of all this.

Now I don't get a 500 error. I just get a white page on the right ( I can only see the text and the button on the left about stating the editor and nothing else)

And no, there was no other autoview installed before. In fact, I tried to install an older version and didn't allow me because a new version was present.

Thanks

error_log_from_server_after_accessing_moodle_autoview.txt

Permalink | Show parent | Reply

There don't appear to be any PHP error messages in this log file, which means that either PHP errors have been completely turned off or the error messages are going somewhere else.

Two thoughts, which I wish I had thought of earlier :

1) What happens when you access /moodle/mod/autoview/test.php on your server ?

2) In Moodle Site Administration go to Server>Debugging. Set the Debug Messages drop down box to 'ALL' and then make sure the 'Display debug messages' box is ticked. This should cause the errors I had hoped to see in the log to show on the web pages. You'll probably see some error messages come up on other pages, don't worry about these, just go back to the AutoView presentation and cut and paste any errors that come up on that page into this message thread. You'll probably want to turn the debugging stuff off again once you have done this.

Permalink | Show parent | Reply

OK, I have just done all the suggested tests.

Please find attached results.

I hope this gives you an idea what's happening. I really want to start with my training programme and this is the only thing stopping it. I have faith in you Tim!

Thanks

Sylvia

errors_after_tests.txt

Permalink | Show parent | Reply

There is nothing in there which I would have considered to be a show stopper bug. However, I have corrected the code which was generating the notice messages just in case. If you download the avedit.php file from :

http://autoview.autotrain.org/file.php/1/module-download/bleeding-edge/avedit.php

and use it to replace the one in your AutoView installation, however i'm not very hopeful this will cure the problem.

Can you also check the exact version number of your Moodle installation, it's just possible we have a version specific bug here, but I need to test with the same version you are using. Also, which web browser (and specific version) are you using at the moment ? Do you get the same error with a different browser ?

Edit : Ignore the web browser bit, I just remembered the link you posted at the start of this message. Doesn't work on mine either....

Permalink | Show parent | Reply

Hi Tim
I am giving up.
I have removed Moodle for the server. Tried different subdomains, folders, you name it (including different versions of moodle and Autoview), I have tried it. Nothing makes Autoview works. Just white screen on the left. Frustrating!

If someone doesn't fix this for me by intalling Moodle and autoview for me, i will have to forget about Moodle forever. The main reason I wanted to use Moodle was for the autoview as I need to have my slides and videos syncronised at the same time and offer quizzes and assessments as part of my courses.

Even if I had to pay for this service, can anybody help me?

Frustrated and Sad Sylvia

Permalink | Show parent | Reply

Hello, still here and willing to help, we haven't finished the debugging process yet if you are willing to stick with it for just a little longer i'm willing to continue to help.

We do offer a commercial service, so if you are willing to pay you can have my full attention.

Permalink | Show parent | Reply

Please contact me to discuss that option by email (silviabuet@googlemail.com)

I look forward to your reply

Sylvia

Permalink | Show parent | Reply

The cause of this problem has now been established and seems to be down to inconsistent file permissions being set inside the AutoView module when it was unzipped into the server directory.

Permalink | Show parent | Reply