500 Internal Server Error for Transcription Page Actions

[Anneliese Dehner]

Hello collective wisdom,

After two years and thousands of successful transcriptions, our Scripto instance is suddenly throwing a 500 error when any transcription action is taken. We haven't changed our code or configurations, so this is puzzling me.

The break happens when data is sent via $.post() from "/scripto/transcribe.php" to "/scripto/index/page-action"

Have you seen this before? Or do you have any idea how to resolve this?

Our versions:

Omeka 2.1.3

Scripto 2.2

mediawiki 1.22.5

I would greatly appreciate any suggestions you have.

Thanks,

Anneliese

[Jim Safley]

Hi Anneliese,

The plugin returns a 500 response when the Scripto library throws an exception. Unfortunately it doesn't also print a stack trace, which would be helpful here.

If possible, open plugins/Scripto/controllers/IndexController.php and in Scripto_IndexController::pageActionAction() echo the exception (echo $e;) within the catch block at the bottom. Then perform a broken action and view the 500 response in your browser's web tools. Hopefully you'll see exactly why you're getting 500.

Jim

--
You received this message because you are subscribed to the Google Groups "Scripto Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scripto-dev...@googlegroups.com.
To post to this group, send email to scrip...@googlegroups.com.
Visit this group at http://groups.google.com/group/scripto-dev.
For more options, visit https://groups.google.com/d/optout.

[Anneliese Dehner]

Thanks Jim.

Unfortunately when I try to echo, var_dump, or console.log anything from within the catch block in Scripto_IndexController::pageActionAction(), I get no textual response. 

Any other ideas?

Anneliese

[Jim Safley]

Are you looking at the response body of the AJAX POST request? You should be seeing something. If not the 500 error is not emanating from the Scripto library. Take a look at your server's PHP error log, usually in /var/log/apache2/error.log.

Jim

[Anneliese Dehner]

Ahhh! Cool!! I didn't know to look at the post response in my network dev tools, but now I do! Thanks so much!

The 500 error was due to using a login that lacked mediawiki email confirmation (we require users to confirm their email address in order to transcribe). All is now working as expected. (Although we should really improve our usability game by asking transcribers to confirm their email address when this happens :)

I really appreciate your help.

Anneliese