-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Could not find a value for configuration field '{ConfigField}' #11488
Comments
Actually I think it works as expected as it create a separate property "ConfigField" which in this case has the value "preview". |
@bjarnef This is interesting, as the "preview" configuration value (of Contentment's Data List) doesn't hold a value - it's a read-only field. So by that logic, it would always log a warning. That doesn't seem quite right - what's the purpose of the warning? Did something go wrong? (that's more a conceptual question) Are the built-in DataTypes immune to this - if so why? 🤔 |
@leekelleher yeah, I think there are use-cases like this, where you could have a config property, which doesn't store a view like this, but it seems to complain because the property exists while not holding any value. I don't remember if prevalues in property editors used to have a However not sure it is an issue (except pollution of the log files with these warnings) - at least not in v8. |
@bjarnef The
|
@bjarnef I think we should re-open this issue, as should Umbraco be raising a warning if a DataType's prevalue doesn't have a value? Is the suggestion that read-only prevalue editors shouldn't be used? |
Hiya @bjarnef, Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more. We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed). To open it this issue up again, you can write For example:
This will reopen the issue in the next few hours. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
9.0.1
Bug summary
When working with Contentment v3.0.0 and Umbraco v9.0.1 I got these warnings in log file:
Originally reported in Contentment repository here, but it may be an core issue when changing property editor of an existing datatype:
leekelleher/umbraco-contentment#176
However the log message
Could not find a value for configuration field '{ConfigField}'
isn't very useful. I think it was meant to log name of "ConfigField" ... not logging the value{ConfigField}
🙈This line is logged here: https://github.com/umbraco/Umbraco-CMS/blob/v9/contrib/src/Umbraco.Core/Models/Mapping/DataTypeMapDefinition.cs#L179-L180
Specifics
No response
Steps to reproduce
Not sure there's is an easy way to reproduce. In my use-case I originally change property editor on an existing datatype from radiobutton list to
[Contentment] Data List
property editor and when models generation failed I noticed these log errors.@leekelleher mentioned it may be a bug with cache not being refreshed when changing property editor of an existing datatype.
Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: