Req: User decides post direction
 

Users continue to request the ability to choose which direction the forum threads are displayed, forward or reverse.

No matter what direction I set it in the control panel, I end up only pleasing half the group. Could someone please create a hack to add this feature? Perhaps as an option in the user control panel?

Thanks!

Easiest way:

Create a new user profile field editable by user and ask your users to enter "1" if they want normal order and "0" if they want reverse. (If you want you can hack register.php and member.php to show this profile field as a "radio button" or "check box")

Then edit showthread.php, find:

Before that add:

Replace X with the id of your profile field

That's it.. :)

Thanks I'll give that a try, and let you know how it turns out.

I was wondering though, what if the user hasn't filled out the new field, and it's simply blank? Will showthread choke on the empty field?

No it will not.. It will be automatically either one even if the field is empty

.

Okay, good news, VB came to its senses and realized the extra column wasn't there.

Lets leave the database alone if we can. Any other suggestions?

If you want a user selectable option, how can u leave db alone? You have to save the user's selection somewhere in your database. You would consider adding a new field to user table if you didnt apply my solution and it would require much more hacking since you need to form a interface for your users to populate this field. Adding a new profile field just saves you from this trouble.

Bottom line is, you can not have such a hack without touching your db.

.

.

1- Creating a new user profile field is done inside Admin CP. I hope you first this method in the first place? It would be very unnecessary to use PhPmyadmin to add a new profile field.

If you created the field via Admin CP, I doubt it would give you this problem. It should not be server intensive to create a new user profile field even if your db is large.

2- Messing with db with PhpMyadmin is not recommended unless you know what you are doing. But if you are intended a new profile field has 2 traces in your db. Its name and options are recorded in "profilefield" table where one new column is also added to "userfield" table. Deleting its record from profilefield and deleting the column from userfield, should solve the problem IF IT IS RELATED to profile fields. (BACKUP DB!) But as I said before I doubt it, it might be another db problem you are having at the moment..