• Home
  • Get help
  • Ask a question
Last post 14 min ago
Posts last week 89
Average response time last week 30 min
All time posts 67718
All time tickets 10464
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#5827 – Can't save modified SEF URLs due to SQL error.

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Sunday, 26 May 2019 23:10 UTC
kbrookes
 
Hi there,

I've got a new site running for a corporate client with a sysadmin I've never worked with before, and we seem to have some teething issues. I encountered the following issue whenever I attempt to modify an existing SEF URL in the sh404SEF component:

ERROR:

Could not save data. Error: 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 'ASC' at line 1


Steps to replicate (on their server):

Go to Components > sh404SEF > SEF URLs

Perform a search for 'general' in the search bar at the top of the URL list.

Click on the URL 'general/terms-conditions' - and change it to 'terms', then click save.

Error appears at that point.
Their sysadmin response is as follows:

On investigation we found that there is some issue with the component sh404sef. This happened as ‘rank’ is the column name in table sh404sef_urls. In MySQL ‘rank’ is used as function, as a result there is a conflict.


Given I've never encountered this in the dozens of dozens of sites I have running sh404SEF, I'm somewhat dubious of their claims.


Here's my system info:



Setting Value

PHP Built On Windows NT SV 10.0 build 17763 (Windows Server 2016) AMD64
Database Type mysql
Database Version 8.0.15
Database Collation utf8mb4_0900_ai_ci
Database Connection Collation utf8mb4_0900_ai_ci
PHP Version 7.3.3
Web Server Microsoft-IIS/10.0
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 3.9.6 Stable [ Amani ] 7-May-2019 15:00 GMT
Monday, 27 May 2019 06:43 UTC
wb_weeblr
Hi

This seems legit and likely due to running MYSQL 8. Nobody runs MYSQL 8 exactly for this kind of non-backward compatible issues! I'll look into it today and see what kind of changes is needed to workaround this.

Best regards
 
Monday, 27 May 2019 06:46 UTC
kbrookes
Awesome - I did point them at the Joomla Requirements before they setup the server... looks like they took the '+' of the '5.5.3 +' as a challenge!

Thanks for looking into it.
Monday, 27 May 2019 15:20 UTC
wb_weeblr
Hi there,

Sorry about the delay. Most of it was trying to get MYSQL 8 to run on my local system without breaking everything! I added some code to allow operating with MYSQL 8, seems good to me. Please download fixed version from the [development versions] and try again.

let me know

Best regards
 
Tuesday, 28 May 2019 00:00 UTC
kbrookes
Awesome!

That worked beautifully - thanks for that :)

What's the process with future updates of the plugin?

Regards,

Kelsey
Tuesday, 28 May 2019 07:25 UTC
wb_weeblr
Hi

If you mean how updates work on top of a dev version, it's all transparent. Your current dev versions will update normally to the next public release. There's not really anything like a public release, all published versions have a sequential number and they will all be updated normally at any time.

Best regards
 
Wednesday, 12 June 2019 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.