[Jeremy]

Developers, are, in general, trained to handle major releases with more caution than point-releases.

I’m going to run a major WP overnight, like when 4.2 released. I’m going to turn off caching and monitor for error. Point releases are easier to manage, and less risky.

I know Eventbrite’s updated API pushed this update faster than you may have planned, but I think its risky to tie extension releases to the core release. If you need to make a major release to aa extension, push the core version to a major number too. It will give me the heads up that “hey, stuff might break” and “don’t do this during high traffic”.

I know I was frustrated yesterday, mostly because I was losing money, but also because I wouldn’t have run that update had I known there was such a big risk of major stuff breaking.

More than anything, I’m most annoyed that the function for the EB tickets box name changed (on a point release). It wasn’t in the notes, as I mentioned above.

[Jeremy]

Please note it did not come down to clearing the cache.

It came down to deleting the .htaccess file and then rebuilding a fresh .htaccess. The cache wasn’t the issue, rewrite rules installed by WPSuperCache was an issue. Perhaps a bugfix will be adding a more robust rewrite rule, as well as noting caching systems can interfere in documentation.

Also, I read patch notes. There was no mention of the function name change for tickets output. So my tickets box moving problem was not communicated in patch notes.

I don’t need a free license. Thanks for the offer.

[Jeremy]

Believe it or not, I got it working.

First off, a few things:

I’m shocked that a point-release featured such a major change. I know that Eventbrite pushed their API update when they did, and I know, as a long-time user of this plugin that I know that the old API creditialing was a pain, but us developers know to watch major releases for major changes. A warning to license holders would’ve been nice. I would’ve held off an update until my major sales period was over.

Other things were changed too. For instance, the tickets iframe positioning function. These are the kind of changes that should have warnings associated. There are developers that build sites that rely on things staying the same by their plugin dev. Part of my chaos today, once I finally got EB authorized, was finding where the heck my tickets went! Last year, when I built this site, I moved them to the top using your knowledgebase articles. So, I thought stuff was still broken until I accidentally scrolled down and saw them in their default spot. This is something that shouldn’t’ve changed. And I posted separately that the knowledgebase is still out of date. I found the fix by delving into code.

I’m using WPSuperCache, one of those most common caching for WP sites, and although I deactivated it AND reset permalinks, rules added to the .htaccess by the plugin perpetuated after it was deactivated. One of those rules was the source of issue.

I deactivated WPSUPERCACHE, then deleted the .htaccess from the root, then rebuilt permalinks, then did the authorization.

So the problem was a caching issue. The steps outlined above are a for-sure way to delete all the caching-related rewrites.

[Jeremy]

And why do you need to replicate the issue on your end when I’ve provided a link to my site and proved the issue is live? What do you need from me to help you mimick a failing environment?

[Jeremy]

I am unable to bring my site to a local environment. I saw that was a suggested solution but that is not a viable solution for all of us.

What I could do is manipulate the database with the returned authorization code if it is stored in a settings hash, but I don’t know how it looks. All I know is I’m loosing hundreds of dollars per hour right now and I need a solution ASAP.

I’ve followed all the to-do’s you guys suggest. But I need help now.

Can you please arrange to send me a working, older, version of the plugin?

[Jeremy]

So if I go to:

http://camps.bonanzaed.com/tribe-oauth/eventbrite/?code=

It redirects to home.

If I go to that URL with the code in it, it gets a “content not found” error:

http://camps.bonanzaed.com/tribe-oauth/eventbrite/?code=X

Likley, the regex that reads the querystring isn’t working.

[Jeremy]

So you know:

I have four plugins on my site, three of them are yours. I turned off the other one. No fix.

I switched to 2015. No fix.

I cleared my cache. No Fix.

I flushed rewrites. No Fix.

I’m an experienced WP developer. I know how this stuff works. I don’t know why you’d make such a major change to a plugin in a point update without any warning. With all the WP security issues we’ve had this month everyone is hyper-focused on keeping updated. This is a major change to handling of API authorization and this is obviously not well tested.

[Jeremy]

That works great.

One last question: Is there a shortcode or query-value I can use to get the eventbrite link so I can make up one? I want a link that says “Click here if you have a voucher code or promo code” that goes directly to EB, since we can’t do that on the site.

Thanks!

[Author]

Posts