Skip to content

Conversation

@chrissigmon
Copy link

This feature allows content editors to set defaults for fields above Standard Values. However, Standard Values will override the Fallback value, which we would want.

Chris Sigmon added 30 commits March 28, 2016 15:03
… deployment then enable it once project is set up.
…ates to dynamically create content items. Fixed spelling error in setting name.
…e event will delete the item when the template is deleted.
…content item in the location specified in the config file when a template is created in a specific location specified in the config file.
…h the database the developer intends since we are dealing with events
…on methods, reduce code, and additional config file changes integrations
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Demo.Web", "Demo.Web\Demo.Web.csproj", "{CC55891F-E4DE-4EBD-9A01-0F4498E49FCF}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = ".tds", ".tds", "{82477168-C91B-4DEA-BBFB-0FE78B4900CC}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This folder wasn't checked into source control and shouldn't be included in the SLN file.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been corrected!

{
using (new SecurityDisabler())
{
return field.Item;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't you be locating and returning the "Default Values Item"? This method it just returning the same item it already has.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants