Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

2.4.0a - NestedURL Clashes?

Go to End

2 Posts   775 Views


Community Member, 607 Posts

13 November 2009 at 11:52pm

Quick question:

Just been picking the new NestedURLs of 2.4.0a down to RequestHandler->allowedActions().

Is there any plans to provide any notification or feedback to the CMS user when a clash, either in from an controller action or from an existing URLSegment, occurs?

It's fairly easy to explain why the "-2" shows up on URL's and why this happens when naming pages in the CMS. But when they have absolutely no access to, or knowledge of the existence of controller actions in the code, would it be possible to provide at least a warning to tell them *why* the clash has occurred? Quite often, our users don't even know that the "-[n]" has been added to the URL.

Just throwing it out there.



Community Member, 114 Posts

14 November 2009 at 10:15am

I have the exact same question. I'd much rather an alert and force the user to manually enter a new URL than silently 'fix' things for them.