Search options (Page 1 of 2)

There is an option  under forum options in admin for  "Sort Topics By".  The default is Last Post, but you can change it to Topic Start

yeah, http://www.campidiot.com  is another one which has removed the copyright.

winmerge is a pretty good one

update posts set topic_id=<your_car_topic_id> where id=<post_to_move_post_id>

Edit: you'll also want to edit the last_post,posted,last_poster columns on the topic record to match the post and increaset the num_replies by 1

http://punbb.informer.com/forums/viewtopic.php?id=7347

modereatepoll is used for the links on the viewpoll page for "delete multiple posts", "move topic", "close topic", "stick topic" which are only visible to the admin / moderator, so you don't need to do anything during the install with it, just copy it to the root.  There is an admin page plugin which lets you choose the maximum number of poll answers you can have.  it is just one file plugins folder.

I did this on 1.2.15, but it appears that it works with anything after 1.2.3

are you sure you don't have more than 1 topics table (for example if you are using a prefix it would be prefixtopics table not topics?  There's not much else that message would mean.

Don't give up, though.  It took me 6 or 7 tries to get that mod to work, and finally did.

There's one at punres.  Why not continue to use that?

lang/<yourlang>/common.php

(for example if you use english it is lang/English/common.php)

look for the 'No View' entry and change the text value.

What sort of shocks and amazes me is that there has not been any response from the informer people.  Not that we would believe them, but I would have expected by now that one of the new developers would have posted a "do not fear, nothing will change or here's our new plan " sort of message to try to encourage the community to not switch.    So why wouldn't we?

You'll want to use one of the domains for master login, and make use of the shared db table.

for example, if example.com is your master login, when a user goes to example2.com:

1) if their  example2.com cookie is set, all done
2) if not, check your shared table to see if your token/timestamp from example.com has been written within the last x amount of time you want login valid for (30 minutes, 10 minutes, or later you can make this rolling time if you want).  if so write the example2.com cookie, all set.
3) if not, redirect to example.com auth page.   If the example.com cookie is already set, write a token/timestamp in your shared table. redirect back to example2.com, and it will be handled by step 2.
4) if example.com cookie is not set, show the login page.  if valid login, set example.com cookie and token/timestamp in your db and redirect back to example2.com and it will be handled by step2.

If they log in to example.com, all you have to do is set the example.com cookie and token/timestamp.

This way nothing is sent in the querystring that can be spoofed, so you are taking advantage of the security of the cookie and validating against the db instead.  you'll only need to pass the redirection page, which you were probably doing to a login page anyway, and eventually both cookies get set if needed.

Edit: I used example.com and example1.com interchangeably.

Any reason you can't cast the column in the order by clause?

order by cast(size_decimal as decimal)

so you'd have:

$result = $db->query('SELECT id, size_inches, size_decimal, normal_lbs, 144inch_lbs FROM '.$db->prefix.'sizes WHERE alloy_id='.$id.' ORDER BY cast(size_decimal as decimal) ASC') or error('Unable to fetch size information', __FILE__, __LINE__, $db->error());