puuh, was to early :-( now, one hour after upgrade - content- and mediapicker shows only top node (content, media) again. did not do anything in this installation.
OK, figuered out the problem, but do not know how to handle it.
I upgraded to version 4.0.2.1 (this is what the web.config has as umbracoConfigurationStatus as well) when I change the umbracoConfigurationStatus to 4.0.2 the content- and mediapickers show their subnodes and everything runs well.
BUT when i do this, the install procedure of umbraco is starting as soon as I try to reach the website.
Hm, what to do? Would be happy for any suggestions.
this is a serious problem for the editors of the website because they cannot insert any images from medialibrary as well as doing other stuff related to some properties in the document types.
i think of a workaround changing the version of umbraco (related to my last post in this thread) which is used when calling the webpage to version 4.0.2 - but i dont know where this is stored. In older umbraco versions there was a version.xml but this is not used anymore.
Have you tried republishing the content? Right click on the parent tree-view node in the content section, and choose "Republish entire site". Also, you can try right clicking on the Home page node for the site (from which all the site pages descend) and choosing Publish, then Publish all child nodes.
I have another site running v 4.0.2.1 (fresh install). here i dont have this problem hm, maybe something went wrong with the update process. it's just hard to figure out, because everything else runs fine
I dont think it has something todo with the cache or like this.
To make things clear. The regular content tree on the left side is presented correct. It "only" affects the pickers (content/media) Everything went fine after upgrade as long as the umbraco upgrade process (the one you are redirected to if you update the dlls and stuff) didn't start. The process touches te web.config and updates the "umbracoConfigurationStatus" in this case to 4.0.2.1
The point is, when i change the "umbracoConfigurationStatus" to 4.0.2 or less the content- and mediapickers in the backend work correct. It behaves wrong (with only top node showing) when this is set to the correct version.
I even copied the updatable files (/bin, /install, /umbraco, /umbraco_client) another time over the installation as i supposed that something was missing. But this did not change anything.
There is a bug in Concierge 2.0 that causes this behaviour (content and media picker not showing the tree). There will be a new version available today that fixes this issue.
At
/umbraco/tree.aspx?rnd=079e3b42-e7a5-4071-b684-4186981e241b&id=-1&treeType=content&contextMenu=false&isDialog=true&dialogMode=id
(Referred by:
http://dnsdev.dns.de/umbraco/treeinit.aspx?rnd=235d8d7c-05c3-4a7a-a713-3c2819e3d610&id=-1&treeType=content&contextMenu=false&isDialog=true&dialogMode=id&app=content):
System.NullReferenceException: Object reference not set to an instance of an
object. at Umbraco.Concierge.LockUnLock.Events.TreeEvent.a(XmlTree& b,
XmlTreeNode& b, EventArgs b) at
umbraco.cms.presentation.Trees.BaseTree.BeforeNodeRenderEventHandler.Invoke(XmlTree&
sender, XmlTreeNode& node, EventArgs e) at
umbraco.cms.presentation.Trees.BaseTree.OnBeforeNodeRender(XmlTree& sender,
XmlTreeNode& node, EventArgs e) at
umbraco.cms.presentation.Trees.BaseContentTree.Render(XmlTree& Tree) at
umbraco.loadContent.Render(XmlTree& Tree) at
umbraco.cms.presentation.tree.LoadTree(String treeAlias) at
umbraco.cms.presentation.tree.Page_Load(Object sender, EventArgs e) at
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object
t, EventArgs e) at
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs
e) at System.Web.UI.Control.OnLoad(EventArgs e) at
umbraco.BasePages.BasePage.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
which looks like "concierge" has something todo with it
Contentpicker only shows the top node (content)
Hi,
recently the contentpickers in one of my sites started to show only the top node (contetnt).
I have no idea why.
I have installed concierge and courier recently. Maybe it has something to do with this - but i'm not sure.
Any ideas?
Thank you
/Horst
just realized that its the same for mediapicker - only top node (media) is showing up.
did anyone have the same problem?
/horst
problem is solved!
upgrade from 4.0.1 to current version 4.0.2.1 made it work again!
/horst
puuh, was to early :-(
now, one hour after upgrade - content- and mediapicker shows only top node (content, media) again.
did not do anything in this installation.
am a bit helpless now :-(
any ideas?
thank you
/horst
OK, figuered out the problem, but do not know how to handle it.
I upgraded to version 4.0.2.1 (this is what the web.config has as umbracoConfigurationStatus as well)
when I change the umbracoConfigurationStatus to 4.0.2 the content- and mediapickers show their subnodes and everything runs well.
BUT when i do this, the install procedure of umbraco is starting as soon as I try to reach the website.
Hm, what to do?
Would be happy for any suggestions.
Thank you
/horst
anyone any suggestion?
this is a serious problem for the editors of the website because they cannot insert any images from medialibrary as well as doing other stuff related to some properties in the document types.
i think of a workaround changing the version of umbraco (related to my last post in this thread) which is used when calling the webpage to version 4.0.2 - but i dont know where this is stored. In older umbraco versions there was a version.xml but this is not used anymore.
would be happy for any help
thank you
/horst
Horst,
Have you tried republishing the content? Right click on the parent tree-view node in the content section, and choose "Republish entire site". Also, you can try right clicking on the Home page node for the site (from which all the site pages descend) and choosing Publish, then Publish all child nodes.
Hope this helps,
JT
hi JT,
tried already, but no success.
I have another site running v 4.0.2.1 (fresh install). here i dont have this problem
hm, maybe something went wrong with the update process. it's just hard to figure out, because everything else runs fine
/horst
Hmm. I find it strange that the nodes displayed for a while, and then disappeared again. It makes it seem like a funny caching issue.
Is there any action that you can take to get them to reappear?
Hi JT,
I dont think it has something todo with the cache or like this.
To make things clear. The regular content tree on the left side is presented correct. It "only" affects the pickers (content/media)
Everything went fine after upgrade as long as the umbraco upgrade process (the one you are redirected to if you update the dlls and stuff) didn't start. The process touches te web.config and updates the "umbracoConfigurationStatus" in this case to 4.0.2.1
The point is, when i change the "umbracoConfigurationStatus" to 4.0.2 or less the content- and mediapickers in the backend work correct.
It behaves wrong (with only top node showing) when this is set to the correct version.
I even copied the updatable files (/bin, /install, /umbraco, /umbraco_client) another time over the installation as i supposed that something was missing. But this did not change anything.
so, still helpless :-(
/horst
Comment author was deleted
Hi Horst,
There is a bug in Concierge 2.0 that causes this behaviour (content and media picker not showing the tree). There will be a new version available today that fixes this issue.
OK, found this in the umbraco log:
which looks like "concierge" has something todo with it
hi tim,
just figuered out from the umbraco log that concierge could be the shooter
thank you
/horst
just installed concierge 2.0.1
everything runs fine again!
/horst
...and thank you JT
...and hmm, my suppose in the initial post was right ;-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.