You haven't chosen a valid URL Slug
Permalink
I'm trying to add a specific page type via the Sitemap and am getting this error when trying to publish:
You haven't chosen a valid URL Slug
The URL slug looks fine on first look. For example the page name is 'Test Project' and the URL is 'test-project'.
The interesting part is that it only happens when I add this page type via the Sitemap. If I add it via the new page icon at the top right of the Concrete5 Toolbar, it works fine. Although when you add it that way, it runs through the composer. When I add a page via the Sitemap, it's just the standard page addition. I've attached an image of the error message for reference.
Any ideas?
You haven't chosen a valid URL Slug
The URL slug looks fine on first look. For example the page name is 'Test Project' and the URL is 'test-project'.
The interesting part is that it only happens when I add this page type via the Sitemap. If I add it via the new page icon at the top right of the Concrete5 Toolbar, it works fine. Although when you add it that way, it runs through the composer. When I add a page via the Sitemap, it's just the standard page addition. I've attached an image of the error message for reference.
Any ideas?
I'm experiencing the exact same, in 5.7.5.3
Hi leinteractive,
Have you checked the bug tracker to see if others are experiencing this issue? If no one has reported this issue, I recommend reporting it and including the steps required to repeat the error.
concrete5 bug tracker
https://www.concrete5.org/developers/bugs...
Have you checked the bug tracker to see if others are experiencing this issue? If no one has reported this issue, I recommend reporting it and including the steps required to repeat the error.
concrete5 bug tracker
https://www.concrete5.org/developers/bugs...
This is reproducible in the latest version of 8.2 if you mark the url slug as required.
@aenowwebsite
Can you list the steps to reproduce the issue, please.
If I can reproduce it, I can create a GitHub issue for it.
Can you list the steps to reproduce the issue, please.
If I can reproduce it, I can create a GitHub issue for it.
Having the same issue