[a1-b]

The section is set to forced sorting by date. The user has the ability to lift up his theme.

The original query:

"UPDATE". TABLE_PREFIX. "Thread SET dateline = $ time WHERE threadid =". $ Message [2];

He should change the date to the current topic. But if you run it, reset the field lastpost for the theme that we raise.

Therefore, until the first request has to be considered lastpost value for the selected date, and then execute it push installation:

UPDATE ". TABLE_PREFIX." Thread SET lastpost = $ lastpost WHERE threadid = ". $ Message [2];

That is, the base initially behaves strangely.

What happens with an example. User created theme. In the same time it is listed as the date and time: 26.01.2012, 22:36, last post: 29/01/2012, 15:16.
The user raises the topic in the list so it becomes a creation date 01.02.2012, 20:56, last post: 01.02.2012, 23:56, but if you go to the very topic that first post of this topic will be a "native" date: 26.01 .2012, 22:36

In principle, this would be so happy with everything, but there is some kind of an annoying bug. After lifting the (updating) date of creation of threads, if users start to write in this topic, then at some point, set a new date for a topic in the 02/01/2012, 20:56 reset to the initial 26.01.2012, 22:36, and the theme again departs Down at the N-th page.

I tried to catch at what point and why the topic is reset - to no avail. Ran a variety of tasks crown by hand, suddenly some clean leads us changed manually in the field of rule - to no avail.

Can not update a field or not, and should be a bit different to do?