TOPIC: Can't add events anymore

Hi Yves,

This weekend I moved the test site, with Matukio, to the live site and everything went fine so far.
Except that I can't add any events anymore in the backend, if I access the events-page of Matukio, it gives me an 500-internal server error.

Events (administrator/index.php?option=com_matukio&task=2) => 500 internal server error
Categories (administrator/index.php?option=com_categories&extension=com_matukio) => Ok
Coupons (administrator/index.php?option=com_matukio&view=coupons) => 500 internal server error
Booking fields (administrator/index.php?option=com_matukio&view=bookingfields) => 500 internal server error
Configuration (administrator/index.php?option=com_matukio&task=3) => 500 internal server error
Statistics (administrator/index.php?option=com_matukio&task=4) => 500 internal server error
Live update (administrator/index.php?option=com_matukio&view=liveupdate) => 500 internal server error.

Do you have any idea what could be causing this?
Could it be that my live site runs on Php5.2 and my testsite was on Php5.4?

Kind Regards,

Erwin

Hi Erwin,

hmm hard to say, could you turn on error reporting (Joomla Global Configuration, set it to Development) and Joomla Debugging?

Could it be that my live site runs on Php5.2 and my testsite was on Php5.4?

No, that should not be the issue.

Best regards,

Yves

Hi Yves,

Thank you for your fast reaction.
I tried it out, and the funny thing is, with error reporting to debugging it works, and if I switch it back it doesn't.
Wit the error reporting on debugging it gives the following error (if I click on "events"):

Warning: Cannot modify header information - headers already sent by (output started at /www/m/o/t/mywebsite.eu/public_html/plugins/system/backendtoken/backendtoken.php:48) in /www/m/o/t/mywebsite.eu/public_html/administrator/components/com_matukio/matukio.php on line 15

Hmm funny one.. Two possible solutions:

Comment line 15 in matukio.php, don't have any idea why it is in there (some heritage from seminar probably) or deactivate the backendtoken plugin, also don't have any idea why they send it out there..

Bet regards,

Yves

Hi Yves,

Thanks for the solution!
I already tried deactivating the backend token but that didn't work,
commenting out line 15 did the trick!

Thanks!

Erwin