Search errors continue

[0bvious]

(sorry, I couldn't reply to this
http://groups.google.com/group/lifepress/browse_thread/thread/718e34b0ca381422
post for some reason)

Hello

I am getting a similar search error, and it only started happening
after I updated sweetcron to lifepress. Here's the error message when
I search for 'Noise':


A Database Error Occurred

Error Number: 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 'AGAINST('noise') AS score FROM (`items`) LEFT OUTER JOIN `feeds`
ON `feeds`.`fee' at line 1

SELECT *, MATCH(item_title, `item_content)` AGAINST('noise') AS score
FROM (`items`) LEFT OUTER JOIN `feeds` ON `feeds`.`feed_id` =
`items`.`item_feed_id` WHERE `item_status` = "publish" AND
MATCH(item_title, item_content) AGAINST('noise') ORDER BY `score` desc


Try it here: http://machinemachine.net/stream/items/search/noise

Any ideas how to stop this?

Thanks

[0bvious]

So I got a good reply to this over at the sweetcron google group. Any
ideas how to remedy:

http://groups.google.com/group/sweetcron/browse_thread/thread/34ed1f3df6876b5a

"Looking at the full SQL statement below, the problem seems to be that
there
are some extra rogue back-quotes in the MATCH argument which confusing
things. More specifically "item_content)" is being quote-wrapped but
because there is no ending parenthesis for the leading paren to the
MATCH
argument that is confusing the SQL engine.

I did a quick search through my Sweetcron source-code and found this
query
on +156 and +166 in system/application/modesl/item_model.php. You can
try
taking a look at that file to see if that is indeed where the extra
bad
quotes are coming from.

This isn't a problem on my Sweetcron install, so my guess is that it's
a bug
with the Lifepress code-base. I remember that Lifepress forked from
Sweetcron several months back, but I haven't followed what changes
they made
on top of Sweetcron."

Please solve...



On Sep 9, 11:13 am, 0bvious <therou...@gmail.com> wrote:
> (sorry, I couldn't reply to thishttp://groups.google.com/group/lifepress/browse_thread/thread/718e34b...

[0bvious]

ANYONE?

On Oct 6, 12:55 am, 0bvious <therou...@gmail.com> wrote:
> So I got a good reply to this over at the sweetcron google group. Any
> ideas how to remedy:
>

> http://groups.google.com/group/sweetcron/browse_thread/thread/34ed1f3...

[!!blue]

Has anyone found a fix?

[Skyler Kehren]

The link at the end of the original post seems to work without error.
It appears to me that Obvious has some to some solution.

Can you confirm this? If so, what did you do to fix it. If not, is
there any more information on situation you can provide.

[0bvious]

Sorry. My reply ended up here by mistake:
http://groups.google.com/group/lifepress/browse_thread/thread/861406f81f74e861#

Basically I 'downgraded' back to sweetcron and the problem was solved.
Lifepress is fundamentally broken and with no support it seems that
sweetcron is the best solution.

[!!blue]

Ah, well, thank you :)

On Nov 11, 2:10 am, 0bvious <therou...@gmail.com> wrote:
> Sorry. My reply ended up here by mistake:http://groups.google.com/group/lifepress/browse_thread/thread/861406f...