One thing that is inconsistent, and I'm damned if I know why it's been done, is the use of a new enclosing tag in add-ons and some other areas for templates.
It's hard to gauge exactly where the changes apply and where they don't but in the add-ons here's an example of a changed file:
This one is a mystery to me as well. Even if we set aside the actual reason for the change... the inconsistency of how it's applied is very odd indeed. (Couple that with the apparent lack of documentation... and users are (again) left on their own to make sense of it all.)
ISC 4.0.7
"... and let's be honest that whole "by design" thing is getting old too."
In terms of the discrepancies this appears to be a changeover thing with the add-ons starting the ball rolling, then the front end, followed by the administration side of things. That's not hard and fast intel btw, but makes sense..
The thing that bothers me, on looking over the Twig examples at the provided link, is that it seems a bit of a step backward towards mixing the programming into the markup. I hope they don't go too far in that direction. It was kind of nice to have all the logic separate from the templates themselves.
meules wrote:I think they going to use this for feature addons. Maybe like multiple languages??
Maybe, although they could have handled multiple languages from the outset if the specification had been written properly from the outset and not patched together as they went along.
Template/language fields have never been properly implemented with hard coded labels appearing all over the place so that would need to change before they could get proper language support added in.
Hi Martin, do you have any updates on this, or what files to modify in the template to edit, as there is no indication for us newbie isc messing around with the store code fools like me,
pitorian wrote:Hi Martin, do you have any updates on this, or what files to modify in the template to edit, as there is no indication for us newbie isc messing around with the store code fools like me,
From what I remember it was more the stuff in the backend (ie: admin modules, etc...) that had changes to their templates. I had to modify the templates for the Royal Mail module for example.
Front end (customer facing) didn't seem to get any changes... In reality all that changed was the way the templates were parsed (ie: tag changed for actual language values) so unless you are seeing templates with missing bits of text, you should be fine.