Here's the initial discussion on this, and alternatives. https://github.com/Pylons/pyramid/issues/881
On Tue, Mar 11, 2014 at 9:49 AM, Ron Drongowski <[email protected]>wrote: > Hi, > > I suppose this question has been answered somewhere but I could not find > an explantion. We are creating a traversal based pyramid-app using our > ZCA-based components we designed for our CMS. So for a regular article an > url would look like this: /path/to/my_article. Traversal ends and we can > register a default view (name=''). This is easy. But, since we have a lot > of SEOs around us, we have very specific needs for custom-urls. We were > asked ro realize the scheme /path/to/my_article/page-2 for the second page > of an article. This would lead to an dynamic view_name, which is currently > not possible - even in an hybrid application, if I understood the > documentation right. I assume you could solve this problem by either > registering a lot of views, extend the traversal (implement an __getitem__ > for the article) or implement your own request factory. All of which do not > seem to be the right thing, while a regex view-name seems to be th eright > thing. Is there a solution for this? > > Thanks a lot. Greetings, Ron > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
