I added t link rel="shortcut icon" href="http://www.buffistas.org/favicon.ico" type="image/x-icon" to the header which might make it show up in more places. Not in mine, Opera nor IE5.
Buffy ,'Chosen'
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.
It doesn't for me, but it won't because I'm a holdover at NS4.77 so no icons work for me. It doesn't on my IE 5, either, but it does on my Mozilla.
Oh -- I fixed the thread adding problem. Amazing what a couple apostrophes can do.
Ooh. You're the best.
I have a very serious complaint about this board and it's architects. It has made the rest of the internet unsuitable. I grow impatient as the other bloated sites load. I scoff at their poor design and unintuitive navigation. I mock the lack of depth in their content.
It's a big problem. Your efficiency is making their normalcy unacceptable.
Thanks.
Oh -- I fixed the thread adding problem. Amazing what a couple apostrophes can do.
What was the problem? Did it have anything to do with Victor being in the middle of the process?
Nah -- it was a coding memfault (needed to put quotes around the new fields 'closed' and 'archived') -- which reminds me,
DX, when you come through -- have you sucked and zipped?
needed to put quotes around the new fields 'closed' and 'archived'
Cool. What exactly do those checkboxes do?
When closed is checked (and it's automatically checked when the postnum passes 10,000), that's when the word [closed] appears by the thread name (you'll notice it's no longer IN the thread name), and posting is severely discouraged. Well, the posting box disappears.
When archived is checked, the thread won't display on the main page at all. My thought it then, when it's been zipped and sucked to mark the thread archived and delete all the posts (but not the thread title). All auto urls to it would then be redirected by showthread to the zip listing page, to the appropriate target. That part's not coded yet.
That sounds good. Do we have any way to store the database version of the archived threads offsite somewhere? Would there be any irreparable disadvantages if we didn't?
Problem with that is that you need to take the user information with you. Which gets all tangled and complex.
As for not saving the records -- I think that should be fine.
As a first stab, we could just move them to another table -- that should help.