Error while searching

[ncsuapex]

I was trying to search the terms "folder stream"

and got this error.


General Error
SQL ERROR [ postgres ]

ERROR: invalid reference to FROM-clause entry for table "m0" HINT: There is an entry for table "m0", but it cannot be referenced from this part of the query. []

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.

Please notify the board administrator or webmaster: admin@videolan.org

[siikah]

Same here. A single one-word search worked, but then it all stopped working.

[Arite]

Intriguing. Any string containing >1 words returns a PostgreSQL error. This occurs with Advanced search too.

Possibly a regression caused by the phpBB 3.0.3 update. I can confirm it is not Style-related since prosilver returns the same error (not that it would be but decided to check just in case).

EDIT: Moved to Forum, Website and Artwork discussion forum.

Arite.

[eaglepep]

I too receive the following when trying to do a three word search "add files playlist" in the Windows forum:

General Error
SQL ERROR [ postgres ]

ERROR: invalid reference to FROM-clause entry for table "m0" HINT: There is an entry for table "m0", but it cannot be referenced from this part of the query. []

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.

[quality]

Same here. A single one-word search worked, but then it all stopped working.

Exactly the same here.

[Arite]

This appears to be the same bug in phpBB:
http://www.phpbb.com/bugs/phpbb3/ticket ... t_id=19195

However it was fixed apparently a while ago, so (as I said before) there may have been a regression since 3.0.2.

There are a few other new similar tickets such as this:
http://www.phpbb.com/bugs/phpbb3/37005

Unless j-b recognises it as just a PostgreSQL database issue probably safe to assume it is a bug in 3.0.3.

Arite.

[Jean-Baptiste Kempf]

Unless j-b recognises it as just a PostgreSQL database issue probably safe to assume it is a bug in 3.0.3.

Agreed.