Thanks for the feedback, will see if we can address this as a minor improvement.
+1 for this
Finally this gets some notice. I only made the suggestion in June 2015.
Thanks to Sebastien for bumping it up :)
I assume this is a minor annoyance that everyone agree is annoying; or if this is a bigger problem, why :)
For my part it's a minor annoyance. As Per said "It would be nice if the behaviour was the same", in other word, it's about CONSISTANCY. One of the corner stones of a good user experience.
If inconsistancy is frequent, then, that is a big problem. But fortunately it's is not the case with Episerver, as far as I have seen.
I would really like this to be fixed as this makes it more difficult for my editors :)
Another +1 here - this is causing some issues for one of our clients with users who do not normally use CMS, but very infrequently need to create crisis messaging content. They're getting confused by the block-creation page not containing the non-compulsory fields.
Just FYI, the dialogue intentionally works like this to make it quick to insert new blocks. We are looking at ways to make it more consistent though.
If I choose to create a new block using the create new link in a contentarea I get a view where I see both required and non required properties. But if I instead click the create new content button in the toolbar I only see the required properties.
It would be nice of the behaviour was the same.
I would also like that for page types but maybe it should be configurable with an attribute on the model or something like this because there tend to be a lot more properties on a page type than a block.