...the check I put in it to prevent it from being activated.
Which apparently didn't fire for me since it tried to activate.
Anyway, thanks for looking into this and pulling it for now.
Are there any other updates we might expect such behavior from, not that this behavior was expected. Just noticing a lot of update notifications lately...
Responses (7)
Member (joined June 2010) Likes (0)
I am also getting the same error.
Member (joined April 2009) Likes (0)
Sorry to hear it, but glad it's not just me!
Did complete loading of your site break after the attempted update? I'm trying to troubleshoot this issue.
Member (joined April 2009) Likes (0)
FYI: If the site does break for anyone else after this update, try this fix.
Lead Developer (joined May 2009) Likes (0)
It is the only one not backwards compatible. Hence the note in the chngelog and the check I put in it to prevent it from being activated.
Lead Developer (joined May 2009) Likes (0)
Ok, removed the latest version till 3.1 actually drops.
Member (joined April 2009) Likes (0)
Which apparently didn't fire for me since it tried to activate.
Anyway, thanks for looking into this and pulling it for now.
Are there any other updates we might expect such behavior from, not that this behavior was expected. Just noticing a lot of update notifications lately...
Lead Developer (joined May 2009) Likes (0)
I don't know of any. Antisplog was just too tied into core functions to keep backwards compatible.
Just always check the popup changlog before updating.
Become a member