Humminbird after update PS to 9.1 is still 1.1 ?

[rzucpalenie]

Prerequisites

• I understand and accept the project's code of conduct.
• I have already searched in existing issues and found no previous report of this bug.

Describe the bug and add attachments

Should the template be updated to version 2 after updating to PS 9.1?
My Hummingbird after update is still 1.1 after update PS 9.0.3 to PS 9.1...
How to update it now ?

Steps to reproduce

My Hummingbird after update is still 1.1 after update PS 9.0.3 to PS 9.1...

Expected behavior

No response

Actual Result

No response

PrestaShop versions where the bug happens

9.1

Module version where the bug happens

9.1

PHP version(s) where the bug happened

8.4

Your company or customer's name goes here (if applicable).

Lukasz

[Quetzacoalt91]

I'll need @tblivet's knowledge on this one, but my guess is even though the files are copied, the version installed in the database keeps the old version because we don't call the Core to update the version number.

[tblivet]

Hi @Quetzacoalt91 and @rzucpalenie, when a theme is installed, a file is generated there, for example: config/themes/hummingbird/shop1.json. This file stores the originally installed version, such as "version": "1.1.0" in your case. The version number displayed in the BO is based on this file. Since it is not properly regenerated, the back office may display an incorrect version number even when the theme files have been updated.

[rzucpalenie]

So @Quetzacoalt91 how to check currently installed version in PS 9.1 ? in shop1.json after update to PS 9.1 still I have 1.1.0 just as you wrote...
Generally, many files inside the template folder have been updated when I update PS to 9.1 30.03.2026... screen atached...

[Quetzacoalt91]

You'll find the version of the updated theme in the file config/theme.yml.

[rzucpalenie]

@Quetzacoalt91 yep, its 2.0 there... thx...
What about shop1.json, leave it as it is or fix this file somehow?

[Quetzacoalt91]

We'll see what we can do during an update, the version of the enabled theme is expected to be updated as well.

[Hlavtox]

@Quetzacoalt91 @tblivet Watch out that this file contains all the layout settings for the theme, so avoid deleting it. It would be great if it was stored in a database instead.

[nicohery]

The file config/themes//shopX.json is used to store the installed theme version and page layout configuration, but it is not mentioned anywhere in the official documentation. The doc only covers theme.yml and settings_n.yml.
https://devdocs.prestashop-project.org/9/themes/getting-started/theme-yml/

This mechanism is hardly compatible with modern CI/CD workflows: the configuration is generated at install time and does not follow the versioned code, which forces developers to manually delete or regenerate this file after each update. In practice, the only fully reliable workflow remains uploading a ZIP archive, which feels quite outdated today.

It would be much more robust to store this information in the database or within the theme itself, and to properly document how it works. This would greatly improve reliability for deployments and automated updates.