Warning: Illegal string offset

  • I’m getting the following errors. I have included the code when I look up the code in Notepad++:

    Warning: Illegal string offset ‘content_css’ in /homepages/16/d424488600/htdocs/clickandbuilds/MYWEBSITE/wp-content/plugins/custom-squeeze/custom-squeeze.php on line 3505

    CODE: $initArray[‘content_css’] = “../wp-content/plugins/custom-squeeze/css/mystyle.css”;

    Warning: Illegal string offset ‘theme_advanced_font_sizes’ in /homepages/16/d424488600/htdocs/clickandbuilds/MYWEBSITE/wp-content/plugins/custom-squeeze/custom-squeeze.php on line 3517

    CODE: $initArray[‘theme_advanced_font_sizes’] =”10px,11px,12px,13px,14px,18px,24px,36px”;

    Warning: Illegal string offset ‘font_size_style_sizes’ in /homepages/16/d424488600/htdocs/clickandbuilds/MYWEBSITE/wp-content/plugins/custom-squeeze/custom-squeeze.php on line 3529

    CODE: $initArray[‘font_size_style_sizes’] =”10px,11px,12px,13px,14px,18px,24px,36px”;

    How do I fix this please???

    The theme I’m using is OptimizePress and the plugin is WpEzpages. I have both of these on an identical site with no errors. What I did do is try to install the theme to this website by copy/pasting from the 1st website’s hosting to the new website, I don’t know if that’s what caused it, I’ve since deleted the theme and re-installed it properly through the WP backend, but still have the problem.

    The code strings in the working website for these lines are identical to the ones pasted here, FYI.

    I’d appreciate your help.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator t-p

    (@t-p)

    Try deleting “custom-squeeze” plugin via FTP or SFTP or whatever file management application your host provides.

    Thread Starter myattitude

    (@myattitude)

    Deleting the plugin isn’t an option as I want to keep it. I was hoping there was a way to FIX the error rather than delete it?

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Then you need to talk to the people who gave this plugin to you. It doesn’t look like it’s a plugin we support.

    Thread Starter myattitude

    (@myattitude)

    Hmm, I speak with other people who use the exact plugin and have no troubles. I think it’s something to do with WP on my end. What could it be?

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    How familiar are you with PHP?

    Thread Starter myattitude

    (@myattitude)

    Not at all but I can learn…

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Hopefully you can get support from your plugin’s authors.

    Thread Starter myattitude

    (@myattitude)

    They’re long gone. Isn’t there something I can do from here?

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    I was going to suggest you var_dump $initArray and then you can at least have an insight as to why you’re getting the error – but I don’t think you would spot the cause of the problem if you saw it

    Thread Starter myattitude

    (@myattitude)

    No I don’t know what var_dump $initArray is. How can I do var_dump $initArray and what should I look for?

    Thread Starter myattitude

    (@myattitude)

    Or, is there at least anyway to HIDE the error from showing when visitors come to the site?

    https://i.gyazo.com/7dc256b73b37c50419fcd37eb3dcf308.png

    Because the plugin actually functions just fine. It’s just the error being displayed that spoils the website for the visitors.

    Thread Starter myattitude

    (@myattitude)

    I have new information:

    It turns out the line:

    Warning: mysql_real_escape_string(): No such file or directory in /homepages/16/d798623345/htdocs/clickandbuilds/MyWebsite/wp-content/plugins/opt/includes/dwpc.php on line 1

    is referring to a MySQL (see d798623345) of another domain I have the plugin uploaded to. So when I upload the plugin to new domain with a different MySQL, it isn’t finding the directory.

    So what can I do to make it find the MySQL directory it IS uploaded to?

    Thread Starter myattitude

    (@myattitude)

    Woops, I was wrong, the number does NOT refer to MySQL. But I did look up the dwpc.php file on an html editor and searhced within it “mysql_real_escape_string“

    I found this part of code:

    ;$ip_address = mysql_real_escape_string($_SERVER[‘REMOTE_ADDR’]); $user_agent = mysql_real_escape_string($_SERVER[‘HTTP_USER_AGENT’]);

    What should I do to to make sure it works?

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Warning: Illegal string offset’ is closed to new replies.