Please document reserved slugs

HI @prestonwordsworth,

Thank you for contacting us.

Each page has a unique slug that cannot be used by another page. This is how wordpress use reserved terms https://codex.www.ads-software.com/Reserved_Terms –

https://docs.gravitykit.com/article/659-reserved-urls

This is how Elementor interact with slugs – https://elementor.com/blog/slug/

I found additional resources that might be helpful to understdn the issue – https://wordpress.stackexchange.com/questions/142542/slug-taken-cant-find-which-page

Let us know if you need additional assistance with Elementor plugin.

kind regards

Dear @marthaeli

Thank you for this. The specific slugs I mentioned – /uncategorized/ (on sites that don’t use categories) and /embed/ (for any page’s oEmbed iframe) – aren’t covered in any of the articles you sent me to. Which shows it’s a question Elementor hasn’t dealt with before.

The issue is this: these two URLs (and potentially other ones) are part of any default WP installation, so they should be included in your Theme Builder in order for a site to have a uniform look. Currently, however, only search and archive pages are covered by Theme Builder, leaving /uncategorized/ and /embed/ unstyled without additional hand-coding.

Hi @prestonwordsworth,

Elementor primarily interacts with the content and layout of your site, but certain reserved slugs and system pages may still fall back to the default theme styling. This is because Elementor’s styling and templates are applied to specific post types and content areas, while some reserved slugs and system pages are controlled by WordPress core functionality or other plugins.

To address this, you can create custom templates and assign them to those specific URLs. Please note that this feature is available with the Pro version of Elementor.

Alternatively, you can use custom code to apply the necessary styling to the problematic pages. For more detailed guidance, you can refer to Elementor’s developer resources on GitHub: Elementor GitHub.

Additionally, I recommend joining the Elementor Facebook Community where experienced users and developers share tips and solutions.

I hope this helps clarify the interaction between Elementor and reserved slug pages. If you have further questions or need additional assistance, please let us know. We’re here to help.

Kind regards,

This answer is on the right track, thank you!

Since Pro is outside the scope of this forum, let me return to my initial question. You wrote:

To address this, you can create custom templates and assign them to those specific URLs.

The only way this solution (creating custom templates) is going to work is by first knowing which ‘specific’ URLs require custom templates.

Has Elementor figured out yet exactly which URLs require such a custom treatment?

Hi?@prestonwordsworth,

No, Elementor itself doesn’t automatically detect which URLs need custom templates. It’s up to you, the user, to identify those specific URLs.

While Elementor Pro offers features for creating custom post templates, the free version focuses on page templates.

• Content variation: Elementor is excellent when you need different layouts for different content types. You might have a standard blog post template, but a separate template for case studies or product pages. Elementor can’t determine this distinction on its own.
• URL structure: While URLs can provide clues, they aren’t always definitive. For instance, you might have blog posts with different categories under similar URLs. You’ll need to consider the content itself to decide if a custom template is necessary.

Elementor, like other WordPress page builders, may not have full control over certain default slugs or pages generated by WordPress itself or by other plugins. These reserved slugs can sometimes cause issues where the default WordPress theme styles are applied instead of the Elementor styles. Here’s a general overview of how Elementor interacts with these reserved slug pages:

1. /uncategorized/: This slug is used by WordPress for uncategorized posts. If your site doesn’t use categories, this can still appear for any post that hasn’t been assigned a category. You may need to create a template for these pages in Elementor to ensure they are styled correctly.
2. /embed/: This slug is used for oEmbed iframe embeds, which are typically handled by WordPress’s default oEmbed functionality. Elementor might not have control over the styling of these embeds because they are rendered outside of Elementor’s template system.

To manage these pages and ensure they reflect your Elementor styles, you can take the following steps:

SEO Plugin Sitemap: Use an SEO plugin like Yoast SEO or Rank Math to generate a sitemap. Review the sitemap to identify any pages or slugs that are not styled by Elementor and create templates for them.

Use Child Theme: If necessary, make adjustments in your child theme’s functions.php file to control the output of certain reserved slugs and ensure they are styled properly by Elementor.

If you need help with this, you can contact our developers. This is where custom codes are discussed. GitHub – elementor/elementor: The most advanced frontend drag & drop page builder. Create high-end, pixel perfect websites at record speeds. Any theme, any page, any design.

Here are some additional resources that might be helpful:

• Theme Locations | Elementor Developers
• Add New Condition | Elementor Developers
• https://codex.www.ads-software.com/Category:WordPress_Development

Please let me know if you have any more questions. 

Kind Regards,