We have moved to GitHub Issues
Created by Jeroen Breuer 12 Jan 2016, 10:48:33 Updated by Shannon Deminick 02 Aug 2017, 09:38:06
This is by design, moving forward no custom properties can be added to the legacy Generic Properties tab
This is by design. We want to move in a direction where you can't add properties to the "Generic Properties" tab at all. You could add an additional tab for special use cases like this.
If Link to document could be moved that would also solve it. Than I'll have a custom tab which shows the URLs and the Vorto property under that. We've had several customers ask for this feature. The first thing they want to see is the URLs when they open a node. So that could be the first tab.
When 7.4 final will be released it might be a good idea to update the default starter kit (think it's called Fanoe). Currently it still adds properties to the "Generic properties" tab. For example umbracoNaviHide. That could be confusing if people can't do that manually to new document types.
Marked as a breaking change for release notes.
@hartvig We like to put the 'umbracoNaviHide' property on the 'Generic Properties' tab. This seems like a sensible place to put it as it is a pretty general property that should be available on all our nodes that are pages. Whilst we could create a new tab just for this property it seem a little clunky.
Can you share the thinking behind the decision to prevent properties being added to the 'Generic Properties' tab?
I would also like to know the reasoning behind locking it, it is confusing to have generic properties then another random tab just for Navi Hide
@hartvig We have previously used this tab for a collection of node properties including (Link using SSL, umbracoNaviHide, umbracoUrlName, Hide Sub Nodes from Navigation, etc.) Another tab name (such as "Nav & URL" is vague to content editors... and to them is essentially the same as "Properties". What will tell a content editor that "properties" is where you set the publish and unpublish dates and choose the template, but not where you do these other things? I know it's not a big thing to make people look through both, but it's nicer to keep it on one tab.
I noticed the folks over at uSkinned have coded (or found?) a workaround with all their v7.4.3 sites combining their 'Generic Properties" tab and the Umbraco "properties" tab.
While I am open to listening to why the change was implemented, I don't currently see the reason and would vote to change it back.
PS: Thanks for all your work on this. Umbraco is my favorite CMS and I appreciate all you and the core team do.
A possible but somewhat messy workaround is to configure this tab in a 7.3 instance then upgrade it to 7.4
@jbreuer I'd up-vote this request; would really love to show the "link to document" on the tab where users are creating content, because it would be far easier for them to share the link (they sometimes mistakenly share the "preview" link which of course doesn't do much good). Better yet, add an option to the Publish/Save button with "Publish and view this page", so that users can immediately copy the URL for sharing. Telling users "go to the Properties tab, scroll to the bottom, click the Link to document field..." isn't as intuitive as they'd like.
I've released a package which can show the node URLs on any tab: https://our.umbraco.org/projects/backoffice-extensions/url-preview/
Disappointed to see no reasoning offered up here for this one. A whole new tab just for navi hide, and confusing editors with "Settings" and "Properties" doesn't seem thought out to me.
I agree, adding generic page properties to the properties tab was always really useful. It seems odd to have to create a tab now specifically for this purpose. Particularly when the only property I am adding is umbracoNaviHide. Ideally we should be able to add properties to the properties tab, or perhaps the core team could consider adding umbracoNaviHide as default property to that tab? If neither of this is possible, it would be nice to understand the reason?
This design change have been made to prepare for a bigger redesign of the content area for v8+ where we want to make sure we don't have old custom properties lying around for upgrades + prepare for new habits.
Backwards Compatible: False
Affected versions: 7.4.0
Due in version: 7.4.0