Skip to content

[Core] Allow selecting nested relations in the pattern. #283

@boazpoolman

Description

@boazpoolman

Feature request

Summary

When you create an URL pattern you are able to select relation fields. This feature request is there to also allow selecting nested relation fields. So you can select relations of relations.

Why is it needed?

A common use case will be a URL pattern like this:

/test/[category.url_alias[0].url_path]/[title]

In this case there is a content type, which has a relation to a category, that category has Webtools enabled, and thus has a URL alias. Now you want to create a situation where the first part of the URL will be the same as the URL of the category. You then need to create a URL pattern like shown above, and thus you need nested relations in the pattern. That is Page > Category > URL alias.

Suggested solution(s)

We should allow recursive relation selection. Where any relation can be selected, regardless of it's depth.

While implementing this we should also consider revamping the URL pattern input, as this will cause a lot more options to be possible and we should maby rethink the field selection UX.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions