Since the the beginning of October, we’ve had sporadic reports of problems with the membership renewal form on the ALA website. Sometimes it was slow-loading pages, other times there were broken links or the authentication didn’t work.
Until last week, we were unable to replicate the problems, which made troubleshooting them difficult. We knew it wasn’t something across the board, because online transactions are actually up from last year for the period from September 1 through November 6.
| Transaction Type | 2007 | 2008 |
|---|---|---|
| Dues | 4,636 | 4,744 |
| Events | 3,873 | 4,396 |
So there was a problem, but it wasn’t happening to enough people to help us pinpoint where it was occurring. However, with the help of a couple of very patient members, we’ve finally figured it out. There were actually three separate problems, which is why it took so long to track down the threads.
The first was a bad redirect, now fixed. The second was the renewal form itself. We tried to improve its usability but accidentally broke some code without realizing it. Again, this is fixed now. The third issue required more time to deal with, because it involved upgrading the ecommerce server to the same version of ColdFusion that the website uses. In the process, we rebuilt that server from scratch, so hopefully the software and code are both a lot cleaner now.
I think part of the problem is communication, because when people have faxed or mailed us print renewal forms in the past, one of the things they’ve told us is that they were unable to register online. We do work with librarians who truly can’t (or don’t want to) register online, but that’s different from “your website won’t let me register online.” Clearly, we need to ask better questions when someone tells us that, so please don’t be offended when we do. We know you just want to complete your transaction and move on, but we need to get a better understanding of went wrong for you. So when you report this type of problem, it helps if you can tell us the operating system for your computer, the version number of the browser you’re using so that we can try to replicate the issue, and the link you used to get to the page.
So we think all is well now, but if you run into any problems using forms on our site or encounter any slow-loading pages (especially involving ecommerce), please report them to us immediately so that we can follow up with you.
And to the member who kept trying to renew for three weeks before finally giving in and calling, thanks for being so persistent! 🙂 Seriously, though, if that happens again, please don’t wait that long to let us know you’re encountering a problem. We know you were probably giving us the benefit of the doubt because of the site redesign, and we really appreciate your repeated attempts, but no one should have to go through that kind of misery. Send us an email, use the site’s feedback form, give us a call, leave a comment on any post here, whatever – we just want to help resolve it for you.
This morning, we experienced a brief period (an hour or two) during which messages destined for ALA mailing lists on our Sympa server were being bounced. The problem had to do with the email aliases file on the mail server where Sympa resides. That file has been restored to a previous version. The root cause of the problem is being investigated, but full service has been restored. The quick return to functionality was in no small measure due to fast error reporting on the part of ALA staff, for which we are grateful.
1. Website (Louise)
Critical things you need to know about:
a. You need to fill out the new SEO (Search Engine Optimization) metadata fields because they are now required; if you get an error message on check-in about a required field not being filled out, it’s probably a metadata field
question – we can use phrases, too?
answer – yes, just separate them by commas
need congruency between the metadata title field and the actual title field – they have to match for the alphabetization to work properly on the listings pages
b. Some listing pages are still blank (eg, “Government Documents,” even though we have a whole Round Table devoted to this topic) and need content. Karen Muller will tag the things she knows are applicable, but it’s going to take a coordinated effort – everyone needs to pitch in to the areas that are relevant to them, because if we don’t add the content, we need to take down the aggregated pages.
c. We’re seeing some problems with Firefox 3 – Collage won’t let you upload anything (images, etc.). We also think we’re having transaction problems on the site with FF3, so if you receive a complaint, please ask the user if they are using this version of the browser. We’re trying to determine if we have a systematic “superbrowser compatability problem” or if it’s an isolated issue.
Please help us track this issue and let us know when you hear about problems with slow pages, authentication issues, etc.
2. Web Editorial Board (Louise)
Louise noted a handout about the purpose of the Web Editorial Board Tag Team, a group that has rights to the entire site and can make quick fixes without requiring permissions first. These are considered “Tier 1” changes, and the Team will always communicate changes to the owning unit, even if it’s afterwards. The charge empowers the team to handle these types of issues.
Tier 2 fixes will have the Tag Team contacting the owning unit before making the suggested changes.
Tier 3 would be things the Team discusses with you and you then change.
The approach will be an ad-hoc one, although we may split up the work to handle specific sections of the site.
If you have questions about any of this, contact Louise or Karen Muller.
3. ALA Connect (Jenny)
Jenny showed the prototype, pre-alpha testing site for ALA Connect to give staff a sense of how the site functions
4. Keeping up with developments (Sherri)
Blog w/RSS Feed – http://itts.ala.org/update/
Wikis – http://wikis.ala.org/learningcollage ; http://wikis.ala.org/webplanning
5. Q&A / Wrap up