Ticketmaster is a pain: "Secure Ticket selection is required"

tl;dr If you get a “Secure Ticket selection is required” error when trying to pay for a ticket on the Ticketmaster website, temporarily turn off all your adblockers and reload the webpage.


Nadia and I have gone to the Australian Open tennis tournament in Melbourne pretty much every year since 2007.

Collage of selfies of a man and woman at a tennis tournament. In most photos the pair are outdoors and are wearing hats. In one of the selfies they are standing in front of Rod Laver Arena.

So when the pre-sale for AO25 kicked off today, I went to buy us a couple of tickets.

Screenshot of an email that reads, across multiple lines, “AO25. The hottest tickets in town. Get Set! Your AO25 Pre-Sale hits today. Your access code to early tickets.”

But the Ticketmaster website kept spitting out this “Secure Ticket selection is required” error every time I tried to make the final payment.

Screenshot of a website form-submission error that reads only, “Oops! Secure Ticket selection is required.”

The problem, of course, was that there was no ‘Secure Ticket’ selection visible on this page for me to make.

So I did what any normal person would do: I fired up my favourite search engine and ran a search on that phrase :)

To my surprise, I got only a single hit to a Reddit thread from about a year ago.

Screenshot of a search engine result from the Moto GP subreddit on the topic of ‘Phillip Island race’.

Since most of the people on that thread didn’t have an answer, and the solution only comes at the end of the thread, I figured I’d write this quick post to add to those search results.

Basically, the ‘Secure Ticket’ selection loads from a third-party website and that third-party website component gets blocked by your adblocker. The fix is to temporarily turn off your all your adblockers and reload the page. When you do that, you’ll see the ‘Secure Tickets’ component that was missing from the page before.

Screenshot of a webpage component titled, ‘Secure Tickets’. This upsell tells you that “By upgrading your tickets to a Secure Ticket you will be eligible to receive a refund if you are unable to attend this event for any of the reasons in our Secure Ticket Terms and Conditions”. This component forces you to make a choice between, “Yes, please upgrade me to a Secure Ticket for an additional $8.62” and “No, thank you. I do not wish to upgrade to a Secure Ticket”.

It’s a pain that you’re forced to actively say “no” to this upsell, but I appreciate that they don’t automatically opt you in to it. (Which they’d be fined for if they did, of course.)

But it’s a bigger pain that they haven’t yet implemented this upsell into their main ecommerce sales path, and so it has to load from a third-party domain.

I would have assumed they did this deliberately, thereby forcing people to turn off their adblockers. But if that was the case, they would have told us what to do in the error message. Since they didn’t do that, we can’t attribute this stuff-up to malice – which I guess is a plus, given all the other reasons to dislike Ticketmaster!

Anyway, now you know the workaround so you know what to do if you get that error. (*sigh* What a world we live in.)


PS, for completeness’ sake: a search on Google for that error notification gave me just 14 results, with the top one being the same as the one from DuckDuckGo.

Screenshot of search engine results, the top one from the Moto GP subreddit on the topic of ‘Phillip Island race’.

Happy days!

The last twenty-four hours have been very exciting for me. At least in terms of typography.

That’s because, years and years after falling in love with the Chaparral typeface, I finally get to use it on my website! That and Myriad, which is the typeface I’m now using for the headings and navigation.

Wait. Something changed?

Before today I was using the excellent Merriweather for this website’s body text and Oswald for the headings and navigation.

Both those typefaces are free and open-source, and both are available through Google Fonts – which is the font collection you could pick from when building a site on Squarespace (the platform this website is running on).

Graphic showing two blocks of text side-by-side. The block on the left has the heading ‘Old’ and uses the Merriweather (body text) and Oswald (heading) typefaces. The block on the right has the heading ‘New’ and uses the Chaparral (body text) and Myriad Condensed (heading) typefaces.

I’d always thought about updating the typefaces on this site, but (a) I love Merriweather and (b) I didn’t want to go through the hassle of trying to see if there was anything better than Merriweather on Google Fonts.

