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
Yeah, the site routing.yml takes higher precedence than the extension added routes. This is also the reason for https://discuss.bolt.cm/d/6-routing-for-sitemap-while-using-pagebinding. It isn't really an issue with this extension, but it could be fixed in this particular instance by naming the route something slightly more unique in the extension like "extensionBoltLabels" or whatever.
Hi,
don't know where to put this, but I figured I start out at the labels extension. I have a tags taxonomy type named: 'labels'
I want to view this in the frontend under the route: /locaties/{taxonomytype}/{slug}
Therefor I have a routing:
This all works like a charm, however. I now can not access the eedit labels page for the labels extension: /bolt/extend/labels
the page loads with the following error:
Removing the addition in routing.yml solves it. But I want that routing! Where's the bug?
Using Bolt 3.2.9 and Labels 3.0.7
The text was updated successfully, but these errors were encountered: