Reserved URL Slugs
What to do if you see this warning:
You should rename your page's URL Slug to avoid using reserved keywords as your URLs. (Learn what terms are reserved below!)
How to update the URL Slug
You can modify the URL Slug for a post or page in the editor by clicking the gear icon on the top of the screen. Click on Document, find the settings section labeled ‘Permalink’.
For embedded Views to work properly, edit the slug to another term that is not reserved.
What are the reserved URL slugs?
Some URL Slugs in WordPress and GravityView are reserved. Creating pages with reserved slugs will result in issues such as 404 error pages, and infinite redirects.
GravityView shortcodes and oEmbeds will not function properly against these URLs by default:
- example.com/search
- example.com/view
- example.com/entry
If you're trying to embed Views and single entries one pages with these URLs, you will get a warning message as an administrator that says: " GravityView will not work correctly on this page".
All other custom post type slugs are considered reserved and should not be used as page slugs. The warning will be thrown as well. If you are not sure which URL is triggering the warning you can find a verbose error log message by activating debug logging in GravityView.
Reserved URLs can be added (or removed) via the gravityview/rewrite/reserved_slugs
filter if required. This is only for advanced users.