Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Chouby

    (@chouby)

    Hello,

    I don’t see any error coming from Polylang in your logs. I can see warnings coming from the Lingotek plugin. They are however rather strange as they are related to undefined constants which are in fact defined in Polylang. The only cases I can see where Polylang doesn’t define these constants are when either WP is too old or PHP is too old. In these 2 cases, Polylang deactivates itself and displays an admin notice about the reason. Lingotek may fail to detect this edge case.

    That said, warnings should not cause an error 500.

    Thread Starter Davide Ardizzola

    (@dardizzola)

    But, why if I deactivate polylang I don’t get any error?

    Thread Starter Davide Ardizzola

    (@dardizzola)

    Now I’ve deactivate Lingotek and activate Polylang, I get same 500 server error
    and this is the error log:
    10/03/2021 15:27:48 [error] [client 188.216.123.146] – https://www.abruzzo-segreto.it – End of script output before headers: index.php

    Plugin Author Chouby

    (@chouby)

    Hello,

    If you deactivate Polylang, Lingotek deactivates itself, that’s why warnings are not displayed. As I wrote, these warnings are unlikely the source of the error 500.

    Unfortunately, your new error message doesn’t help me to understand your issue. I can interpret PHP errors ike your warnings but not this one. I suggest that you contact the support of your host provider to know more.

    Thread Starter Davide Ardizzola

    (@dardizzola)

    >> . I suggest that you contact the support of your host provider to know more.

    Curious: the host provider said the same about you.

    So, I’m stucked.

    Plugin Author Chouby

    (@chouby)

    Are they not able to provide you the meaning of this error?

    I suggest that you make a copy of your website to install it on your local computer. Then you set WP_DEBUG to true in your wp-config.php. Maybe you’ll see a more meaningful error message.

    Hi ! I do have the same problem, even with the new update. I am running with PHP 7.3, is there a way to avoid those 500 internal server error ?
    Thanks

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘500 Internal Server Error’ is closed to new replies.