Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author ovann86

    (@ovann86)

    Hey Dana,

    Thanks for reporting, I’ll take a look now.

    Im curious as to how WordPress reacted – white screen of death or just failed to do the update and left you with the previous version intact?

    Plugin Author ovann86

    (@ovann86)

    I’ve had a look and I can’t see a reason for why it errored.

    What I will do is run the file through a clean up, in case there’s something wrong with the file itself and re-write the code in that area to remove the opening and closing php tags.

    Hopefully that’ll sort it out, but as I cant make it happen here I wont know until you confirm ??

    Thread Starter rdanamcd

    (@rdanamcd)

    Hi Thanks,

    I downgraded back to 1.7.4 and back to normal. I’m trying again on 1.8.1. This is the only plugin I’m updating… right after updating I hit refresh or just going to the homepage I get the following errors:

    Parse error: syntax error, unexpected ‘}’ in ../wp-content/plugins/ajax-upload-for-gravity-forms/gravity-forms-ajax-upload-addon.php on line 332 Notice: is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in ../wp-includes/functions.php on line 3897 Notice: is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in ../wp-includes/functions.php on line 3897

    I downgraded back to 1.7.4 and it’s back fine.

    Thanks
    Dana

    Plugin Author ovann86

    (@ovann86)

    Hey rdanamcd – sorry about the issues you had.

    I think your issue stemmed from me inadvertently using a PHP short tag opening, or at least that was the problem I saw when I looked (from memory, it was a week ago now).

    You should be able to upgrade to the latest version again, if not please let me know.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error after updating 1.8’ is closed to new replies.