- πΊπΈUnited States recrit
@blake.thompson correct, this was for the group content path in the form of
/group/{group}/content/{group_content}
.However, reversing the parameters also makes an assumption that the last is the correct entity.
The attached patch takes a better approach by getting the entity type from the route name and then using that to sniff out the matching route parameter.Future Considerations: Allow others to suggest an entity. Example: The group's gnode module could suggest the node referenced by group content instead of the group content entity. The node typically has the metadata needed for the page.