hookActionCheckoutRender cannot be used anymore to manage (add / remove) checkout steps

[bibips]

The hook actionCheckoutRender cannot be used to add a new checkout step. This is a regression from the classic theme because this following code is not enough anymore to add a step :

    public function hookActionCheckoutRender($hookParams)
    {
        $checkoutTestStep = new CheckoutTestStep();
        $checkoutProcess = $hookParams['checkoutProcess'];

        $steps = $checkoutProcess->getSteps();

        $checkoutTestStep->setCheckoutProcess($checkoutProcess);

        $newSteps = [
            $steps[0],
            $checkoutTestStep,
            $steps[1],
            $steps[2],
            $steps[3],
        ];

        $checkoutProcess->setSteps($newSteps);
    }

Regarding the hummingbird theme, when we changed the checkout steps, the navigation menu was not updated, meaning customers could not access the additional steps.

The problem is that the default steps are hardcoded in checkout-navigation.tpl , rather than being based on the steps in CheckoutProcess class.

[mcaldex]

hi @tblivet @ga-devfront , do you happen to know if this is getting fixed in the short term?
Given that Hummingbird 2.0 is going to be the default theme for prestashop 9.1, this becomes a even bigger trouble which we should aim to fix, in my opinion.

I could try to dive into it myself soon if you're still unsure on the timing.

Thanks

[Hlavtox]

Ping @tblivet @ga-devfront

[ga-devfront]

After several attempts on our part, it appears that no fix is ​​possible without overriding the PHP code in the theme. We have taken note of the problem and are planning a joint fix for Hummingbird V3, which should be released at the same time as PrestaShop V10 (in order to implement the necessary breaking changes).

[kpodemski]

Hello @ga-devfront

Could you elaborate? It's a big regression. Why would it require changes in the PHP file if that works in Classic?

[ga-devfront]

Hello,

To clarify my previous message: the situation initially seemed blocked due to an architectural difference between how the Classic theme and Hummingbird handle checkout steps, combined with how PrestaShop core passes this data to the templates.

In the Classic theme, there is no global "progress bar" or navigation menu at the top of the checkout page. The steps are simply stacked as an accordion. PrestaShop core loops over the steps in checkout-process.tpl and triggers the rendering of each step individually. Because the step renders itself, it naturally has full access to its own inner variables, such as its $title.

Hummingbird, however, introduces a completely new UI component: a global navigation bar ( checkout-navigation.tpl ) that sits above and outside the actual step rendering. This means the template needs to know all the steps in advance to build the desktop list and the mobile progress indicators.

The technical challenge we faced was twofold:

1. By default, PrestaShop only passes the $steps variable downward to checkout-process.tpl.

2. Even if we access the $steps array from the outside to build the navigation menu, PrestaShop secures each step behind a RenderableProxy. This proxy exposes the step's identifier (e.g., checkout-addresses-step), but completely hides its internal properties, meaning the $title is inaccessible.

Because the title was inaccessible to the navigation bar, we initially thought it would require breaking changes to the core classes, which is why I mentioned waiting for PS v10 / HB v3.

The plan for the fix: However, after further investigation, we realized we can fix this properly without any BC break. Instead of using hacky workarounds in the theme, we are plotting a much cleaner solution:

1. In PrestaShop Core (target v9.2): We will submit a PR to explicitly expose the $title field alongside the identifier in the step array returned by the CheckoutProcess. Since adding a new key to an existing array is backward compatible, it does not have to wait for a major version.

2. In Hummingbird (target v2.1): We will update the checkout-navigation.tpl templates to implement a dynamic {foreach} loop over the $steps array, utilizing this newly exposed $title property.

This will properly resolve the regression and guarantee that any checkout step injected by a third-party module is accurately represented in the Hummingbird navigation bar. Thank you for pointing this out and pushing us to look for a robust solution!

[tblivet]

@ga-devfront Thanks for your answer, there’s nothing more to add 👍
We’ll try to add this to our internal roadmap soon so we can allocate time to fix it and be ready for the releases of PrestaShop v9.2 and Hummingbird v2.1

[kpodemski]

@ga-devfront @tblivet

If I understand correctly, there's nothing that prevents us from fixing it in 9.1.1?

[ga-devfront]

Yes of course, however I thought we were closer to a 9.2.0 than a 9.1.1.