Ben Thomson
Ben Thomson
@mjauvin this will just need the `@event` docblocks detailing the event and its usage so that the Winter docs will pick it up as an available event.
@mjauvin would you be able to clarify the state of where we're at with this problem? Your comment last week mentioned this PR was not needed, but now it has...
@mjauvin does the same issues occur when you use the form events / callbacks inside the controller, as opposed to those in the model? I think I've been fairly open...
Unless I was mistaken, the original issues were from using the `filterFields` function in a model (or the `model.form.filterFields` event) to hide a field. Can you hide a field using...
I don't know myself. I tend to avoid this sort of magic and apply the rules to the models themselves through `beforeSave` callbacks or things of that nature. As I've...
Perhaps, and until someone presents a form configuration so complex as a test case, I'll remain blissfully unaware.
@LukeTowers the changes on the staging site need to be merged in first, but theoretically all that's required is for us to split off the docs into another branch for...
Fixed as of https://github.com/wintercms/docs/commit/bd8f63731e63e89ff0cf38c2aa58326b1cd773a4
@LukeTowers we can add a parameter to the Skin class that defines whether to load the global assets or not - thereby making it the responsibility of the skin to...
So basically just can this PR because that's what was done originally?