Josh Crawford

Ah right, that might be problematic, not to mention that won't work anyway. Firstly, that's going to load up the Asset element query with a `null` ID, so it's going...

I have a feeling this might indeed be an issue between Hyper and Vizy, which I _believe_ is fixed in Hyper 2.1.0 and Craft 5.5. But let me know if...

Still struggling to reproduce this one, sorry. I did replicate your field setup exactly as well. One question, in your video I noticed that after typing in the "CMS Identifier"...

In related news, I am in the middle of some refactoring to improve this behaviour, generally. I'd be keen to see if the latest changes I've been making improve your...

Thanks for confirming it's not working. I'm wondering if you might be able to reduce your fields as much as you can while still replicating this? I'd probably recommend creating...

@nitriques As I mentioned, can you reduce your fields as much as you can to replicate it in an exact scenario? While @Stepho288 video is excellent, there's a lot of...

Yeah, it's a known issue, but basically harmless. It's often in combination with Matrix as well, which is lacking some Vizy support in Craft 5. Basically, it's trying to update...

It's not actually possible amazingly enough (to add blocks from a toolbar button), but very easy to add - good thinking. You can also set "Block Type Picker Behaviour" to...

Good call on the Sanity comparison, I haven't checked in with that for a while now. I've even been on the fence for some time about the current block-picker in...

This is a great point, in that we need to look at hooking into the merge process, and update the field handles in vizy content. This is done in normal...