• Hi, we have a constant error. We use Polylang and have a home page in English with a German counterpart. If I am logged in WordPress and do any change, a few minutes afterwards and for several minutes, users get the error below.

    The error is below, the other things to know:
    1) Permalinks are set to “Post name”
    2) Static front page is “Home”
    3) Polylang settings are: “When the front page is visited, set the language according to the browser preference”, “The language is set from content”, “Remove /language/ in pretty permalinks”, “The front page url contains the language code instead of the page name or page id”.

    Thank you for your help!

    Here the error message:

    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 in/home/content/p3nexnas05_data03/06/2095606/html/wp-content/plugins/polylang/include/model.php on line 192

    https://wordpress.org/plugins/polylang/

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

    (@chouby)

    Hi!

    Could you please read this:
    http://wordpress.org/support/topic/fatal-error-1178

    Are you hosted by GoDaddy?

    *Before* trying to fix the issue, could you check your database for the _transient_pll_languages_list entry in the table wp_options and report the value field here?

    Then try to repair your database. Then if the issue is still there, could you try the fixes I propose in the other topic?

    Also could you give me your PHP version and MySQL versions?

    Thread Starter haimhouse

    (@haimhouse)

    Hi, thanks, I tried to replace the lines in polylang/include/model.php at line 139 as you suggested. So far it works, will test it, as the error sometimes comes up, sometimes not. One question: If I update Polylang, will I have to add this line every time again after update? Or will you fix it in the next version?

    Plugin Author Chouby

    (@chouby)

    Hi,

    At this stage, I am still looking for an explanation. The proposed fix decreases a bit the performance of Polylang, so it’s not my intention to modify definitely the code as proposed.

    That’s why my other questions are important to help me solving the issue.

    Thread Starter haimhouse

    (@haimhouse)

    Hi, sorry, it took a little longer. Here is the value:

    a:2:{i:0;O:12:”PLL_Language”:15:{s:7:”term_id”;i:13;s:4:”name”;s:7:”English”;s:4:”slug”;s:2:”en”;s:10:”term_group”;s:1:”0″;s:16:”term_taxonomy_id”;i:13;s:8:”taxonomy”;s:8:”language”;s:11:”description”;s:5:”en_US”;s:6:”parent”;s:1:”0″;s:5:”count”;i:39;s:10:”tl_term_id”;i:14;s:19:”tl_term_taxonomy_id”;i:14;s:8:”tl_count”;i:6;s:6:”locale”;R:9;s:6:”is_rtl”;s:1:”0″;s:5:”mo_id”;s:3:”732″;}i:1;O:12:”PLL_Language”:15:{s:7:”term_id”;i:15;s:4:”name”;s:7:”Deutsch”;s:4:”slug”;s:2:”de”;s:10:”term_group”;s:1:”0″;s:16:”term_taxonomy_id”;i:15;s:8:”taxonomy”;s:8:”language”;s:11:”description”;s:5:”de_DE”;s:6:”parent”;s:1:”0″;s:5:”count”;i:29;s:10:”tl_term_id”;i:16;s:19:”tl_term_taxonomy_id”;i:16;s:8:”tl_count”;i:6;s:6:”locale”;R:24;s:6:”is_rtl”;s:1:”0″;s:5:”mo_id”;s:3:”733″;}}

    What do you think? Regards!

    Plugin Author Chouby

    (@chouby)

    Your database looks good. So the problem is not there.
    Do you know your PHP version?

    Thread Starter haimhouse

    (@haimhouse)

    Hi, yes, we have PHP version 5.4.16

    Plugin Author Chouby

    (@chouby)

    Well I never tested specifically this version. But I tested older and newer versions, so I am not sure it is the source of the problem. Maybe some other specific server setting at Godaddy. I don’t know.

    I just released Polylang 1.5.3. With this version, you should disable the problematic code by setting:

    define('PLL_CACHE_LANGUAGES', false);

    in wp-config.php. So there will be no more need to modify the plugin code in the future.
    This will remain an option as it slightly decreases the performance of Polylang and works as is for most users.

    Thread Starter haimhouse

    (@haimhouse)

    Hi, sorry to ask, but where can I change the wp-config.php file? I have seen that it should be on the root directory, but as I use a managed WordPress-service by GoDaddy, the onliy thing I see is the usual WordPress user interface, where all configurations are done.

    I upgrade Polylang to 1.5.3 and get a fatal error
    (Fatal error: Call to a member function get_home_url() on a non-object in D:\Hosting\9409428\html\wp-content\plugins\polylang\frontend\choose-lang.php on line 166)
    i updated wp-config.php (as you told in http://wordpress.org/support/topic/fatal-error-1178) but problem persist.
    I DEACTIVATE all my others plugins and the problem persist.
    My website host in GoDaddy.

    @haimhouse you must use filezilla (open source application or another) to see via FTP your folders and try to change wp-config.php file in GoDaddy.

    FYI.
    I rollback to polylang 1.5 and problem disappear.

    Plugin Author Chouby

    (@chouby)

    @beto_bens
    There is something that I don’t understand. Did you experienced the problem described in this topic? With which version?

    Could you precise your Polylang settings?

    Hello Chouby,

    Sorry. But by mistake y duplicate my comment in two forums. I don’t have this problem, i have another that i answer you.

    Thanks for your help.

    Hi Chouby

    I have a similar problem. I installed Polylang with a Centum Theme from Purthemes, hosted by Siteground. I installed WordPress and Polylang automatically, so they should be the newest versions.

    I tried to use the language button in the top bar in the dashboard, then the whole admin panel broke. Now, when I login, I directly get a blank page with this line:

    Fatal error: Call to undefined method PLL_Links::get_translation_url() in /home/himala13/public_html/wp-content/plugins/polylang/include/wpml-compat.php on line 89

    I deleted the whole polylang folder via cpanel/FTP, then the error was gone. I reinstalled the plugin, and it was instantly there again. The plugin worked for a couple of hours before the error showed up the first time, and I really liked it. It would be pity if I can’t use it!

    Any ideas?

    Plugin Author Chouby

    (@chouby)

    @beto_bens, @mrflapjack
    Well. This topic is now completely messed and will be impossible to follow. Please open a new topic for your problem.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Fatal error at 'polylang"’ is closed to new replies.