requesting:
Both would require a separate admin post page, since the name input is disabled, and since it might be a good idea to make it optional to include XHTML code. I'll put it on the list.
>Both would require a separate admin post page, since the name input is disabled,
you could enable it with javascript, sort of like how the [del] links work when user deletion of posts is disabled...
>>2
You can enable the Name field even in forced anon mode, but ignore that's typed into it unless the name matches an admin tripcode. Same thing as you're doing with the Link field and sage.
Sure, but the disabled field is a nice visual hint of what's happening.
Also, you can't click in the Name field in pseud0ch with FORCED_ANONYMOUS
>>5
There's the visual hint that says "Anonymous posting is being enforced" next to the Reply button. If you shift it down one row to put it directly under the text field for Name, it'll be more visible (and not wrap into an ugly, mostly-empty line between Name/Link/Reply and the textarea in my overworked 800x600 browser windows).
That's not a good hint. I have this thing for proper user interface design. But, there are better ways to handle this. I'll just have to figure out which one is easiest most elegant.
If ease of implementation isn't a consideration, I like >>3's suggestion. It's consistent with how the Manage link works in other situations.
In addition to (or instead of) checking for admin trips or such in the Name field, you'd check for the proper management password in some hidden POST variable.
There ought to be some way for an admin to indicate whether they want their posts to be interpreted as unmodified XHTML, as well.