You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a module contains files in the default tpl_modified folder, they are added during the installation but do not seem to be updated on newer releases.
MMLC: Version 1.23.0
Steps to reproduce:
Create a module with files in /new_files/templates/tpl_modified/**
Publish the module. The template files will be copied to your active template (i. e. tpl_modified_responsive)
When you release a module update, the files in the active template do not seem to be updated
That's correct. The problem is that many users adapt the template files to their design after installation. If an update is carried out, the MMLC would overwrite these adjustments. To be on the safe side, template files are not updated. You would have to come up with something for the MMLC if you wanted to automate this as well.
The problem is that many users adapt the template files to their design after installation.
Even additional template files coming from a module?
This also affects PHP-Files in /CURRENT_TEMPLATE/source/boxes, which is breaking at least one of my modules after each update if I make changes there.
I understand that modified users change their template files but I doubt it also applies to template files from modules.
It's natural that an update overwrites existing files, even modified itself is overwriting core and template files after an update. I believe it to be default and expected behaviour. Maybe the MMLC can do the same?
Alternately, maybe a flag in the config could be a workaround to tell the MMLC to overwrite all files during a module update.
Activity
RobinTheHood commentedon Nov 6, 2024
That's correct. The problem is that many users adapt the template files to their design after installation. If an update is carried out, the MMLC would overwrite these adjustments. To be on the safe side, template files are not updated. You would have to come up with something for the MMLC if you wanted to automate this as well.
grandeljay commentedon Nov 6, 2024
Even additional template files coming from a module?
This also affects PHP-Files in
/CURRENT_TEMPLATE/source/boxes, which is breaking at least one of my modules after each update if I make changes there.I understand that modified users change their template files but I doubt it also applies to template files from modules.
It's natural that an update overwrites existing files, even modified itself is overwriting core and template files after an update. I believe it to be default and expected behaviour. Maybe the MMLC can do the same?
Alternately, maybe a flag in the config could be a workaround to tell the MMLC to overwrite all files during a module update.