Polylang 1.5.3

Polylang 1.5.3 aims to fix some annoying bugs. Creating a new blog when Polylang is network activated resulted in a fatal error since Polylang 1.5.1. This issue should be now fixed.

Also some users (it seems that all are hosted at GoDaddy) experience  a random fatal error. I did not elucidate the reason for this, but at least tried to find a fix to avoid it. So if you get the error:

Fatal error: PLL_Model::_languages_list(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition “PLL_Language” of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition

Putting this line in your wp-config.php:

define('PLL_CACHE_LANGUAGES', false);

should solve the issue.

I chose to make the fix an option because it has a (slight) negative impact on performance and, as far as I know, is needed only for sites hosted at GoDaddy.

For people experiencing a fatal error when using both the Avada theme and Polylang, this new version of Polylang does not solve the issue, but I am glad to announce that it will be solved in the next version of Avada. The theme authors have worked on this. So please be patient until the next Avada release…

As usual, the complete changelog is available in readme.txt.

2 thoughts on “Polylang 1.5.3

  1. Eric

    Hi, Unfortunately, the wp-config.php modification for the fatal error when hosted on GoDaddy is not working. Or at least, it is not working all the time. It is still throwing the fatal error in a ramdon fashion (it looks random but never really is). You might be facing a race condition.

    1. Frédéric Post author

      Yes. That’s bad news and you are the second to tell me that today. The attempt above was a blind one because I have really no clue why this error occurs and why it seems to occur only on sites hosted by GoDaddy. I will try looking for clues on the forum.

Comments are closed.