Splitting a topic fail

[GoogleCodeExporter]

What is the expected output? What do you see instead?

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. | File: 
/geeklog-1.8.0/public_html/forum/moderation.php | SQL in question: UPDATE 
gl_forum_forums SET topic_count=topic_count+1, post_count=post_count+1 WHERE 
forum_id= 

The post we try to split is remove but is not display (forum=0 and subject=0)

Also number of replies is wrong for the original topic.

Original issue reported on code.google.com by hostelle...@gmail.com on 4 Dec 2012 at 9:25

• Merged into: #47

[GoogleCodeExporter]

Original comment by hostelle...@gmail.com on 4 Dec 2012 at 9:27

• Added labels: Forum

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'll handle this one.

Original comment by hostelle...@gmail.com on 8 Dec 2012 at 9:01

• Changed state: Accepted

[GoogleCodeExporter]

Solution : $_REQUEST['movetoforum'] and $_REQUEST['movetitle'] are not numeric 
so we do not need to set the second parameter of the COM_applyFilter function 
to true

$movetoforum      = isset($_REQUEST['movetoforum'])   ? 
COM_applyFilter($_REQUEST['movetoforum'])        : '';
$movetitle        = isset($_REQUEST['movetitle'])     ? 
COM_applyFilter($_REQUEST['movetitle'])          : '';

Original comment by hostelle...@gmail.com on 8 Dec 2012 at 9:04

• Changed state: Started

[GoogleCodeExporter]

Duplicate of Issue #47 - Confirmed fixed.

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

• Changed state: Duplicate

[GoogleCodeExporter]

Based on the information provided in this post, I was able to find the location 
of the code that needed to be changed: in site/forum/moderation.php, around 
line 66. And now the problem is gone. Which leads me to ask: if an issue has 
been marked as 'fixed', does that mean that the problem has been fixed in a 
public release of Geeklog, or simply that one of the developers found a fix and 
may or may not have provided said fix in the issue tracker?

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

[GoogleCodeExporter]

The issue was reported after the forum 2.8 release and the fix is now in the 
repository. So this fix will be fully available in the next public forum 
release. We hope this will in the next few days :)

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