[eluser]Rolly1971[/eluser]
well you may need to alter the code to test for 'xyz/(:any)' in the route, and resort the array returned in order to ensure it is not overriding other routes.
personally, though, i do not use db driven routes. i use the CI routes file with generic route defs to determine what needs to be loaded for content from the db. Using the controllers index function to test the uri.
in my case, for the front end site, the first segment of the uri is the page that needs loading.
eg:
example.com/about, example.com/register, example.com/login all get routed to the welcome controller. the index function reads the uri segment and loads the content from the db based on the uri string.
when a new page is added to the database in the admin, a new menu item is also created in the db, which is then loaded into the page on next page load. With the 'name' field being used as the uri segment.
this probably does not really help our situation though, but like i said, you may need to alter the MY_Router to do checks for (:any) in the route and resort the array to ensure they do get put in the right spot as not to override end user defined routes.
