Retraction Watch is back at full speed. Here’s what you need to do to make sure you’re seeing our content.

Our readers will likely know that the site has been having significant trouble for more than two weeks. Thanks for your patience, your offers to help, and for sticking with us during that time. We’re happy to say that we seem to have identified all of the various issues involved, and have solved them. Some of those fixes may mean that you’ll need to resubscribe to our email alerts, so keep reading (or skip over the vaguely technical stuff in the next few paragraphs if you’d rather).

Many of our readers were curious — or perhaps concerned is a better word — about what was causing the downtime and broken functionality. First, we have no evidence that were subject to a DDOS attack, or to a hack. The site is constantly monitored for those.

So what was the problem? Readers have noticed that for some time — a few months, at least — they would have trouble accessing the site for a minute or two after we published a new post. For a while, we thought that was because a high percentage of the 15,000 people who had signed up for alerts about new posts were hitting the site at once. In the spirit of transparency, those brief outages may have been a canary in the coal mine that we should have paid more attention to. We did brief investigations into what was causing that problem, but they didn’t turn anything up, so as frustrating as they were, we didn’t keep them at the top of the priority list.

Starting February 8, however, the site began behaving very badly. It would go down for hours at a time, seemingly without warning. When it did come up, the newest post wasn’t on the homepage. The RSS feed broke repeatedly. Trust us, it was as frustrating for us as for everyone else.

We spent hours on the phone and in online chats with our host, and with WordPress gurus, trying various solutions. We optimized the site. We turned plugins on and off. We upgraded the version of PHP we were running. We bought more RAM. We switched email software so that we could space out delivery and not hit the servers all at once. (More on that in a bit.)

The site began performing better, but not perfectly. A few days ago, unbeknownst to us, our comments stopped working. Then, yesterday, one of the gurus at WPMU-Dev — these folks are great; check them out if you’re running WordPress — suggested that the comment problem might be due to a conflict between the theme we’ve been using since 2010 — called Journalist — and new versions of WordPress. Sure enough, when we reverted to a generic WordPress theme, comments worked again. New posts showed up on the homepage, and the RSS was fixed, too.

In the end, then, the theme may have been the central issue. The rest of the fixes, however, helped, and will likely keep the site more stable moving forward, so we’re keeping them. For now, we’re keeping the generic theme, too, but we will — carefully! — look into other options that could display our content better.

Here’s what that all means for readers who want to keep up with our content. When we switched email software, some emails transferred over, and some didn’t. To put a positive spin on some of what happened in that migration: We learned, not surprisingly, that a number of people had switched jobs, and were signed up more than once. It was a way to clean up the email list a bit. But if you want an email alert every time we publish a new post, please sign up again. To do that, scroll down the page until a “Follow” button shows up on the lower right, and click on it, then enter your email.

Of course, if you’d like one daily email, sign up here for The RW Daily, which includes posts from the previous 24 hours, plus a preview of items that will show up in Weekend Reads. (And if you’re having trouble signing up, or with anything else, please contact us at

Thanks again for your patience. As we noted yesterday in Weekend Reads, some of these fixes came at a cost, so we’d be remiss in not asking if readers would consider making a donation to support us. See you online.

Like Retraction Watch? You can make a tax-deductible contribution to support our growth, follow us on Twitter, like us on Facebook, add us to your RSS reader, sign up for an email every time there’s a new post (look for the “follow” button at the lower right part of your screen), or subscribe to our daily digest. If you find a retraction that’s not in our database, you can let us know here. For comments or feedback, email us at

3 thoughts on “Retraction Watch is back at full speed. Here’s what you need to do to make sure you’re seeing our content.”

  1. Tks for the update, and good luck! However I must say that the new layout is terrible — unless if you are reading it in a mobile, perhaps. The main iframe is almost as narrow as the side bar, at 550px, and both take less than 1/3 of the screen. Most monitors today can show more than twice that width comfortably.

    I know it looks like a stupid request, but please fix that (wordpress supports PC/tablet/mobile layouts if I’m not mistaken), or at least please offer again the full text under RSS (instead of just a snippet) such that I can read you without getting a headache.

    1. Thanks for the feedback.

      We’ll certainly look into other themes, but we’re going to be very careful about making such changes given that our old theme was what seems to have broken the site in the first place. In the meantime, what you describe — “The main iframe is almost as narrow as the side bar, at 550px, and both take less than 1/3 of the screen” — isn’t what we’re seeing. Here’s a screenshot.

      As far as full text RSS, we haven’t offered that in a number of years. We prefer to know how many people are accessing the site, and for them to engage with the content on screens or mobile.

      Thanks again.

  2. Much like in research, people have these sorts of problems with websites but often don’t write about them. Thanks for writing this article.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.