Then last night I discovered that Squarespace now offers the full suite of Adobe Fonts to choose a typeface from, and so here we are :)

The decision about which typeface to use for headings and navigation was pretty easy too. I had a bunch of good options to choose from, like Proxima Nova, League Gothic, Brandon Grotesque, and Alternative Gothic (which both Oswald and League Gothic are reworkings of, by the way).

I ended up going with Myriad because (a) it’s a gorgeous typeface (basically a copy of Frutiger) and (b) both Myriad and Chaparral were created by Carol Twombly (in 1992 and 2000, respectively) when she was a type designer at Adobe. As you can see from the graphic above and, indeed from this website, the two pair really well.

Why is this a big deal to me?

This change in typeface is noteworthy because the only reason I started using Merriweather in the first place was because it is the closest free, high-quality alternative to Chaparral that was available on Google Fonts all those years ago. But now I get to use the typeface I wanted to use all along!

I am particularly pleased that, with just this small change, the vibe of this site has gone from “modern and sturdy, but also warm and readable” to “subtly classy, but also friendly, lively, and readable”.

Yay!  

New Squarespace Website!

In case you haven’t already noticed, we’ve upgraded our website.

We’ve moved from a basic, static HTML site that was built in 2008 to one that’s hosted on the fantastic Squarespace platform – which, by the way, I highly recommend.

Why the upgrade?

We upgraded the site because the old one was…well, old. Also, it was too manual and time consuming to maintain. This new site, on the other hand, is leaner, faster, and, overall, a more effective online presence for both me and Nadia.

The web has also changed a lot in four years. For example, your own website no longer needs to host your entire online life. You can do things like outsource your media storage and sharing to services like Flickr, YouTube, and Picasa Web Albums. And, on the social media side, you can outsource a lot of your micro-content and general web content sharing to services like Twitter and Google+.

But you know what the best part is? Using a professionally hosted web content management because that really makes website management both easy and a lot of fun.

What do you think of the new site? Love it? Hate it? Don’t care?

Time to Upgrade Our Website

Nadia and I have maintained our website at insanityWORKS.org since 2004. It was overhauled once (in 2007) and is past due for another major upgrade.

Moving to a Content Management System

This time, though, the plan is to move it on to a Content Management System (CMS). Much as I love getting down and dirty with HTML code (via Dreamweaver, of course) a CMS-based site will be much faster and significantly easier to maintain. At the very least we won’t be stuck managing it from only those computers that have Dreamweaver installed on them.

The question then becomes: Which CMS do I choose? I’ve been using both proprietary and open source systems since 2001 so I know a lot about a lot of them. That means I can use pretty much any one that’s out there quite effectively; though I do plan to use an open source one for this site.

Fortunately, my choice is limited by the ones that my web hosting provider, E-Starr, provides automatic support for (specifically, installation and upgrade support). I’ve used a bunch of these CMSs in the past, too, so I’m already quite comfortable with most of them.

My Needs Have Changed

What’s also good is that my personal website needs aren’t what they used to be three years ago. For example:

  • A lot of information about me is now available on my Google Profile
  • I now host my photos on Picasaweb (albums) and Flickr (photo stream)
  • I do most of my writing on my blogs (this one and my professional one)
  • I no longer need to maintain a PDF version of my CV for people to download because most of that information is available on my LinkedIn profile
  • A lot of the other content that I host on the site can be moved elsewhere (like Slideshare or Google Docs, for example)

What’s left, then, is mostly text content and a couple of archived websites. Any old CMS can handle the former and latter will remain the way they are so, all told, my CMS requirements are actually quite simple.

So, What Now?

What I think I’ll do now test a bunch of the CMSs available to see which one I like the most. I do have lots of options, including:

  • Drupal
  • Geeklog
  • Joomla 1.5
  • PHP-Nuke
  • phpWCMS
  • phpWebSite
  • Siteframe
  • TYPO3
  • Xoops

Not to mention WordPress, which can be tweaked to make a pretty good CMS itself.

So, if all goes well, I will report back in a few weeks, by which time I hope to have the newest version of insanityWORKS.org up and running.

Wish me luck!