Last post 12 hours 18 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67837

All time tickets 10483

All time avg. posts per day 20

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.

#2594 – Wrong urls

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.

Tuesday, 09 August 2016 12:12 UTC

aceberlin

Hi,

we had last year some tickets because 'wrong' urls. The reason is the component k2 and the Multilanguage function. So we received wrong "en" urls from site there are only in German publishing. In the last year we don't found a solution for this problem. We try to delete the wrong urls and to give the "real" site the alias but does also not help.

After the update joomla to 2.6.2 we had the problem with the wrong language sign /en or /de on the end of the urls. You help us in our last ticket #2574 (this ticket is not more in our history here?!?) but we found the wrong urls every day new in our 404 requests.

Is it possible, for booth problems, to suppress the creation from this urls? For example our German blog is xxxx.de/blog - the English site is "news" with the url xxxx.de/en/news. So are all entries with xxxx.de/en/blog are wrong.

I know sh404SEF don't create the urls but I find this our in 404 also in google webmaster tools.

Or do you had a new idea for me and this problem?

Greetings
Norman

Tuesday, 09 August 2016 12:18 UTC

wb_weeblr

You help us in our last ticket #2574 (this ticket is not more in our history here?!?)

Ticket is still there, https://weeblr.com/helpdesk/sh404sef/2574-problem-with-the-url

So are all entries with xxxx.de/en/blog are wrong

Are there the URL manager still? if so, make a search for en/blog, then select the URLs found and delete them (with duplicates).

I know sh404SEF don't create the urls but I find this our in 404 also in google webmaster tools.

Search console can tell you on which page they found a 404. If it is an internal page, on your site, then you need to find it and fix it. Otherwise, having 404 listed doesn't mean it is a problem.

Rgds

Wednesday, 10 August 2016 14:53 UTC

aceberlin

Hi,

what do you mean with "URL manager" Do mean the joomla "System – Redirect" or SEF URLs in sh404SEF?
The Redirect system is empty (nothing in all categories incl. trash). in SEF URLs we found the wrong en/blog an delete then, but there come back.

It gives also sites like this: https://xxxx.de/augengesundheit-screening this url received from sh404SEF also a short url "r4"
This is totally wrong. This is not a joomla article that is a k2 article. That is not in "Uncategorised" this is in "weitere Leistungen" and to find here https://xxxx.de/weitere-leistungen/augengesundheit-und-screening .

This is the same problem like the en/blog - i can delete them but it comes back again :(

Wednesday, 10 August 2016 14:59 UTC

wb_weeblr

what do you mean with "URL manager"

Euh, the main page of sh404SEF, the URL manager.

in SEF URLs we found the wrong en/blog an delete then, but there come back.

Deleting a URL record in sh404SEF has no purpose. JOOMLA creates URL, not sh404SEF. URLS always come back because Joomla keeps creating them when it needs it to be displayed on a page. sh404SEF is only here to turn a non-sef URL (used by Joomla internally) into a SEF.

It gives also sites like this: https://xxxx.de/augengesundheit-screening this url received from sh404SEF also a short url "r4"

Why are you talking about SHURL? What does this has to do with the discussion?

This is not a joomla article that is a k2 article.

I have no idea what you are talking about. What does the fact it's a joomla article or K2 has to do with the SEF URLhttps://xxxx.de/augengesundheit-screening? Why do you talk about "uncategorized"?

By the way, and extremely important: Which version of K2 are you using exactly? If version 2.7 or higher, do you have the K2 URLs plugin, that K2 provides?

Rgds

Wednesday, 10 August 2016 17:04 UTC

aceberlin

Okay step-by-step
At first: I know Joomla generate urls – not sh404SEF – I wrote that before.

(1) in SEF URLs we found the wrong en/blog an delete then, but there come back.
So – my original question was: “Is it possible, for booth problems, to suppress the creation from this urls?” Yes, Joomla create them but why and where? In the frontend you can’t receive this urls – that is the reason for the 404. My question is how to fix it.

(2)It gives also sites like this: https://xxxx.de/augengesundheit-screening this url received from sh404SEF also a short url "r4"
>> Why are you talking about SHURL? What does this has to do with the discussion?

We talk about the SHURL because we have the same problem like the wrong urls like “en/blog” with this URLs like this demo url https://xxxx.de/augengesundheit-screening - this url don’t exist. And normally it give no SHURL in for the k2 component. Why we receive there?
This target from this content is https://xxxx.de/weitere-leistungen/augengesundheit-und-screening
If you follow the wrong URL https://xxxx.de/augengesundheit-screening you will see the main page with all details – also the show of the category

We use
- Joomla 2.6.2
- K2 v2.6.9
- sh404SEF 4.7.3.3292
- We don’t have a separate “K2 URLs plugin”

We make not the update to the newer v2.7.1 because we read the k2 forum it gives problems between the v2.7.1 and sh404SEF and the creation from new URLs. – Is that true?

Thursday, 11 August 2016 09:54 UTC

wb_weeblr

(1) in SEF URLs we found the wrong en/blog an delete then, but there come back.

So – my original question was: “Is it possible, for booth problems, to suppress the creation from this urls?” Yes, Joomla create them but why and where? In the frontend you can’t receive this urls – that is the reason for the 404. My question is how to fix it.

Surely but how and where this non-sef URL is created has nothing to do with sh404SEF, and all to do with your site. I have no idea

we have the same problem like the wrong urls like “en/blog” with this URLs

Are you talking about the SHURL or the SEF URL. What do the SHURL has to do with it. It's a totally separate thing, unrelated to the creation of SEF URL.

I have not understood what you said honestly. Here is what I see:

If I visit https://xxxx.de/augengesundheit-screening, I see this:
[xxxx]
If I visit https://xxxx.de/weitere-leistungen/augengesundheit-und-screening, I see:
[xxxx]

So those 2 pages show different content, and they are not related at all.

I can also see that requesting https://xxxx.de/r4 redirects to https://xxxx.de/augengesundheit-screening. What is wrong with that? are you saying that /r4 should redirect to /weitere-leistungen/augengesundheit-und-screening instead of https://xxxx.de/augengesundheit-screening?

We make not the update to the newer v2.7.1 because we read the k2 forum it gives problems between the v2.7.1 and sh404SEF and the creation from new URLs. – Is that true?

As usual on the internet, absolutely not true. From version 2.7, K2 have moved their sh404SEF plugin from the main download to a separate plugin. So you need to get it separately from the main K2 download. That's all. We do not provide support for K2, it's actually K2 that provides (and has provided for years) support for sh404SEF. This support was built-in the main download, they moved it out now. They are also the ones providing support for everything K2+sh404SEF related.

Rgds

Friday, 26 August 2016 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.