Davidls wrote: A temporary solution for DELETE is to do a blank FIND/REPLACE WITH
I agree that it's the best solution waiting for a real DELETE action but it needs to be officially authorised
A part from that I agree with Ptirhiik.
The template needs to be boost one good time to add useful and logical needs, and there is many important ones.
Just one example: being able to add instructions to modify the DB is a good thing, but the new SQL action seems a bit too restrictive.
Most of MOD authors now use php files to update the phpBB DB and there is many good reasons for that (as fixing table prefix potential issues).
The phpBB group itself uses php files to proceed updates so why can't we do the same in our MODs how-to ?
I think sometimes you focus your attention on details which are not necessarily the most important. A few days ago I read an amazing discussion about how to write "MOD" in "MOD Author".
The debate was what is accepted: "mod", "Mod" or "MOD"
#1 EM can use a php function to be sure to read the good string in any case (lower each letter for example) - so that's not a problem
#2 For the MODs DB, I think that's a bit too much to refuse a MOD only because its written "Mod" and not "MOD" ; and it's easy to create a small software that can switch any case in writing the header entries to the good one - so that's not a problem too
#3 And the most important: why obliging to write "MOD..." ?
All entries on the header are about the MOD of the how-to! Why behind "Author" should we need to add "MOD" and not behind "Installation Level" for example?
We loose our time talking about this kind of details.
Simplify guys, and focus on the real needs to go ahead quicker than other competitors!