It appears that there is code that inspects the thread and determines the months in use in that thread. This code limits the months available in the month box. In some threads, the available months are 6, 7, 8... others, it's the full 1 through 12.
Example, this thread only has months 2 and 3 because the thread began in February and ends in March Topic!Cindy "Natter 33 1/3" Feb 22, 2005 12:45:04 pm PST
I'm suggesting that we do away with this code and always present months 1-12 Jan-Dec and days 1-31 as options.
Except the code was working up until October 1, so why not try to fix what may be a simple problem rather than scrapping it and going to a much less elegant solution?
I'm advocating scrapping because the code in place doesn't do what it attempts. It's trying to limit entered dates to ones within the thread's timeframe. The way it's structured, it's still possible to enter dates outside of the timeframe (in some cases).
Secondly, I don't see the value of doing a couple of extra queries on every page view, especially when that control is used relatively infrequently (granted, assumption), for little gain.
Listing all of the months and all of the days is quite straightforward and it doesn't appear that things will go poof if invalid dates are supplied by the user.
There are no extra queries on the page view, but thanks for looking out, Eddie.
I'll try debugging the code before I throw it out. I apologise to anyone who's had their browsing broken by this, but I'm unlikely to get to it before this coming Sunday.
Suggestion for the Request Queue:
Sometimes in this thread and Buffistechnology, it would be helpful to upload a text file with code (for example) rather than try to format the code so that B.org parses it correctly. There could be a hyperlink next to Mark and Block... possibly View or File? that would display the attached text (unformatted) in another browser window when clicked.
We'd probably want to limit the uploaded file size to maybe 50k. I imagine there are bandwidth and file space and security considerations.
Thoughts?
Or you could upload the file to yousendit.com, and then include the link in the post.
There are some very good reasons for the posting restrictions we have, mostly based on past abuse noted at other boards. The last thing anyone needs to see is photos of Charlie Daniels showing up in every thread.
Would an option to disable html and quick-edit parsing within a post be simpler?
Or you could upload the file to yousendit.com, and then include the link in the post.
That works; it hadn't occured to me.
The last thing anyone needs to see is photos of Charlie Daniels showing up in every thread.
Oh dear. I'd forgotten all about that.
Pictures in-thread are different (visual impact-wise) from peoplesforum-style attachments, but I can see it quickly spiraling out of control. A cat on every post!
