Josh Crawford

Fixed for the next release. To get this fix early, change your `verbb/cp-nav` requirement in `composer.json` to: ``` "require": { "verbb/cp-nav": "dev-craft-4 as 4.0.6", "...": "..." } ``` Then run...

Fixed in [4.0.7](https://github.com/verbb/cp-nav/releases/tag/4.0.7)

Hmm, I wonder if your project config may have gotten out of sync? If you download your database from production, to your local dev environment, then run `./craft project-config/rebuild` that...

@peerfischer can you comment on any of my directions above? Are you also on Fortrabbit?

Still struggling to reproduce this, sorry! I've been at it all day making changes, messing around with the CP Nav items themselves, and messing around as much as I can....

Would love to have a response to some of those questions, particularly if this is an upgrade from Craft 3 or a fresh install of Craft 4? And that's on...

Thanks for the clarification, I'll keep diving into what's going on here. The hardest part seems to be reproducing it for me, but with at least 2 people having this...

If anyone can send their database or `composer.lock` and `composer.json` files to `web at verbb.io` hopefully that will give me some clues as to how your install is different.

Thanks @ursbraem still trying to figure out how it's happening to you all, but not with my several test installs!

@ursbraem That would make sense as the entire nav seems to be re-generated. And for subnav items that have a parent, they would be referring to the new parent.