by David Snopek on November 22, 2021 - 10:17am

Today, I have the unenviable task of announcing some bad news:

myDropWizard is closing down, with our final day of normal operation on February 25th, 2022.

This isn't our ideal outcome - until very recently we were working hard to prepare for the upcoming Drupal 7 End-of-Life (EOL) and were on the verge of publicly announcing the details of our D7ES plans. In fact, we had already started sharing those details privately with potential customers, and had most of the marketing materials ready to go.

However, in the sprit of Thanksgiving which is coming up later this week in the USA, there is much in the 6-year history of myDropWizard that I have to be thankful for:

  • The opportunity to collaborate with many wonderful, talented and passionate people over the years (especially my co-founder Elliot Christenson)
  • The support of our customers, which has given us the resources to do the important (but unglamorous) work we felt needed to be done
  • The goodwill of the Drupal community in supporting and contributing to our efforts (especially all the folks who posted D6LTS issues and patches)

Read on for more details about what this means for D6LTS and our customers.

Why is this happening?

I won't give too many details, but since I'm sure someone would ask in the comments if I didn't, I'll briefly address this right away. There are many contributing factors, but primarily:

  • The coronavirus pandemic had a very negative impact on our business.
  • The postponment of Drupal 7's End-of-Life, while good for the Drupal community, also postponed our (hopeful) recovery.
  • Other factors in the personal lives of our founders.

What does this mean for Drupal 6 LTS?

In July, we had announced that we'd be extending the end of our Drupal 6 LTS offering another year, until February 24th, 2023. This is something we had done every year since we first started doing D6LTS in 2016.

Unfortunately, this means that we're going back on that extension, and will be discontinuing our D6LTS offering on February 25th, 2022, along with all other normal operations of our business.

I'm sincerely sorry to any of our customers, or others in the Drupal community, who were depending on that extra year.

Luckily, there is still one vendor providing D6LTS: Tag1 Consulting. If you still need D6LTS, I recommend getting in touch with them.

What does this mean for our customers?

We will continue to provide the same support and maintenance services that you've come to depend on up until the very last minute - meaning 5pm CT on February 25th, 2022. That is a little more than 90 days from now.

We will finish any on-going projects, but won't take on any new ones. If you pre-paid for developer hours (ie. a "mini-project"), you can still request us to do development with the remaining hours until we stop operations. Or, if you want a refund for the remaining hours, we'd be happy to provide one via PayPal, if requested before we stop operations.

If we are providing managed hosting for your site on Linode, we can either:

  1. Send you backups of your current site so you can migrate to different hosting, or
  2. Transfer the server to your Linode account, allowing you to take over billing and control of the existing server

If there's anything I missed above, please don't hesitate to contact us to discuss the details!

We'd like to do what we can to make this transition as painless as possible for you.

Thank You!

I'm very proud of all the work that we've done at myDropWizard.

I'd like to say one last Thank You to all our customers, partners, and everyone who has ever worked for or with myDropWizard.

Thank You and Take Care!

Want to read more articles like this?

Subscribe

Subscribe to the myDropWizard.com blog and recieve e-mail updates when new articles are published!

Comments

Many thanks for your many contributions to D6LTS! All the best!

Thanks, @dsnopek, for all the work you've put into D6LTS! I'm sorry to hear this is happening.

Are you planning to do anything with the MDW updates system and/or make anyone else a maintainer of the d6lts github repo? Have you been in discussion with Tag1 about taking over any of that?

Thank you for all the years of hard work on D6LTS, and the incredible myDropWizard updates system. Wishing all the best for you and everyone else on your team!

Thanks!

If someone from the Tag1 team wanted to take over the "d6lts" group on GitHub, I'd be happy to hand that off! However, they have their own way of addressing D6LTS via their Quo product, and it seems likely they'll prefer to keep doing things that way.

I just saw the comments over on the D.O issue queue where they linked to their own repo (https://www.drupal.org/project/d6lts/issues/3259488). I'll check that out. Thanks again!

Thank you David and your team for your contributions especially on d6lts. I wish you all the best for the future.

Who ends up here and doesn't know how to proceed, there is some additional information under: https://www.drupal.org/project/d6lts/issues/3259488

Sorry to hear this - I must admit, I only noticed when updates.mydropwizard.com started emitting 522 errors, which led to repeated update failure emails on my end (and also a delay in loading the updates page).

I think just disabling myDropWizard is probably the way to go, but it looks like the variables mydropwizard_project_url (normally the HTTPS url updates.mydropwizard.com/files/update/v1 ) and possibly mydropwizard_statistics_url ( updates.mydropwizard.com/update/statistics/v1 ) could be changed if people want to set up their own compatible service using the module.

You should consider making this page your homepage so visitors don't think they can still sign up or send an email. I was pointed to this page after thinking you were still in business, and I would have not bothered you with an email if your public-facing traffic was just this page.

Thanks for the suggestion! This is now the case :-)