Big Upgrade 3.2.1 to 7

[pollingj]

I've been tasked with a substantial upgrade of Alchemy on some older sites (6 of them), and each site has 100's of pages each. The current sites are all running AlchemyCMS 3.2.1. I'm just looking for some advice on the best way to run through the upgrade.

The options I currently see are

1. Slow upgrade through each version 4.0, 4.1, 4.2 etc etc
2. Jump to 7.0 and fill in the gaps with manual migrations etc.

Just wondering if anyone had any advice on this please?

[tvdeyen]

Mostly follow these instructions:

1. Upgrade minor version and run

bundle exec rake alchemy:upgrade

2. Follow on screen instructions.

3. Repeat.

But: There are Ruby and Rails upgrades involved that needs to be coordinated in between major versions as well.

Luckily the company behind Alchemy (Blish) - also my company and main sponsor - is expert in maintaining Alchemy installations and offers upgrades as well as maintenance and hosting services for Alchemy users.

Please write me at thomas@blish.cloud or via private Slack message if you need any further information.

[pollingj]

I've started the process and it's started ok, along with some custom migrations I've needed.

One thing I've not spotted yet is how to cope with the limit of just one _view partial, in later versions of AlchemyCMS 4

Our code currently renders certain resources but with different layouts depending on the page_layout we are using e.g.

<%= render_element resource, :card%>

and then

<%= render_element resource, :full_screen%>

on another.

So we have view files like this:

• elements/_resource_card.html.erb
• elements/_resource_full_screen.html.erb

With the :part being removed from render_element, what's the strategy now for this?

[tvdeyen]

Since render_element is "just" a convenience layer around render partial you could easily replace it with something like

<%= render "alchemy/elements/resource_card", element: element %>