Josh Crawford

This is correct behaviour, with how Craft handles content propagation at least. To illustrate, this same behaviour happens with entries. Creating a section on a multi-site install, enabled for multiple...

If you're talking rendering a thousand nodes, then yes there are some things to consider. Navigation nodes aren't inherently expensive to render, but the same would apply as if you...

Two things of note - firstly nesting it within the `entry` interface might be tricky without creating a custom field that is owned by an entry. But it _might_ be...

As of https://github.com/verbb/navigation/commit/fb2e4eee401c8fbae8af2ed76d10058528fbdc34 track changes are enabled, so this should be all that’s required?

So long as I understand correctly, this isn't something that's possible or going to be incorporated. Navigation doesn't define the URL or slug of **element** nodes, that's defined by the...

The tricky part here is that the move event is controlled by Craft's [structures/move-element](https://github.com/craftcms/cms/blob/c436b066065c2ca53d6f63154f5cc8aefe06aab2/src/controllers/StructuresController.php#L125) controller which doesn't give us much opportunity to provide a better error message. We would need...

Good call on needing `structures::EVENT_BEFORE_MOVE_ELEMENT` that’s true. I’ll see what I can do to improve this. Although they are two different things - one is a save event, the other...

That's great news to hear! I've just added the `UserException` on my end when moving nodes, and you could do the same in your custom validators, swapping out `$e->isValid =...

Thanks for that! Yep, might be it's own separate widget, or just adding some settings to chose what to show. Appreciate it 👍

I know this is an old post, but it first guess, I would say this sounds like a caching issue with Facebook. I imagine by the 'wrong' image, it would...