Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • AvihayBit 149 posts 303 karma points
    Apr 06, 2017 @ 20:42
    AvihayBit
    0

    This document is published but its url would collide with content (error)

    Hi,

    I get this error written near Link to document: "This document is published but its url would collide with content (error)"

    I just installed it on Umbraco version 7.5.12 and added

    <add key="virtualnode" value="lessonsBase"/>
    

    to the web.config...

    Did I missed anything?

  • Sotiris Filippidis 286 posts 1501 karma points
    Apr 06, 2017 @ 21:12
    Sotiris Filippidis
    0

    No, I don't think you missed anything. Can you check if, when hiding the URL segment for this document type, you end up having two nodes with the same URL?

  • AvihayBit 149 posts 303 karma points
    Apr 06, 2017 @ 21:19
    AvihayBit
    0

    Nope, It happens to all of this Document Type descendants...

    It did effects the links to this descendants but all pages gives 404 and the error I mentioned...

  • Sotiris Filippidis 286 posts 1501 karma points
    Apr 06, 2017 @ 21:25
    Sotiris Filippidis
    0

    That's strange.

    Have you tried to:

    1. Touch web.config to reload the application
    2. Republish entire site to recreate the cache
    3. Publish all descendants?
  • AvihayBit 149 posts 303 karma points
    Apr 06, 2017 @ 21:28
    AvihayBit
    0

    Yes, already tried that :(

  • Sotiris Filippidis 286 posts 1501 karma points
    Apr 06, 2017 @ 21:33
    Sotiris Filippidis
    0

    I'm curious now. The only case I've seen such an error is when there is a URL collision (duplicate URLs). If you've checked and you are sure that there isn't any such issue, then maybe it's something new that I'm not aware of. What happens if you remove the setting from your web.config? Do URLs behave normally?

    Also, is there any chance that the 301 url tracker is causing the issue? Any strange redirects there?

  • AvihayBit 149 posts 303 karma points
    Apr 07, 2017 @ 06:01
    AvihayBit
    0

    URLs behaves normally when removing the settings from the web.config, 301 url tracker isnt installed...

    But!! I think I found the reason: when I changes all the url to english it works fine, my website pages have Hebrew names and it seems that it cause some error when VirtualNodes plays with the URL when part of it is Hebrew with character...

    Any Idea for a simple solution? utf-8 update? :)

  • Sotiris Filippidis 286 posts 1501 karma points
    Apr 07, 2017 @ 06:26
    Sotiris Filippidis
    0

    Oh my. Truth is I never tested it with non-English characters. It's time to try it with Greek then :)

    I suspect the problem lies in the fact that the request to the server gets percentage-encoded when using Unicode characters. It will need some testing.

    BTW, I usually convert non-English characters to English since I'm not very convinced that non-English characters are good for SEO.

  • AvihayBit 149 posts 303 karma points
    Apr 07, 2017 @ 06:52
    AvihayBit
    0

    Oh, Great! I will follow for an update, thanks!

    About the SEO - it depends on the characters the users use, if they search for a Greek phrase, It make sense that it would be good to have it in the URL...

  • AvihayBit 149 posts 303 karma points
    May 04, 2017 @ 20:45
    AvihayBit
    0

    Hi Sotiris, any updates about this feature? The Greek nation is looking forward :)

  • Vitaliy 2 posts 71 karma points
    May 24, 2017 @ 07:18
  • Alessandro 11 posts 84 karma points
    May 26, 2017 @ 08:48
    Alessandro
    0

    I think it's related with this: http://issues.umbraco.org/issue/U4-9430

  • Jeroen Breuer 4908 posts 12265 karma points MVP 5x admin c-trib
    Jun 02, 2017 @ 08:37
    Jeroen Breuer
    0

    If you're getting the "url would collide with content" error you could try the Url Preview package: https://our.umbraco.org/projects/backoffice-extensions/url-preview/

    It will show the URLs instead of the error.

    Jeroen

  • Sotiris Filippidis 286 posts 1501 karma points
    Jun 02, 2017 @ 08:54
    Sotiris Filippidis
    0

    I apologize for not being able to answer things here during the last few weeks, due to a very demanding workload. This is ongoing, so I'm afraid I won't be able to check things for a few weeks more. I promise to debug (and adapt everything to 7.6 if needed) as soon as workload lessens a bit.

  • AvihayBit 149 posts 303 karma points
    Jun 04, 2017 @ 15:02
    AvihayBit
    0

    Awesome, we'll hold patiently for it :) thanks!

  • Michal Koblasa 45 posts 139 karma points
    Jun 08, 2017 @ 12:40
    Michal Koblasa
    0

    I will add, i found this error even before i installed DotSee.VirtualNodes. Before package i have implemented simple UrlProvider. So error "This document is published but its url would collide with content (error)" will not be connected with plugin but it may be a core error (im not completely sure).

    public class CustomUrlProvider : IUrlProvider
        {
            public string GetUrl(UmbracoContext umbracoContext, int id, Uri current, UrlProviderMode mode)
            {
                var content = umbracoContext.ContentCache.GetById(id);
                if (content != null)
                {
                    return "/" + content.UrlName + "/";
                }
    
                return null;
            }
    
            public IEnumerable<string> GetOtherUrls(UmbracoContext umbracoContext, int id, Uri current)
            {
                return Enumerable.Empty<string>();
            }
        }
    

    When i istalled plugin, error disappeared.

  • Logan P. 47 posts 217 karma points
    Jul 05, 2017 @ 18:53
    Logan P.
    0

    I'd like to add that if you do not have a Content Finder implemented for your UrlProvider, you will get the duplicate url error (which is the wrong behavior I think?). This comes from Umbraco trying to route the request to see if it is a duplicate url.

  • AvihayBit 149 posts 303 karma points
    Jul 05, 2017 @ 21:12
    AvihayBit
    0

    Well, I do not see how what both of you wrote have to do with the problem I described. I did not use any UrlProvider, only VirtualNodes and only when I use non-English characters as name of the nodes I get the error....

    @Sotiris - any update that solves this is planned soon?

  • Alessandro 11 posts 84 karma points
    Jul 06, 2017 @ 08:05
    Alessandro
    2

    They talk about UrlProvider because VirtualNodes has its own custom implementation behind the scene in order to allow proper url resolution.

    As I said I think only Umbraco HQ can fix it because it's a core little bug. http://issues.umbraco.org/issue/U4-9430

  • AvihayBit 149 posts 303 karma points
    Jul 06, 2017 @ 08:11
    AvihayBit
    0

    Oh, now that makes sense. Thanks Alessandro.

    Update here if it would be fixed please...

  • Ali 5 posts 74 karma points
    Sep 25, 2017 @ 00:35
    Ali
    0

    did anyone find a solution to this? I am on v7.6.6 and i am getting this error when there is a french character in the url. Once i remove it, the page works.

  • Hiren Oza 15 posts 87 karma points
    Nov 17, 2017 @ 10:37
    Hiren Oza
    0

    Hello,

    I'm getting same message(This document is published but its url would collide with content (error)) for Link to Document in Content for all nodes.

    I don't have any non-English character in URL. I just upgraded Umbraco from 7.4.0 to 7.6.0 and getting this error.

    Any idea/suggestion?

  • Jeroen Breuer 4908 posts 12265 karma points MVP 5x admin c-trib
    Nov 21, 2017 @ 10:49
  • Denford 132 posts 323 karma points
    Jan 08, 2018 @ 11:36
    Denford
    0

    Ok sorry guys i am still confused with this, so exactly what is causing this :) i have a new site running v7.7.4 and i don't have any other languages except the default english-us , all nodes under my home node are fine, its the others under my settings and from that document and all its descendants they all have this error.

    I have installed @jeroen URL preview, and there definitely is nothing funky on the URL, pretty standard i think, see attached images. At least in my case these are not actually view-able pages and are just info/setting providers.

    enter image description here enter image description here

  • Denford 132 posts 323 karma points
    Jan 08, 2018 @ 12:05
    Denford
    0

    Ok so apparently to get around my problem, i had to add a non existing host name to "site-general-settings" ? confused.com , have always done my settings this way think as latest as v7.5.3 i think (that the last site i done where it worked) and didn't have any problems before.

    apparently just been informed by a trusted friend that both "home" and "site-general-settings" now both are internally "/" even though the other doesn't have a host name attached and showing its link as "/site-general-settings/"? Sure someone from the core team can confirm that and still got no clue why this changed and what was the reason for the change.

  • Petr Svoboda 17 posts 68 karma points
    Jan 09, 2018 @ 13:37
    Petr Svoboda
    0

    I have the same problem.

  • Alex Skrypnyk 6163 posts 24143 karma points MVP 8x admin c-trib
    May 30, 2018 @ 10:44
    Alex Skrypnyk
    0

    Set useDomainPrefixes to true in umbracoSettings.config helped me:

    <useDomainPrefixes>true</useDomainPrefixes>
    
  • David Amri 214 posts 740 karma points
    Jan 22, 2019 @ 07:50
    David Amri
    0

    Hi Alex,

    I've got issues with the multi site setup and was wondering if you did anything else in order to make it work. Do you use the virtual node package? I've changed the domain prefix to true:

    <useDomainPrefixes>true</useDomainPrefixes>
    

    But I'm still getting collide errors. All the pages that are children of a virtual node gets the collide errors, the rest is working. Any ideas?

    Best regards /David

  • Dan White 206 posts 510 karma points c-trib
    Jul 01, 2019 @ 20:58
  • Malka Genzer 12 posts 84 karma points
    Feb 11, 2021 @ 08:17
    Malka Genzer
    0

    I know it's on old issue, but we still have this problem with hebrew characters on the V8 version. If there is any fix/solution/update ,we'll be glad to hear :-)

  • Hasan Habib 8 posts 88 karma points
    Mar 09, 2023 @ 04:59
    Hasan Habib
    0

    Still have the same issues with Umbraco version 7.15.7 assembly: 1.0.7706.20570

Please Sign in or register to post replies

Write your reply to:

Draft