Two small but notable bugfixes for the forums:
1. No more silly negative number SQL errors. (thanks Matt_Burch!)
2. No more scalar value used in array errors for polls.
Just here for the activity... well not really
Thanks, now I can finally use the "Recent Post" link instead of going into the forum and THEN clicking the last page >__<
guy lifting weight (animated smiley):
O-IC
OI-C
"Oh, I see it"
I love you very much Moose, may I cuddle you?
None.
PyMS and ProTRG developer
The first problem doesn't give the error anymore, but its screwy. In a thread with one reply i clicked the "Recent Posts" thing and it only showed the last post and it wasn't on a page (pages list showed [<][1][>] and [1] was still clickable). I clicked the page 1 link and it showed both posts. Hard to explain, you probably don't get what I said, just try it yourself.
Yeah, pages that normally would have died have lost proper page numbers.
In my mind, it's a lot better than not viewing the page.
*Applause From Studio Audience*
None.
PyMS and ProTRG developer
When trying to "View Recent Posts" on a thread with no replies, i get:
Warning: Invalid argument supplied for foreach() in /home/starlite/public_html/scripts/forums/topic.php on line 413
and it shows no posts.
IP/Moose forgot to do if ($var) { foreach ($var as ...) { ... } }
None.
When I click on a topic I've never read, but has replies, the first post does not show up and the next post says it is post #-19.
I guess making a note to moderators would be a good idea? So when they click a topic they haven't read, and it shows the second post first; They don't just delete it because it doesn't make any sense..?
None.