Aha.
No.
I'll try to remember to port the fix (hell, and finish the fix) this weekend. Programming neurons are missing.
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Aha.
No.
I'll try to remember to port the fix (hell, and finish the fix) this weekend. Programming neurons are missing.
Jon--for the functionality to automate voting, what do we need?
Poll:
Question:
Option:
Does that cover it? And the basic assumption being that the poll is open between start and end (or from now until end if no start is specified). People get one vote (have people needed to change their answers?) per question, and poll results are only visible to the poll owner (& admins?) before the end date and time, and visible to everyone after that.
Am I missing anything much?
That looks pretty exhaustive. Maybe to the poll table, add a link to the post at which the lightbulbs discussion starts?
Who is the "poll owner"? Were you thinking the person who made the proposal? If so, I don't think they should have access to the results before the end date. They don't have access to that information now. Maybe simply make it an admin thing and leave out the creator altogether?
I don't know if people have had to change their votes in the past, but I think it's a good idea to work that functionality into the code.
Admin only poll creation? Yeah, that could work. And adding the link.
As for vote changing--as long as you only get the one vote per question, I don't see the harm.
Yeah, I think in the few instances where someone needed to, they emailed the vote counter in the past. So it's good to have the capability.
Jon, you should be able to close threads now. Holler if you still can't.
It seems to be working. Thx.
I've (hopefully) closed two of the bugs now--fixed the thread creation, and fixed it so that you can assign a folder on thread creation.
Well, they're fixed on .org. Now I have to port those fixes to css.net.
Jon, where were we with the changes to the CSS site? I'm not at my email and I don't remember if there was something I was supposed to be doing.
I kinda want to switch over.
Sorry, ita. I saw your post on Monday, but was running out the door and then forgot about it.
If I recall correctly, the only problem I had with the CSS formatting was that if-there-is-a-very-long-string-of-unbroken-text-it- makes-the-columns-overlap-with-each-other-in-some-browsers. Since there are other issues with really long unbroken lines (like horizontal scroll bars) that usually cause the poster or a stompy to fix the offending text anyway, I would say that we can go forward without fixing it.
Ideally, it would be nice to have the separate 2-column CSS separate from the 3-column CSS, but I don't think it's necessary.
t on edit But of course now I can't seem to replicate the problem... Grrr....