Edit theI'd rather edit the template than install an add-on as I've already made some modifications and marked them with comments.
register_macros
like so:Thanks Andry. Quite pricey for such a simple thing, but looks like it can't be done without an add-on.
It can be achieved very simply with a template edit.
A paid add-on is not required.
I am not in my office now so can't give you the details but I will tomorrow, unless someone else does so before then.
Thanks Andry. Quite pricey for such a simple thing, but looks like it can't be done without an add-on.
Agreed... but how many template edits carry over to the next cleanly? One really has to remember what each specific one is for.Add-ons are cool but template edit is cool too for those who wants to learn, and because if every time you want to do a simple template edit, you install a third party add-on and you quickly end up with dozens and dozens for not much.
Much cleaner if there was an ability to document any changes made. It can already track that the template has been modified.... why should one have to dig though the entire template to find a comment (which is not highlighted to begin with).You can use<xf:comment>...</xf:comment>
tags.
Problem with doing that is if you comment out something that another developer is looking for in the template and replaces it with something, what they are trying to do won’t work.You can use<xf:comment>...</xf:comment>
tags.
But it is MUCH easier if I pull up that template to refer to a "notes" field for any modifications that I have detailed. Those will be specific to MY modifications, and not any others.... not to mention carrying forward even if those modifications get "accidentally" overwritten in a merge process.Either you can use<xf:comment>
tags (easily found with a simple CTRL + f in the template) or use<!--
-->
which are very easily identifiable in the code:
Yes it's true but it's not done, it seems to me, to uncomment code but rather to add information on what we do in the code.Problem with doing that is if you comment out something that another developer is looking for in the template and replacers it with something, what they are trying to do won’t work.
<!-- -->
tags, hence the interest of add-ons and the system for modifying templates. But I persist in saying that installing an add-on for a single line template modification is a bit "too much", a solution would be to be able to create template modifications directly in the ACP without going through the creation of an add-on.Note I say a stupidity because it is possible by activating the development mode...a solution would be to be able to create template modifications directly in the ACP without going through the creation of an add-on.
That existed (or similar) at one point in the 1.x line. For some reason it was removed in the 2.x line. Or it may have been an add-on that allowed it... that's been a decade (± a couple of years) ago though, so I've had a lot more pressing matters come forth.solution would be to be able to create template modifications directly in the ACP without going through the creation of an add-on.
But I persist in saying that installing an add-on for a single line template modification is a bit "too much", a solution would be to be able to create template modifications directly in the ACP
Yes, you're right, I'm going around in circles, my remark was not relevant.That is exactly what the addon does, adds a template modification without any work from the user
Edit theI'd rather edit the template than install an add-on as I've already made some modifications and marked them with comments.
register_macros
like so:We use essential cookies to make this site work, and optional cookies to enhance your experience.