Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Low Search Problem - Error Number: 1064
Status | Resolved |
Add-on / Version | Publisher 1.6.2 |
Severity | |
EE Version | 2.9.2 |
Gavin Lawrie
Apr 01, 2015I am migrating a site to using Publisher.
The site uses Low Search.
I have installed the Publisher / Low Search extension.
When I generate a search result in English, and then change the page to show a different language I get this MySQL error
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 'AND is_draft = 0 ORDER BY row_order ASC LIMIT 600' at line 4
SELECT row_id, col_id_3, col_id_4, col_id_5 FROM exp_matrix_data WHERE field_id = 8 AND publisher_status = "open" AND publisher_lang_id = 2 AND entry_id = AND is_draft = 0 ORDER BY row_order ASC LIMIT 600
Filename: third_party/publisher/models/publisher_query.php
Line Number: 107
The Low Search configuration currently does not use any collections, and so it seems you cannot force an index rebuild in conventional fashion (https://getsatisfaction.com/low/topics/you_are_not_authorized_to_perform_this_action).
Any ideas?
Brian Litzinger
Gavin, what does your full template code look like? It seems you are rendering a Matrix field in Low Search results list?
Gavin Lawrie
The page that is throwing the error is a simple search results page that lists whatever results are obtained from low search. The site itself has channels that use matrix fields, so by implication some results may well be items that are from matrix fields via low search - but that’s not a template thing directly.
Unhelpfully (from the diagnosis perspective) the error is not happening today - so I’m guessing that somewhere between then and now Low Search rebuilt its index and so the error does not now occur. But given that the error was being triggered in a Publisher module, there might be some kind of modification you can make to the query that would prevent it happening in future.
I’ll close this, but if you need any additional information about the site configuration feel free to use access details provided with original posting to have a look around - the site is a development machine.
Thanks as ever for looking / helping.
BoldMinded (Brian)
If you need to re-open it, please attach your template code so I can use the exact same code locally to try to replicate.
Gavin Lawrie
Here it is just for the record: