isn't it possible to just delete the entire posts (number #823-#8xx) instead of only their contents? or does the db-code not allow it? 

okay, i just banned my first IP on func.

If i delete the posts entirely, that would probably screw up the code that assumes the posts are sequential and stuff... i'm not sure exactly, but when i first wrote the DB i decided i didn't want to delete posts.

Now, what i will likely do is censor the posts so that you can't see them. The moderator tools to do that don't exist yet, though. 

 

There was a SQL error. 

i've intentionally made the error messages obscure to prevent people from using them to attempt to hack the board. I should probably set up something to log the more descriptive error so that I can see what's happening, but it wasn't something that I thought happened very often or consistently. 

That was the first time I had seen that in a long time. It was also the first time a board error ate one of my posts. 

test 

another test 

another test! 

last test? 

please? 

But why does it go backwards in increments of 50 and forwards in 5? Is this some crazy UI Zen you have thought up, meltshine? 

 

I seem to have gotten thread paging working in its most basic form. By default, links to a thread will show the first 25 posts (instead of all posts.) You can still see all posts by editing the "start" and "end" variables in the URL. If you post to a thread regardless of what page you are viewing, it will bump you forward to show the most recent 25 posts, with your post at the bottom.

- Number of posts per page will eventually be a user preference.
- I might eventually add "first 25" and "last 25" links as well.
- I'm not sure if this thread navigation needs to go both at the top and bottom of the post list or just one place, or what.
- I might need to change the wording of the links on the forum page. 

When there are less than 25 next or previous posts, it displays the number of actual next or previous posts. So there were only 5 next posts in that case.

The 50 was because I was playing around. 25 will be the default for now, while I work on getting a user preference for it. 

Very good addition metl, first/last would be a nice addition yeah.
And maybe add a little black line above the links, to separate them from the last post. =) 

I'd prefer to keep the same "load entire thread" vs "last 25" as now and use the paging only for the latter. At least I'd like a separate link to get the entire thread.

Most threads are either relatively short ones (no problem loading entire thread) or very long ones (very few would probably want to page through it all from the beginning). 

I'd like to see the Next/Previous 25 links at the bottom, seperated by a black dividing line like Bal said. 

just modify the link at the top where it says "start" and "end", go to the end of the thread, then set "start" to 0, and that will load the whole thread. 

I'm undecided on whether to have a link to load the entire thread or to force people to edit the URL. One of my goals was to remove "load entire thread" as a default or easy choice, becuase I think it's a bigger DB hit. But I'll think about it. 

I know how to do it, but as this is probably one of my most frequent forum activities, it'd be very cumbersome to have to edit many links I click.

Btw, the current "All xx" links (which is what I want) don't seem to work; they still give the paged beginning of each thread. I hope it's because metl is working on it ;) 

maybe it's ^^^ his fault the forums have been slow then! hehehehee... 

Yeah, ever since you've added this paging thing, the forums have become really fast for me... 

Exactly the same here... Maybe you corrected a small bug indirectly... Anyway: it's cool how it works fine now ! 

tell me agian why using generic php-bb-nuke-thingy-code that every other web forum uses is a bad idea and coding Func from scratch makes the forum so much better? It's not that I actually believe a word of it, it's just that it's a rainy afternoon and I could do with a laugh.