error warnings

  • Resolved computerfreaks

    (@computerfreaks)


    9 years, 2 months ago

    I have a problem with my woocommerce multilagual plugin related to woocommerce appointments, i get following error codes:

    Warning: Illegal offset type in isset or empty in /kunden/289160_5023/webseiten/wp-content/plugins/sitepress-multilingual-cms/inc/taxonomy-term-translation/wpml-term-translation.class.php on line 38 Warning: Illegal offset type in isset or empty in /kunden/289160_5023/webseiten/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php on line 247 Warning: mysqli_real_escape_string() expects parameter 2 to be string, object given in /kunden/289160_5023/webseiten/wp-includes/wp-db.php on line 1171 Warning: Illegal offset type in isset or empty in /kunden/289160_5023/webseiten/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php on line 257 Warning: Illegal offset type in /kunden/289160_5023/webseiten/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php on line 258 Warning: Illegal offset type in isset or empty in /kunden/289160_5023/webseiten/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php on line 262

Viewing 6 replies - 1 through 6 (of 6 total)
  • George Botsev

    (@botzev)

    9 years, 2 months ago

    Hello and thank you for contacting us.
    This seems to be more a problem with WPML, than WooCommerce Multilingual because of the warnings that you provided.
    As far as I see at these places we expect to receive a string value, and instead we receive an object value.
    This means that there is something wrong maybe with the translation of the terms and some term may not be properly translated or something else from the database.
    In any case please try and check for the term involved and translate it if not translated.
    If you have difficulties with this, I would suggest that you open a new ticket in our support forum at wpml.org and point to this ticket, so that our expert supporters help in the debugging of the issue.

    hudin

    (@hudin)

    9 years, 2 months ago

    Seeing errors as well after updating to 4.1

    PHP Fatal error: Class ‘WPML_File’ not found /wp-content/plugins/woocommerce-multilingual/inc/currencies/currency-switcher/class-wcml-currency-switcher-templates.php on line 31

    etc

    Downgrading, thanks.

    George Botsev

    (@botzev)

    9 years, 2 months ago

    I am not sure if it is the best solution to downgrade WooCommerce Multilingual, since you obviously have older WPML than 3.6.3

    hudin

    (@hudin)

    9 years, 2 months ago

    I have WPML 3.4.1

    hudin

    (@hudin)

    9 years, 2 months ago

    Downgrade hasn’t fixed it. Shop is still offline and spewing a 500 error. What needs to be changed to fix this. I have a campaign going today and this is ill-timed.

    George Botsev

    (@botzev)

    9 years, 2 months ago

    Latest version of WPML is 3.6.3 and the class WPML_File is introduced (if I recall correctly) in WPML 3.6.0

    Error 500 is completely different thing and you have to enable debugging so that I can try to think of some reason why this is happening.
    The error could be in the server log or in the debug.log from WordPress.
    To enable debug logging in WordPress you need to set this options in wp-config.php
    above the line that says:
    /* That’s all, stop editing! Happy blogging. */


    // Turn debugging on
    define('WP_DEBUG', true);

    // Tell WordPress to log everything to /wp-content/debug.log
    define('WP_DEBUG_LOG', true);

    // Turn off the display of error messages on your site
    define('WP_DEBUG_DISPLAY', false);

    // For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
    @ini_set('display_errors', 0);

    Please do note to remove any other instances of this code if you have it in the file:

    define('WP_DEBUG', false);

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

The topic ‘error warnings’ is closed to new replies.