wwww.example.com/news - displays list of news content in cms wwww.example.com/news/some-news-story - single news page generated in cms wwww.example.com/news/some-news-story-2 - single news page generated in cms
wwww.example.com/results - displays list of results which when clicked will take you to result article from custom table wwww.example.com/results/1 - single result page generated from custom table wwww.example.com/results/2 - single result page generated from custom table
wwww.example.com/results - cms page load custom data from snippet wwww.example.com/results?id=1 - if id 1 exists load custom data else return 404
This question has been answered by Jako. See the first response.
However I was unsure the correct way when it comes to custom generated data:
Take a look on the CustomRequest extra.
Try wwww.example.com/results/1.html
It should work that way.
I have updated the package for logging the found configuration together with the additional request parameters set by that configuration. The log level for invalid configurations is changed from info to error in debug mode, so you should notice those issues.
0 === strpos($search, $request['alias'])