You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case that right now it's not supported by TSR. I'd say it's not an issue, more than a lack of support/feature request.
I work with a CMS (https://plone.org) that uses a concept that is called "object traversal" to retrieve the objects stored in the CMS database. The objects are stored in an objects/documents DB that is able to store them in a hierarchically way (as a file system, with parent/child structure). So they map the way it's stored directly with the natural organization of a website:
/folder/nested-folder/page
in the DB, the folder object is the parent of nested-folder and this one, will be parent of page. When the user calls that URL, it traverses the tree until it gets to the page content, then that content is rendered.
We can match this via "splat" routes, all fine.
Then, the tricky part. The traversal concept also accepts the idea of "views" or actions applied to the content objects. Then the edit view becomes:
/folder/nested-folder/page/edit
So instead of the public view mode rendered content, you get the edit form of that content.
I noticed this can't be achieved, not in TSR, nor in any other modern router. We are currently using RR5, which supported this back then, but I noticed that RR6 does not support it either.
Is that something that it's sensible to add as a feature? is it difficult to achieve?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a use case that right now it's not supported by TSR. I'd say it's not an issue, more than a lack of support/feature request.
I work with a CMS (https://plone.org) that uses a concept that is called "object traversal" to retrieve the objects stored in the CMS database. The objects are stored in an objects/documents DB that is able to store them in a hierarchically way (as a file system, with parent/child structure). So they map the way it's stored directly with the natural organization of a website:
/folder/nested-folder/page
in the DB, the folder object is the parent of nested-folder and this one, will be parent of page. When the user calls that URL, it traverses the tree until it gets to the page content, then that content is rendered.
We can match this via "splat" routes, all fine.
Then, the tricky part. The traversal concept also accepts the idea of "views" or actions applied to the content objects. Then the edit view becomes:
/folder/nested-folder/page/edit
So instead of the public view mode rendered content, you get the edit form of that content.
I noticed this can't be achieved, not in TSR, nor in any other modern router. We are currently using RR5, which supported this back then, but I noticed that RR6 does not support it either.
Is that something that it's sensible to add as a feature? is it difficult to achieve?
Thanks for in advance!
Beta Was this translation helpful? Give feedback.
All reactions