Some addons use TMS to do the edits where there's no hooks.
As I understood it, that's effectively what the new core functionality is.
Some addons use TMS to do the edits where there's no hooks.
I guess for his "add-on like" template edits, which are nothing else but style edits.What are you using the TMS for?
I guess for his "add-on like" template edits, which are nothing else but style edits.
Some addons use TMS to do the edits where there's no hooks.
You are calling template edits, style edits now? That's fine with me but that's what TMC does as well as TMS.
Forreal???I had thought the big issue was that TMS allows for per style edits while the new TMC does not?![]()
The only difference DRE is we won't be able to export them as template edits for say premium styles. Using TMC that is that I understand
I had thought the big issue was that TMS allows for per style edits while the new TMC does not?![]()
I had thought the big issue was that TMS allows for per style edits while the new TMC does not?![]()
I wouldn't lie to you.Forreal???
He suggests us make the changes to the templates directly, which is cool and all, problem is when you have to revert changes due to either a Xenforo or addon/style upgrade. So what I learned from this is when I get TMC, I'll apply the TMS changes to TMC on my parent style and for individual style edits, I'll use that for TMS. I only have one template that needs to be edited directly into a child style so that means my TMS will only be used for that one template edit in that one style and the TMS changes from other resource author's addons.if you're not an add-on developer, but unless you have multiple styles, I'd recommend just making the changes to the templates directly.
Okay so I went back to Mike's thread and saw this:
He suggests us make the changes to the templates directly, which is cool and all, problem is when you have to revert changes due to either a Xenforo or addon/style upgrade. So what I learned from this is when I get TMC, I'll apply the TMS changes to TMC on my parent style and for individual style edits, I'll use that for TMS. I only have one template that needs to be edited directly into a child style so that means my TMS will only be used for that one template edit in that one style and the TMS changes from other resource author's addons.
Okay so I went back to Mike's thread and saw this:
He suggests us make the changes to the templates directly, which is cool and all, problem is when you have to revert changes due to either a Xenforo or addon/style upgrade. So what I learned from this is when I get TMC, I'll apply the TMS changes to TMC on my parent style and for individual style edits, I'll use that for TMS. I only have one template that needs to be edited directly into a child style so that means my TMS will only be used for that one template edit in that one style and the TMS changes from other resource author's addons.
Oh wow I forgot about that. I really missed that coming from vBulletin 4.The new template history and merging will make this less of an issue.
Nah just gather our pitchforks and demand Mike stares at the code until he implements individual style editing with exporting.
that would make XF real special if this was implemented. Style updating made easier than it already is? I think we would need to change the term "updating style".![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.