Last post by Spuds -
Not the editor colors. Those will simply be rendered as,, for example,<span style="color: darkred;" class="bbc_color">test</span> So simply a named color CSS value that the browser needs to know.
Now the user can use hexcodes, or RGB values, etc in the BBC color tag,, but the editor is set to only use named colors (at least as far as I know, meaning that is all I've ever tried)
I vaguely remember back and forth over whether this was a good idea or not to actually do it. It may not have entirely worked properly.
Interesting. I can see how that may or may not work as expected. Its seems it already difficult for users to understand some of the nuances of what is new. One could reset a thread to a old pointer when a post it edited or maybe a notices for a watched topic that something changed.
Last post by Spuds -
Those are defined in the GenericControls.template.php in your theme directory (or the default theme directory if you do not have a custom one). In that file (line 80 for me) you will see
Last post by Mrs. Chaos -
Me again. I would like to add a new color to the color picker when selecting the font color for a new post, and want to change two old colors slightly. Where can I do this (theme BeSocial)? I can't find the right pages again. Only here I could find a line with the names of the current colors (line 81):
One problem is that when you edit a post, its not marked as new again (and would be rather impossible anyway), so anyone who has read the post will never have any indication that someone changed it.
SMF did actually do this. In the messages table was an id_msg_modified which would be used to track if the message had been edited by replacing it with the current maxMsg value and this could be used for read detection though I vaguely remember back and forth over whether this was a good idea or not to actually do it. It may not have entirely worked properly.
Last post by Steeley -
Roger that... well, then, how about just an either/or permissions option for user-editing-own-post to select an edit time-out, or edit-until-replied-to?
Although I still think if, in selecting the latter case, changing the edit time out to a "reply-block" time-out (to give the poster some "oops" correction time on an active dynamic site) shouldn't be too dysphoric (although as I think about it, "Preview" would serve that purpose if it didn't discard attachments to use it, I suppose. )
In any event, once a post has been replied to, further editing of it should be prevented, and if it hasn't been replied to, editing could be allowed - maybe if edited after the reply-block time out expires stuff an "updated" flag on it for a week or say..if it's then replied to, which flags the thread as having a "new" post and the "updated" flag can go away)? :-b
After all - current logic shows when it was last edited by the user..
(Although as I think about it more, it's entirely possible this is a proposed solution in search of a theoretical problem..)
Edit: For some reason smileys don't work for me now.. :-[
In addition to the time limit setting a user is allowed to modify their own post, an alternative option would be to allow the user to modify until that post has been replied to.
One problem is that when you edit a post, its not marked as new again (and would be rather impossible anyway), so anyone who has read the post will never have any indication that someone changed it. You could key off the replied to, but there are far more lurkers than posters. You could possible allow edit until its shown as read by someone or the edit to modify has passed.
The other options, well if they are difficult to explain to a user, imagine the difficulty in trying to implement something with too many conditions, it just becomes overly complex. Just look at the conditions I posted in what you need to remove an attachment, and that function is somewhat straight forward