Activity log for bug #288919

Date Who What changed Old value New value Message
2008-10-24 21:56:30 saggers bug added bug
2008-10-25 00:33:43 bengtan prosepoint: status New Confirmed
2008-10-25 00:33:43 bengtan prosepoint: assignee bengtan
2008-10-25 00:33:43 bengtan prosepoint: statusexplanation
2008-10-25 08:34:34 bengtan prosepoint: importance Undecided High
2008-10-27 01:02:51 bengtan title installation completion error message ProsePoint does not support table prefixes
2008-10-27 01:40:36 bengtan prosepoint: status Confirmed Fix Released
2008-10-27 01:40:36 bengtan prosepoint: statusexplanation ProsePoint 0.06 has been released which fixes this bug. Thank you.
2008-12-01 00:23:39 bengtan prosepoint: status Fix Released In Progress
2008-12-01 00:23:39 bengtan prosepoint: statusexplanation ProsePoint 0.06 has been released which fixes this bug. Thank you. Hi Pierre, Thank you for pointing this out. Your diagnosis is correct. However, I think the following changes are better for pp.admin.inc: Line 80: $result = db_query("SELECT COUNT(*) FROM {node} node LEFT JOIN {content_type_story} content_type_story ON node.vid = content_type_story.vid WHERE node.type = 'story' AND content_type_story.field_extended_status_value = '%s'", $value); and Line 90: $result = db_query("SELECT COUNT(*) FROM {node} node WHERE node.type = 'story'"); because they are a bit easier to read. Yes, I will check other queries for this problem, and incorporate a fix into a future release of ProsePoint. Thank you.