Home Forums WoodMart support forum Warning: Illegal string offset

Warning: Illegal string offset

Viewing 21 posts - 1 through 21 (of 21 total)
  • Author
    Posts
  • #223971

    alkasmi
    Participant

    i have many error , below one of theme and attach an image of the screenshot:
    Warning: Cannot assign an empty string to a string offset in /home3/xkodnet/public_html/wp-content/themes/woodmart/inc/options/class-options.php on line 229

    Warning: Illegal string offset ‘favicon_retina’ in /home3/xkodnet/public_html/wp-content/themes/woodmart/inc/options/class-options.php on line 229

    Attachments:
    You must be logged in to view attached files.
    #223982

    Artem Temos
    Keymaster

    Hello,

    Thank you so much for purchasing our theme and contacting our support center.

    Could you please disable all plugins that are not related to our theme and provide us your admin access so we can check it?

    Thank you in advance

    #223984

    alkasmi
    Participant

    ok i have send what you asked

    #224013

    Artem Temos
    Keymaster

    Please, disable all external plugins that are not related to our theme.

    #224022

    alkasmi
    Participant

    Ok i disabled the pulgins that are not related to the theme

    #224026

    Artem Temos
    Keymaster

    Thank you. Please, provide us your FTP access as well.

    #224027

    alkasmi
    Participant

    ftp access

    #224114

    Artem Temos
    Keymaster

    Your Theme Settings were somehow removed from the database. We have reset them to defaults and now it seems to work correctly.

    #224173

    alkasmi
    Participant

    hi,
    it worked fine but while i’m editing on setting it returns like before , i tried to reset the setting but it still not working fine please help

    #224189

    alkasmi
    Participant

    i found that one i change the botton color in the setting this issue happen again

    #224196

    Artem Temos
    Keymaster

    OK, please, don’t touch anything on the website while we are trying to fix the problem. We will reply when we finish.

    #224207

    alkasmi
    Participant

    but please don’t let me so long

    #224216

    Artem Temos
    Keymaster

    We have downgraded WPML String Translation plugin and now it seems to work correctly. Please, don’t update it now. We are investigating what is wrong with the latest version.

    #224477

    alkasmi
    Participant

    hi,
    have you done investigating what’s wrong bcaouse i couln’t use the WPML becouse of the downgraded you made ,it’s asked me to update so what sould i do ?

    #224480

    Artem Temos
    Keymaster

    You can just ignore that message and continue using WPML. We have contacted WPML’s team and waiting for their response. We don’t have any ETA when this issue will be fixed.

    #224809

    alkasmi
    Participant

    i can not ignore the message, it’s not allow me to continue i attached a screenshot to explain more

    Attachments:
    You must be logged in to view attached files.
    #224813

    Artem Temos
    Keymaster

    We have changed the plugin’s version. Please, check how it works now.

    #225607

    tiagonunes
    Participant

    Greetings,

    I am having the same exact problem. How can I fix it?

    Best Regards

    Attachments:
    You must be logged in to view attached files.
    #225642

    Artem Temos
    Keymaster

    Hi @tiagonunes,

    Please, create a separate topic and send us your admin and FTP access so we can check.

    Regards

    #226487

    alex.l
    Participant

    Hi,
    We faced with the same problem. After saving theme setting we’ve got a lot of warnings in /wp-content/themes/woodmart/inc/options/class-options.php. Theme settings were crushed.

    After updating WPML String Translation plugin to version 3.1.2 the problem has been disappeared.

    According WPML String translation release notes they fix it.

    Thanks to XTEMOS team for amazing theme and quick support! We’re really enjoying Woodmart theme!

    #226567

    Artem Temos
    Keymaster

    Hello,

    Yes, this bug is already fixed by WPML team so you just need to update the String Translation plugin.

    Kind Regards

Viewing 21 posts - 1 through 21 (of 21 total)