Aha, as of Bolt 3.3, it seems that unneeded parameters are stripped out, that means we probably won't have access to id anymore as the contentlink route defined in routing.yml has its path defined as {contenttypeslug}/{slug}.
This extension is still broken in Bolt 3.3 even with the isset checks, because I currently need that id for getting that hierarchical URL. I think it can be partially solved by making another lookup table from $contenttype/$slug to $contenttype/$id.
Aha, as of Bolt 3.3, it seems that unneeded parameters are stripped out, that means we probably won't have access to
id
anymore as thecontentlink
route defined inrouting.yml
has its path defined as{contenttypeslug}/{slug}
.Compare 3.2 and 3.3:
This extension is still broken in Bolt 3.3 even with the
isset
checks, because I currently need thatid
for getting that hierarchical URL. I think it can be partially solved by making another lookup table from$contenttype/$slug
to$contenttype/$id
.