Pagebuilder 5.3.4 and Joomla 5.1.2 generates Error 1064 - Forum | JoomShaper
Solved SP Page Builder

Pagebuilder 5.3.4 and Joomla 5.1.2 generates Error 1064

Asked by Christina Vogl 2 years ago Last activity 2 years ago

Hey,

after System Migration to Joomla 5.1.2 and Pagebuilder 5.3.4 we get the following error:

1064: 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 '8) ORDER BY lft ASC' at line 3

Blank page! Can you Help?

Accepted answer

Marked as the solution
Rashida Rahman Staff

Hi Christina Vogl,

Please take my sincere apology for the unwanted delay.

I have tried to login but it says the credentials are not correct. Would you please check and share again?

Sorry again.

Best Regards

Christina Vogl Asked this

Now it must work!

Christina Vogl Asked this

Hallo. Any updates so far?

2 more replies

Rashida Rahman Staff

Hi there!

Sorry for your experiecne!

Would yoou please give me your admin access to check the issue for you? Kindly keep a full site backup before giving the access.

Best Regards

Christina Vogl Asked this

See infos attached.

Christina Vogl Asked this

Hellou, is there any solution avaiblable? :)

Rashida Rahman Staff

Hi there!

Apology again.

I can see you are using SPPB 3.8.10 version there still. Did you downgrade in the meantime? Do you have backup of your full site including the database?

Can I make some changes in your site freely? Such as updating SPPB there?

Moreover, where the error is visible that you mentioned at the first place?

Best Regards

Christina Vogl Asked this

Couldnt Update due to blank page, as already told at first entry:

after System Migration to Joomla 5.1.2 and Pagebuilder 5.3.4 we get the following error:

1064: 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 '8) ORDER BY lft ASC' at line 3

Blank page! Can you Help?

Christina Vogl Asked this

yes we did. your new update obviously fixed the problem. thx.

Log in to reply.