Brandon
Brandon
This should now work out of the box in v4 with the routing updates.
I did change that as it was an oversight on my part to not have them properly ordered to begin with. Previously, ordering items in the backend had the potential...
I might've been over-thinking it when I did the change and there was perhaps no issue with having the ID's as it was before since they will always be unique...
I believe the latter (wrapping) _should_ work. https://github.com/Log1x/acf-composer/issues/230 has some more info.
ahhh I see. I will have to look into it when I get a moment but it might be an oversight
This should be better in https://github.com/Log1x/acf-composer/pull/267 – check the PR for examples.
I haven't used context so maybe someone else can chime in. It's been previously discussed [here](https://github.com/Log1x/acf-composer/issues/130) which might help.
You shouldn't need to repeatedly clear the cache nor re-publish the Poet config if you had already published it previously. Have you added the `post-autoload-dump` to your `composer.json` as shown...
Unfortunately you will have to debug a bit to see why that might be the case. There's no way for me to really know why it wouldn't be registering. Does...
Is Poet installed in the same `composer.json` as Acorn/ACF Composer?