Notices during import

  • Resolved Grégory Viguier

    (@greglone)


    11 years, 12 months ago

    Hello.

    I don’t think it will help a lot but, here are some php notices I had during the import:

    Notice: Trying to get property of non-object in /mon-petit-poney/wp-content/plugins/polylang/include/mo.php on line 36
Notice: Trying to get property of non-object in /mon-petit-poney/wp-content/plugins/polylang/include/mo.php on line 41
Notice: Trying to get property of non-object in /mon-petit-poney/wp-content/plugins/polylang/include/mo.php on line 36
Notice: Trying to get property of non-object in /mon-petit-poney/wp-content/plugins/polylang/include/mo.php on line 41

Import from WPML to Polylang should have been successul!

    WP 3.9.1
    Polylang 1.5
    WPML to Polylang 0.1.2

    It’s a Multisite installation (with 2 sites), and the notices displayed for the main site only, not the other one. Both plugins are network activated.
    As a result, the default administration language was not set correctly (en_US instead of fr_FR). So, nothing important in the end.

    Greg

    PS: “successful”, not “successul” 😉

    https://ww.wp.xz.cn/plugins/wpml-to-polylang/

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

    (@chouby)

    11 years, 12 months ago

    Hi Greg,

    Thank you very much for the bug report. I am glad to get feedback on this plugin.

    I guess that the working site has no strings translations and that you lost the strings translations in the main site. I just uploaded a dev version (0.1.2.1) which should fix this issue.

    For the default administration language, I found an ‘admin_default_language’ key in WPML settings but I don’t use it.

    The Polylang default language is set from the WPML setting ‘default_language’. And the default admin language is just the language of the WordPress install (set by WPLANG is wp-config.php). There is not option to override this in Polylang

    The “should” in the success message is important 😉

    For my information on how this plugin sucessfully (or not) works, did you migrate from an install using the latest WPML version 3.1.5?

    Thread Starter Grégory Viguier

    (@greglone)

    11 years, 12 months ago

    Hey.

    Indeed, I lost the strings translations in the main site. Luckily I had only few of them.

    For the default administration language I only had to go to “Settings” >> “General” and set “French” back. The other site was good.

    Erf, I forgot to mention my WPML versions, they are the latest ones:
    WPML 3.1.5
    WPML String Translation 2.0.5

    Thread Starter Grégory Viguier

    (@greglone)

    11 years, 12 months ago

    BTW…
    Stable tag: 0.1.2 ===> Stable tag: trunk
    Just sayin’ 😉

    Plugin Author Chouby

    (@chouby)

    11 years, 12 months ago

    Do you mean that it i resolved?

    Thread Starter Grégory Viguier

    (@greglone)

    11 years, 12 months ago

    I was able to get all back, so, let’s say yes.

    Plugin Author Chouby

    (@chouby)

    11 years, 12 months ago

    So let’s say that this small fix will make v0.1.3

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Notices during import’ is closed to new replies.