Jump to:

23483 Posts in 18965 Topics by 2878 members

General Questions

SilverStripe Forums » General Questions » 2.4.0a - NestedURL Clashes?

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

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

Page: 1
Go to End
Author Topic: 551 Views
  • Double-A-Ron
    Community Member
    604 Posts

    2.4.0a - NestedURL Clashes? Link to this post

    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.


  • ttyl
    Community Member
    114 Posts

    Re: 2.4.0a - NestedURL Clashes? Link to this post

    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.

Page: 1
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.