SQL Syntax Error When Deleting Items in Latest SP Page Builder Update - Forum | JoomShaper
Awaiting an answer SP Page Builder

SQL Syntax Error When Deleting Items in Latest SP Page Builder Update

Asked by Marius 1 year ago Last activity 1 year ago

Dear SP Page Builder Support Team,

I recently updated to the latest version of SP Page Builder in Joomla, and I am encountering an issue when attempting to delete elements. The following error message appears:

You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'AS collection_item WHERE collection_item.id IN (4)' at line 2
This suggests a possible syntax issue in the SQL query. I am currently using:

Joomla version: Joomla! 5.2.3 Stabl]
SP Page Builder version: 5.5.0
MariaDB version: 10.6.18-MariaDBa
PHP version: 8.2.27
Could you please provide guidance on resolving this error?

Thank you for your assistance.

Best regards,

3 replies

Oldest first Newest first Most helpful
Asfakur Rahman Saikat Staff
1 year ago

Hi Marius,

Thank you for reaching out, and sorry for the inconvenience.

Could you please specify which element deletions caused this issue? It would also be helpful if you could provide a screenshot for reference.

Additionally, the username and password you provided are not working—perhaps they haven't been activated yet?

I look forward to your response.

Best regards

Marius Asked this
1 year ago

Could you please specify which element deletions caused this issue? It would also be helpful if you could provide a screenshot for reference.

Apologies, I wasn't clear enough. I am referring to the Dynamic Content elements. I created a collection, and within that collection, I added several items. When I try to delete these items completely, I receive the error shown in the screenshot.

https://moveos.ro/images/Screenshot%203.png

Additionally, the username and password you provided are not working—perhaps they haven't been activated yet?

Apologies, the user was not activated. It should be working now.

Asfakur Rahman Saikat Staff
1 year ago

Sorry for the inconvenience.

The issue is occurring with MariaDB and has been reported to the development team.

Hopefully you will get a solution soon.
Thanks for understanding.

Log in to reply.