Support » Plugin: All-in-One Event Calendar » Broken after Update to 2.3.7

  • Resolved kerrock


    Since the update, several lines of error “warnings” are now in the header and top of page where calendar is supposed to be.
    Here is one of the lines of error code:

    Warning: Illegal string offset ‘domain’ in /home5/namegoeshere/public_html/wp-includes/xxx.php on line 490

    Will there be another update to fix this mess?

    Thank you,

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Benjamin


    Hi Kerry,

    Please upgrade add-ons if you use them.

    We had no add-ons installed.
    We rolled back from a previous backup and now all the Events are gone.
    What do we do now?

    Plugin Author Calvin


    Hi kerrock!

    Is this the real and full error message? Warning: Illegal string offset ‘domain’ in /home5/namegoeshere/public_html/wp-includes/xxx.php on line 490

    If it is, then it doesn’t look like as it was caused by the updating our plugin, but to something related to your WP installation.

    No, that’s not the ‘real’ error string. (I wasn’t sure if there was anything confidential in the string that shouldn’t be shown so I substituted “namegoeshere/” and the “xxx”.php.)

    If it’s okay to post, I can send you a screenshot of the errors if that helps?

    Plugin Author Calvin


    Hi kerrock!

    Sure, please post the screenshot and I will try to help you out!


    I don’t see how to upload a jpg.

    BTW: After rolling back a backup and found our Events missing, we also rolled back the database and was able to restore all the Events, but the errors are still showing in the header.

    The Calendar is on a ‘test’ page so it wouldn’t be seen.
    Please view it here:
    p/w: test

    Plugin Author Calvin


    Hi kerrock!

    Which version of WordPress are you using?


    WP Version is 4.4.1

    Plugin Author Benjamin


    Hi kerrock,

    I see no error in the header, you were able to resolve the issue in the meantime?

    Well, that’s odd.
    We didn’t do anything except roll back to the previous backup – but the problem still presented itself after doing that.

    But, you’re correct – the problem does seem to be gone right now.
    Not sure how it could resolve on its own…
    Could just ‘waiting’ fix it??

    We will proceed with the hope that the problem is gone.
    Thank you for your time!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Broken after Update to 2.3.7’ is closed to new replies.