When moving an older post to a newer posts thread, it will become the leading / original post (depending on date) of that thread.
eg moving post from 04/05/2007 10:13:41 p.m. (dd/mm/..)
to a thread, where lets say the original post was created 06/05/2007 02:53:12 a.m.
will result in the thread displaying moved_post->original_post

Been playing around, but sadly I'm new to php and drupal in general.
Attempted using
$query = db_query("SELECT TIMEDIFF((SELECT Posted FROM {F_Posts} WHERE PostID='$PostID'), (SELECT LastPost FROM {F_Threads} WHERE ThreadID='$ThreadID'))");
which would result in something along the lines of -47:00:57
eventually followed by
if (strpos($OlderPost, '-') != '0') {

But uieforum_update_last_post_details keeps buggering me over.

Hope the dev isn't lost to the great void.

CommentFileSizeAuthor
#2 B becomes A.jpg114.39 KBQui.dormit.non.peccet

Comments

daniel.hunt’s picture

daniel.hunt commented
Assigned: Unassigned » daniel.hunt

I'm not sure I see the problem here - if you move a post into another thread, it will take its place in the chronological line of posts just as every other post does.

No post in this system is flagged as the "first" post in a thread - they're just chronologically ordered.
Is that a problem for you?

Daniel

Qui.dormit.non.peccet’s picture

Qui.dormit.non.peccet commented
StatusFileSize
new B becomes A.jpg114.39 KB

hmm, let me redescribe the problem:

1) There are two posts post A, posted yesterday at 1pm; and post B, posted today at 3pm
2) You select to move post A to post B
3) After the move, post A is above post B, as the original post

The issue:
Post A was moved to post B's thread, but took it over by becoming the original post
(Posts in order would be A, B, or #1, #2) (See attachment)

I just believe this isn't how it's intended to operate. If you move post A shouldn't it just be 'tacked on' to the end of post B?..
I just believe this would be an issue as the title of the thread no longer reflects the first post that will be displayed

Chronological order makes sense in some cases, however for moving surely you should assign it a new PostID to have it tacked on at the end?

Qui.dormit.non.peccet’s picture

Qui.dormit.non.peccet commented

Oh, forgot to mention, when moving post, also get this error message..:
user warning: Incorrect datetime value: '' for column 'LastPost' at row 1 query: UPDATE F_Threads SET LastPost='', LastPoster='0' WHERE ThreadID='3' in F:\Apache\htdocs\includes\database.mysql.inc on line 172.

daniel.hunt’s picture

daniel.hunt commented

Yeah I see your point now.

Interesting discussion really - I'm in favour of the "chronological order, no matter what" approach. Whereas you're obviously in favour of the "er, but that's not the first post" approach :)

As for the db error - I'll look at it later on tongiht - thanks.
Daniel

daniel.hunt’s picture

daniel.hunt commented
Status: Active » Closed (fixed)