Illegal String Offset Warning

  • Hi guys,
    I have a website – https://zamkato.com
    And i’ve had the following error that’s been showing up for the past few days and i’ve been trying to fix it, but i see nothing wrong with any of my plugins or CSS files –

    Warning: Illegal string offset ‘custom_css_post_id’ in /home/content/n3pnexwpnas01_data03/75/3056475/html/wp-includes/theme.php on line 905

    I have seen this to be a common problem on the internet, however i am unable to find any solutions. I would be really helpful if someone could help me out please.

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

  • That looks like it may actually be generated by a conflict between the ‘nexus’ theme and the ‘wp-poll’ plugin for some reason. 

    /wp-content/themes/nexus/includes/shortcode/source/shortcodes.php on line 278..
.. headers already sent (output started at /home/content/n3pnexwpnas01_data03/75/3056475/html/wp-content/plugins/wp-poll

    You might first try temporarily renaming just the ‘wp-poll’ plugin folder and see if the errors go away. If not, temporarily rename the nexus theme folder, then try logging back in. That should probably let the default WordPress theme take over so you can figure out what the conflict might be.

    Thread Starter Zamkato

    (@zamkato)

    Thank you so much for the reply, i tried renaming both the files nothing seemed to help. I’ve been using the WP-Polls widget for quite some time now so i was surprised at first thinking it could’ve caused the problem.

    Not sure what to do next, any other suggestions?

    If functionality isn’t being affected and they’re only warnings, you can probably suppress them by turning off error reporting. That will give you some time to research a bit further and see if there might be a plugin or theme update that can eliminate the errors completely.

    [edit]

    Okay… Now I’m not sure what to think. I’ve been searching for clues as to what specifically may be happening here… (simple Google search for “/wp-includes/theme.php on line 905” Warning: Illegal string offset “custom_css_post_id” )

    …and the first similarity in the results that stands out for me, is the prevalence of “/content/n3pnexwpnasXX_data.XXX” in all the domains listed in the returned results for that specific error.

    A quick check revealed that all of the domains listed on page 1 and 2 of the results (I checked the first 8 unique domain names excluding the obvious www.ads-software.com and other forum discussions) are hosted by GoDaddy. I then jumped to page 4 of the search results and picked another domain name at random. That too, appears to be hosted by Godaddy. Then again on page 6, with the same results.

    I don’t know if that is just coincidence of an unlikely probability, or if it’s a pattern forming clue.

    Maybe someone with a sharper eye can spot something?

    • This reply was modified 7 years, 11 months ago by Clayton James.
    • This reply was modified 7 years, 11 months ago by Clayton James.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Illegal String Offset Warning’ is closed to new replies.