Moving Topic Produces Error

[GoogleCodeExporter]

I tried moving a topic that contain one post from a public forum to a private 
forum and I got the following error and lost the post to boot :-)

09/21/11 16:27:27 - 1064: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '' at line 1. SQL in question: UPDATE gl_forum_forums SET 
topic_count=topic_count+1, post_count=post_count+1 WHERE forum_id=

It looks like the forum id got lost somewhere along the way...

Original issue reported on code.google.com by TomHo...@gmail.com on 21 Sep 2011 at 8:31

[GoogleCodeExporter]

Original comment by TomHo...@gmail.com on 27 Feb 2012 at 10:47

• Changed state: Fixed

[GoogleCodeExporter]

Issue 54 has been merged into this issue.

Original comment by TomHo...@gmail.com on 24 Mar 2012 at 10:23

[GoogleCodeExporter]

Issue 68 has been merged into this issue.

Original comment by TomHo...@gmail.com on 21 Mar 2013 at 10:53

[GoogleCodeExporter]

Still having this problem with Forum 2.8.0. What was the fix?

Original comment by mdemi...@gmail.com on 5 Apr 2013 at 1:42

[GoogleCodeExporter]

I'm also still seeing this problem. I had no idea it had been flagged as 
'fixed'. I am also running Forum 2.8.0, and I'm running Geeklog 1.8.2sr1. Any 
idea what's going on here? Anyone?

When I try to move a post to a different topic, I see this:
----
An error has occurred:

(This text is only displayed to users in the group 'Root')

256 - An SQL error has occurred. Please see error.log for details. @ 
/home/jrivett/geeklog-private/system/databases/mysql.class.php line 260

array(3) {
  ["sql"]=>
  string(93) "UPDATE gl_forum_forums SET topic_count=topic_count+1, post_count=post_count+1 WHERE forum_id="
  ["ignore_errors"]=>
  int(0)
  ["result"]=>
  bool(false)
}

Original comment by zulu4...@gmail.com on 5 Apr 2013 at 2:05

[GoogleCodeExporter]

Hi,
It is fixed in the next release (2.9.0)
See the solution on this page 
http://code.google.com/p/geeklog/issues/detail?id=68

Original comment by hostelle...@gmail.com on 5 Apr 2013 at 2:18

[GoogleCodeExporter]

Oh, crud. I just posted in that issue, asking whether the fix is in a public 
Geeklog release. Thanks for the tip. The solution provided in issue 68 worked 
for me.

Original comment by zulu4...@gmail.com on 5 Apr 2013 at 2:37

[GoogleCodeExporter]

Issue 68 has been merged into this issue.

Original comment by hostelle...@gmail.com on 5 Apr 2013 at 4:28