Slug collision warning on custom hierarchical pages

  • Resolved tinytim84

    (@tinytim84)


    8 years ago

    Hi there,

    I’m getting the slug collision warning on a custom post type that is a hierarchical page. It’s slug is events, but it’s much deeper down in the url structure of the site. e.g. https://localhost:8060/insights/hr-services/events/. The Events Calendar is at https://localhost:8060/events/, so I have no issues with the site. Your plugin calendar appears at https://localhost:8060/events and my HR Services events page appears fine at it’s url, but I still get the warning. Is there a reason for this, and is this a bug in the plugin? This isn’t really an issue as everything is working as I’d expect, but it is confusing for the authors as they think they’ve done something wrong.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Barry

    (@barryhughes-1)

    Hi @tinytim84,

    That’s a great observation.

    The key thing here though is that the post slug in question is still events, which is what The Events Calendar is picking up on here. It’s position in the post hierarchy allows for the sort of URL you provided in your example, but there remains some potential for collisions to take place (happily, though, they seem rare in practice).

    Hey there! This thread has been inactive for a while so we’re going to go ahead and mark it Resolved. Please feel free to open a new thread if any other questions come up and we’d be happy to help. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Slug collision warning on custom hierarchical pages’ is closed to new replies.