Bart Nagel

Is there any workaround to use this feature before this patch is merged?

Possibly related, I can't start the VM with this installed, and it appears to be due to a space in the path to the VM itself: ``` /Volumes/Macintosh HD Storage/.vagrant.d/gems/2.4.4/gems/vagrant-notify-forwarder-0.5.0/lib/vagrant-notify-forwarder/action/start_host_forwarder.rb:24:in...

I eventually got things working -- the issue was where VAGRANT_HOME was rather than where the VM was. I had VAGRANT_HOME pointing to something in `/Volumes/Macintosh HD Storage/...`. I believe...

I'm actually not using twig at all -- we're using Craft in headless mode, and have a separate application which fetches data via GraphQL. I think a custom node type...

So with the above issues still standing, I have this working. My PHP class looks like this. ```php

> Sorry, I may have explained that incorrectly. Custom fields are for all node types, and are managed in the Navigation settings, under Node Fields. You won't see then in...

I'm giving that a try. It couldn't find my template and so I added this to my module: ```php Event::on( View::class, View::EVENT_REGISTER_CP_TEMPLATE_ROOTS, function(RegisterTemplateRootsEvent $event) { $event->roots["myapp"] = __DIR__ . "/templates";...

I've discovered why I shouldn't continue exploring late at night. I was totally overthinking this. I can simply use an "entry" node, and point to my bookmark entry. It doesn't...

There was no error actually being thrown. Maybe something changed upstream: it looks like you now need to pass `rethrow: true` as part of `twigOpts`. Adding this in gulp-twig/index.js around...

The thing is, upstream twig doesn't throw you the error at all unless you pass that `rethrow` option. It has its own catch block, catches its own error and produces...