04.12.01

Template protection  -  @ 07:50:10 576
I would think that any essential PHP code in templates should be 'filtered' out by b2 in template editor, except the usual author/e-mail/comment tags. This saves a lot of potential damage to an edited file. When saving the template, b2 checks if the necessary code has been put in place; if not, it does just that but only if one or more author/e-mail/comment tags have been put in the file (to prevent any disasters from occuring should one be just editing a casual file).

Otherwise, it would also be wise to follow the Blogger way. b2 can process the filename (which is put as a preference) and accordingly format the tags. I think this is very much slower and harder to fix than the first one suggested.
3 comments

 

:: comments

 

michel v - email - url
I've been scratching my head on this one. What do you mean ? Could you give me an example, explain just one or two test cases ?
05.12.01 @ 15:15:41 885

 

ian - email - url
okay michel, you know those php tags? it could be potentially dangerous to a page if the php tags are not 'protected' and hidden off by the template editor.
07.12.01 @ 11:17:27 720

 

michel v - email - url
oh, I see what you mean. let's see if I can do that, it shouldn't be hard, just a matter of search&replace job
07.12.01 @ 14:29:56 854

 

:: leave a comment

 

name

email

url

your comment

Auto-BR (line-breaks become <br> tags)

 

:: return to the blog

[powered by b2.]

4 sp@mbots e-mail me