Bob den Otter

Hi, @Spidlace, If we merge this in, as-is, won't it break the behaviour that we currently use in things like `title_format: "{name} - {id}"` ?

Some other pitfalls we'll need to avoid if we're going to refactor this and introduce breaking changes: - the fields configuration (and primarily the "options" and its "attr" flags) are...

Hi! It's not a bug, it's a feature. ;-) Disable the honeypot, in Boltform's YAML, if yo don't want it.

This is weird.. Firefox is my primary browser, and i've never envountered this problem myself. What errors are you getting exactly?

Please update this issue with the information from the issue template, which we've carefully put together and you have deftly removed.

Hi, @LewisHobden Sounds good. Would love this as an improvement for Bolt. Some initial thoughts: > Flysystem V2 Yes, let's go straight for v2! Knowing Frank, what he labels "beta"...

It's not supposed to work like that, i think.. Webpack is for *bolt itself*. The themes should be agnostic, and separate from that. What are you trying to achieve?

Hmm, I'm not sure this is a good fix.. This will effectively "rename" a user to have id `1`. If that specific user already has content, it'll be linked to...

> @bobdenotter yes right. Then let us just make the currently created user have the id `1`? Yes, you mean whenever we create a user, to ensure there's one with...

Bumping this to a later version. If there's a valid usecase, we can bump it higher on the priority list again.