Last post 8 min ago

Posts last week 82

Average response time last week 34 min

All time posts 68051

All time tickets 10515

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#1551 – Error 500 with sh 404

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Wednesday, 16 December 2015 19:02 UTC

abcclim

Hello,
Suddenly my site is in error 500 after some research, here is the error in question "Parse error: syntax error, unexpected " in /home/xxxx/www/components/com_sh404sef/cache/shCacheContent.964e88fd0bdf81c011ac135a71b8c638.php on line 320 "
SH 404 by disabling the site works properly understood without rewriting.
I consulted the file in question but I see nothing that concerns me.
Do you have an idea of the problem?
I said that sh 404 is installed on long site name no problem, and I do the last update.
Best regards
AC

Wednesday, 16 December 2015 22:49 UTC

wb_weeblr

Hi

This means there was an error writing to disk and the URL disk cache became corrupted. This may happen when disk write cannot cope with the write rate generated by concurrent visits.

Best is to disable that feature: set "Activate URL cache" to No, under the "Advanced" tab of sh404SEF configuration.

Rgds

Thursday, 17 December 2015 18:11 UTC

abcclim

Thank you it works perfectly
Rgds

Thursday, 17 December 2015 18:29 UTC

wb_weeblr

Hi

Glad to hear that :)

Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.