First of all, what's a slug?

The slug is the user friendly and URL valid name of published content. In UXi, the following types of content are used:

  1. Blog Post
  2. Page
  3. Media Attachment
  4. Location
  5. Testimonial

Most commonly, the slug refers to the user friendly name of a page or post.

 When a new post is published, a post slug is generated by UXi. The slug is made up of the following:

  • the name of the category the post is published in
  • the name of the post itself.

IE: /category-name/post-name/

 When a new page is published, a page slug is generated by UXi. The slug is made up of the following:

  • the name of the parent page, if there is one
  • the name of the page itself.

IE: /parent-page-name/page-name/

 However, the same process happens when images are uploaded to a new page or post. As a result, if an image and a page share the same slug, there will be conflicts with the URL.

IE: /page-name/attachment-name/

For this example, we'll use a site with the URL of If a page called 'Madwire' is created as a sub-page of another called 'Our Partners', it's slug would be /our-partners/madwire/ resulting in a full URL of

Below is an example of a page (on the left) and an image (on the right) that share a slug.


To resolve this URL conflict so that the page can be displayed using the /our-partners/madwire/ slug, the details of the image were updated using the Edit Media dashboard.  


Once the image's title and slug are updated to use Madwire logo, the page itself can be saved using the correct slug.

As mentioned above, UXi uses five different types of content. Pages, posts, and images are detailed above. Here is a list of default slugs used for locations and testimonials.

 When a new location is published, the slug is: /locations/location-name/

 When a new testimonial is published, The slug is: /testimonials/testimonial-name/

Because these slug settings for locations and testimonials cannot be changed, avoid creating pages that use URL's of /testimonials/ or /locations/. This will likely cause conflicts viewing the pages.