-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to set the default value on a property editor #2407
Comments
Yep, that would be a great idea, if anyone is up for helping out on this that would be lovely! 👍 |
Hi @PeteDuncanson, We're writing to let you know that we've added the For more information about issues and states, have a look at this blog post Thanks muchly, from your friendly PR team bot :-) |
The documentation already contains an example on how to set a 'default' value: https://our.umbraco.com/documentation/reference/events/EditorModel-Events/. I've added the quotes around default, as it actually resets the value whenever it's cleared. This example also has a lot of bugs/quirks, as it only sets the value for the first variant/language and throws exceptions whenever the tab or property alias isn't found (e.g. when it's renamed). Maybe the documentation can be updated with the example I posted in umbraco/Umbraco-CMS#7859 (comment) and/or we can make the whole process a lot easier by adding some helper methods... |
Hi guys! The EditorModels-Events article has been updated to use ContentSavedState. Would one of you be up for verifying, whether that update "solves" this Issue? 😄 |
The new sample code and the comments look good, so this issue can be closed IMO! |
Thanks for checking @ronaldbarendse ! 💪 I'll consider this one closed for now then. Have a fab' day! |
For reference, this issue is related to #2577. |
See umbraco/Umbraco-CMS#7859 for details of the origin of this one. Seems you can set default values via code but the only reference to it seems to be a video by Paul Seal. If that is the case then we should really get that documented in the offical docs.
Love your work.
The text was updated successfully, but these errors were encountered: