← All posts

How to Update Winden 1.x to 2.0 Without Losing Your Config

winden

Updating Winden from version 1.x to 2.0 can look worrying: the plugin deactivates itself, and after you turn it back on, your Tailwind config and CSS look like they are back to the defaults. Nothing is lost. Winden 2.0 stores its data in a new place, and a small migration plugin moves your old settings there in one click. This video shows the whole Winden 2.0 migration from start to finish.

Check your configuration before updating

Before you update, look at what you have now so you can tell later that everything came back. Open Winden in the WordPress admin, go to the Settings tab, and check the Tailwind Config tab (your custom screens, colors and spacing) and the Base CSS tab.

Update the plugin

Go to Plugins and click update on Winden as usual. After you refresh the page, you will see that Winden is deactivated, with a notice like this:

The plugin winden/wakaloka-winden.php has been deactivated due to an error: Plugin file does not exist.

This is expected. We made a lot of code changes in 2.0, and the main PHP file now has a different name, so WordPress no longer recognises the old file. Click Activate to turn Winden back on.

Why your config looks reset

When you open Winden again, the styles and the config are back to the defaults. Your data is still in the database. Version 2.0 uses a new data structure and looks for it in a different location. The Winden description on the Plugins screen now says: "If you are upgrading from version 1.X.X please » Download Migration Plugin « to help you transfer old data."

Click that link. It opens the Migration to 2.0 page in the docs. Under After upgrade steps, click Download migration plugin.

We did not build this code into Winden, because only users upgrading from version 1 need it. If you are starting with a fresh install of 2.0, you can skip this step.

Install and run the migration plugin

  1. Go to Plugins → Add New Plugin, upload the downloaded zip, then click Install and Activate.
  2. A new Winden Migration menu item appears in the admin sidebar. Open it.
  3. On the Winden Migration Settings screen, click Migrate Data. As the screen explains, this moves your CSS, configuration data and license key from the old options to the new ones.
  4. Go back to Winden. Your Tailwind config and Base CSS are back as they were.

Remove the migration plugin

The migration plugin, listed as Winden Migration from v1.x.x to v2.x.x, only has to run once. When your data is back, deactivate it and delete it. That's all you need to start using Winden 2.0. The Migration to 2.0 docs page explains why we moved to the new structure and lists the requirements. PHP 8.1+ is shown there.

Get Winden → dplugins.com

Related posts