The current page is shown because the Blocklayout Template Engine failed to render the page, however this could be due to a problem not in BL itself but in the template. BL has raised or has left uncaught the following exception:

Database Query Error

Description: ErrorNo: 1064, Message:Database error while executing: 'SELECT xar_articles.xar_aid, xar_articles.xar_title, xar_articles.xar_summary, xar_articles.xar_authorid, xar_articles.xar_pubdate, xar_articles.xar_pubtypeid, xar_articles.xar_notes, xar_articles.xar_status, xar_articles.xar_body FROM xar_articles WHERE xar_articles.xar_aid IN () ORDER BY xar_articles.xar_pubdate DESC, xar_articles.xar_aid DESC'; error description is: '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 ') ORDER BY xar_articles.xar_pubdate DESC, xar_articles.xar_aid DESC' at line 1'.

Explanation: A database query could not be executed, either because the query could not be understood or because it returned unexpected results.

Product: App - Modules

Component: Articles


The following exception is instead the exception caught from the main catch clause (Please note that they could be the same if they were raised inside BL or inside the template):

Error Message
Exception Icon

System Error

Database Query Error

ErrorNo: 1064, Message:Database error while executing: 'SELECT xar_articles.xar_aid, xar_articles.xar_title, xar_articles.xar_summary, xar_articles.xar_authorid, xar_articles.xar_pubdate, xar_articles.xar_pubtypeid, xar_articles.xar_notes, xar_articles.xar_status, xar_articles.xar_body FROM xar_articles WHERE xar_articles.xar_aid IN () ORDER BY xar_articles.xar_pubdate DESC, xar_articles.xar_aid DESC'; error description is: '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 ') ORDER BY xar_articles.xar_pubdate DESC, xar_articles.xar_aid DESC' at line 1'.

Explanation:

A database query could not be executed, either because the query could not be understood or because it returned unexpected results.

Click here to raise a bug