Internal Server Error

There have been many reports of internal server errors which I’ve never been able to reproduce, let alone attribute to any part of my plugin. Often these seem to be down to security software that blocks Loco’s behaviour, but I’ve been unable to verify that.

Please try version 2.0 beta version: https://localise.biz/help/wordpress/translate-plugin/developers

If the problem persists in v2, please start a new topic. I’m closing this as support for v1 has ended.

Hi,
I have the equal problem:
[Thu Aug 11 12:01:15 2016] [error] [client xxxxxxxxxxxx] Premature end of script headers: admin.php, referer: https://xxxxxxxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s

I try the version 2.0 beta an also produces the equal mistake.
Any solution?

Thanks

I try the version 2.0 beta an also produces the equal mistake.

I need to be able to reproduce this error, so please outline exactly how I can see it happening.

Hi,
I go to https://xxxxx/wp-admin/admin.php?page=loco-translate
and Internal server error appear

https://prntscr.com/c4cqrw

My memory_limit is 256M. The Logs show me this ->

[Thu Aug 11 12:57:24 2016] [error] [client xxxxxxxx] Premature end of script headers: admin.php, referer: https://xxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s

BR

That is a link to version 1 of the plugin. You said you are using version 2.

I’m guessing you clicked the return link from the plugin activation page, but the links in the new version have changed. I guess this is going to be an issue for others when switching over, so I’ll add in some kind of redirect.

However, the screen that WordPress should give in this situation should not give you a 500 error unless something else is wrong.

Hi Tim

yes I made a mistaki upload de version. I put the 2.0 and works Fine

Thanks for your time!

no problem. I’ve added a legacy link redirect into v2 now anyway, hitting page=loco-translate will redirect to page=loco. Serves me right for changing the page slug, but I got tired of it being so long.