We have moved to GitHub Issues
Created by Hefin Jones 12 Nov 2014, 13:47:40 Updated by Claus Jensen 17 Jan 2017, 07:32:18
Relates to: U4-8763
Relates to: U4-5769
This worked as I would expect with the text string outputted to the page using
However when I went to add an additional property to the "SEO" document type e.g. "Description (description)" and tried to output the text using
Nothing appeared was outputted to the browser ... and using:
Resulted in "Object reference not set to an instance of an object" error
So even though the new property is visible on the "Page" document type in the Content Section - the property doesn't actually work. I can see the property appearing in the umbraco.config file ok,
The only way I've managed to get it to work is to un-assign the "SEO" document type from the "Page" document type and then re-assign - this then makes the property work again - but obviously by doing this the existing content is lost!
This still seems to be an issue in version 7.2.1 - meaning we would need to get our composition document type properties absolutely correct at the very first attempt as the issue outlined above would stop us from making any amendments to the document type after it's used as a composition - is there a workaround for this or is it expected behaviour?
I had a really long night trying to render a property that just came out blank (when using Razor). Switched to an XSLT macro this morning (because the property was clearly visible on the Doctype when inspecting with XMLDump) and it just rendered as expected.
The property was created with the alias "telephone" but later renamed to "phone".
I blame poor cache refresh - esp. if I understand correctly that the ppty is in the XML but does not render in Razor (assuming it's MVC Razor and not legacy Razor?). Will try to look into it.
"Stock" 7.2.1 Razor (MVC, right?)
Yes "stock" is what I call "MVC" ;-) If the value is in the XML document but GetPropertyValue returns null, it means that the content type we use to look for properties does not know that the property exists, ie has not been properly refreshed.
Currently working on fixing events & refreshing for content & content types...
I just reproduced this in a clean Fanoe install, and it does seem to be a cache issue. When I touch the web config, then the new content shows up.
@mortenbock Great, good to know :-)
Just hit this one this morning also.
I just hit this one on an Umbraco 7.3.1. Recycling the application pool (touching the web.config) fixed it!
Could not reproduce on 7.4. What I have done:
It is that last line which I assume should fail? Is it possible to test again on 7.4 and tell me whether you can replicate?
Proposing to close as "not repro".
@zpqrtbnk I can still repro, using the steps as described above (SEO tab, create title, publish page with title, add description, publish page with description,
@Model.Content.GetPropertyValue("description") doesn't show anything).
navigate to document => works
But did you add content in the description property and does it show on the page? Nothing breaks, this is true, but it also doesn't show the description content.
ok, trying again
cause: when clearing the published content type cache, we clear the content type that has been modified but do not propagate to composed types, fixing...
yup, that fixes it, thanks!
Which Umbraco version is this due in? I'm not sure if this fix was applied to 7.4.3, as I'm experiencing the same (or a very similar) issue: http://issues.umbraco.org/issue/U4-8763
The commit in the merged PR is part of 7.4.2. Will look at the other issue.
Backwards Compatible: True
Affected versions: 7.2.0, 7.4.1
Due in version: 7.4.2
Sprint: Sprint 10