I'm not sure if that's how Elena's husband got the last post in N8.
Beats me. I just had Charpe check, and there's no posting box. Maybe he really does have a deal with Cthulhu.
Wait. People? She eats people? 'To Serve Man.' It's 'To Serve Man' all over again.
Gunn ,'Power Play'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
DXMachina - Feb 22, 2003 6:44:57 pm PST #3163 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
Jon B. - Feb 22, 2003 6:59:33 pm PST #3164 of 10000
A turkey in every toilet -- only in America!
Jon, I'm thinking the simplest place to put an error message a la "Whoops too late" is in the space where the posting box would go, if someone tries it.
Testing my understanding: Someone posts to a closed thread (because they've had the page open since before it closed). When they hit "Post message" you want the showthread page to appear as it does now, but with an error message somewhere on the page indicating why the user's post ain't there?
I think it should be higher up on the page than the posting box. I think the error message would be more visible if it were nearer to the top of the page.
§ ita § - Feb 22, 2003 7:08:02 pm PST #3165 of 10000
Well not canonically, no, but this is transformative fiction.
I was trying not to mess with the unchanging parts of the design. Everything from the thread title down to just above the last HR is generated together. So the variations, according to current coding principles have to happen outside that.
Jon B. - Feb 22, 2003 7:18:14 pm PST #3166 of 10000
A turkey in every toilet -- only in America!
I see. How about just above the last HR then? i.e. right after the
"Read New | Message center | ..."
Also, how hard would it be to make the post a page variable that displays with the error message? I'd hate to spend a lot of time posting a message only to find that it errored out and is lost in the ether.
§ ita § - Feb 22, 2003 7:22:16 pm PST #3167 of 10000
Well not canonically, no, but this is transformative fiction.
Also, how hard would it be to make the post a page variable that displays with the error message? I'd hate to spend a lot of time posting a message only to find that it errored out and is lost in the ether.
If we're doing that, I'd think that below the HR is the place to go, wouldn't you? Perhaps even put it back in the posting box, with an error message above and no buttons?
Jon B. - Feb 22, 2003 7:32:47 pm PST #3168 of 10000
A turkey in every toilet -- only in America!
If we're doing that, I'd think that below the HR is the place to go, wouldn't you? Perhaps even put it back in the posting box, with an error message above and no buttons?
Aesthetically, this makes total sense. My concern is that the error message won't be seen until and unless the user scrolls all the way to the bottom.
How about a NAME tag in front of the error (e.g. t a name="error" t /a ) and have the reloaded page URL include an #error at the end so that the page automagically displays the error section?
§ ita § - Feb 22, 2003 7:33:18 pm PST #3169 of 10000
Well not canonically, no, but this is transformative fiction.
Sounds like a plan.
Jon B. - Feb 22, 2003 7:34:58 pm PST #3170 of 10000
A turkey in every toilet -- only in America!
How do you want to work it? You want me to code up a dummy page without the PHP? Or do you already have some PHP-coded page that I can work with to fancify the error message?
§ ita § - Feb 22, 2003 7:36:27 pm PST #3171 of 10000
Well not canonically, no, but this is transformative fiction.
I haven't finished the logicking yet, so a mockup is best.
Jon B. - Feb 22, 2003 7:39:20 pm PST #3172 of 10000
A turkey in every toilet -- only in America!
Okeley dokeley. I should have some time tomorrow. I may even have time to work on that admin "search-for-user-email" upgrade. :)