• Home
  • Get help
  • Ask a question
Last post 2 hours 33 min ago
Posts last week 141
Average response time last week 4 hours 42 min
All time posts 67805
All time tickets 10478
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.

#4592 – Impossible to redirect to a SEF URL

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.
Thursday, 01 February 2018 11:22 UTC
ghribi
 Hi,
since the last update to joomla 3.8.4, I can not redirect 404 page to a SEF URL.
i get the error:
Alias %s already exists as an alias, or as a SEF url. It was not stored into the aliases database


I purge the safe URLs and clear cache but the problem is still there.
My site
https://www.xxxx.com
LOGIN:xxxx
PASSW:xxxx

Regards
Thursday, 01 February 2018 11:54 UTC
wb_weeblr
Hi

1 - I have tested this with latest sh404SEF and Joomla 3.8.4 on another site and could not find any issue.
2 - The message is correct, sort of, because the alias actually already exists. But there is a problem with the leading /

What's happening here is that the display of the 404 is incorrect. This URL request had a double slash (//en/shared-shuttle-orly-disney.html) when it was requested and older versions of sh404SEF did not record the initial slash in 404s. This is now fixed and the 404s but the alias already in place was for the old way of recording.

Long story short: after deleting the existing alias
[xxxx]
and trying again, it works fine this time.

Rgds
 
Thursday, 01 February 2018 12:07 UTC
ghribi
Thanks a lot for your help

Regards
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.