Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
This is a very cool datatype, but I've got a strange problem occurring. I'm using Umbraco v4.7 with uComponents 2.2 Beta 3, and with the Multi-Node Tree Picker when I expand the folders within the 'Select Items' tree they sometimes don't load the children (I have 2 levels of folders/nodes beneath the root select node). It just briefly shows the loading/expanding animation and then nothing happens as if the folder is empty. Sometimes this happens quite often, eg. 1 out of every 3 times, other times it will work fine for 10 or so times in a row. Once it fails to expand one tree item, then all other trees within that 'Select Items' section fail (including Multi-Node Tree Pickers in the other tabs) until I refresh the page. I have tested in different browsers and its happening in Firefox 5, Chrome, IE9.
I have done some more testing with this using Umbraco 4.7 and uComponents v2.1 RTM, and the problem still occurs but it seems to happen only when I have more than 1 Multi-Node Tree Picker property on a document type. It happens when the properties are on the same tab, and also when they are on separate tabs.
Same issue here, on Umbraco 4.7.0 and uComponents 2.1 (latest stable release). Oddly enough, the tree pickers work fine on our test server, but on my local dev maching they don't load. As jonok describes, only the root folder is displayed, but no children appear. I experience the problem regardless of whether I have one or more MNTP controls on a single tab or document type.
My web inspector console displays an Error 500 for each instance of the MNTP, with different "rnd" values for each instance:
I have seen this 500 error before ... however it disappears once I restart the app-pool (or touch the Web.config). I've been unable to debug this, as I can not figure out how to replicate the error, and once I see the error, attaching Visual Studio to the w3p.exe process restarts the app-pool (making the error disppear!)
If you can figure out how to reproduce the error, that would be great.
Thanks for the quick reply, Lee.
I'm not hooked up with Visual Studio, so I'm afraid I can't help much there. And unfortunately I have no problem reproducing the error, which is consistent across app pool recycles and web.config touches. But only on my dev machine, not on our test server, and not on my colleagues dev machine either. All are running IIS 7.5 and .NET 4.0.30319, and I can't see any other environment variables, that would affect it. I'll let you know if I discover anything that points to some reason or consistency.
Request URL: http://domain.com/umbraco/webservices/TreeDataService.ashx?rnd=c82d9828543a4444ad330f69dbafb7f8&id=1691&treeType=FilteredContentTree&contextMenu=false&isDialog=true&dialogMode=id&nodeKey=1648&rnd2=99.8
@Lee: Mysteriously, all my MNTP instances have started working again. An unrelated bug caused all my Umbraco nodes to unpublish themselves (oh joy), and to solve that problem I deleted my entire App_Data/TEMP directory, including all Examine indexes, and then published all my nodes again (not just "Republish entire site" to refresh the cache, but actually republishing each node). After that, the MNTPs suddenly worked again.
I can't be sure of the actual cause-and-effect here, as I could easily have done something else that affected it, but is there any chance that the MNTP rendering would be tripped up by unpublished (or "semi-published") nodes, or anything to do with the Examine index? Or more likely something in the ClientDependency folder in the TEMP-directory, which I also deleted?
I had a similar thing just now whereby no content tree was being rendered by the MNTP at all (on a new 4.7.1 installation running SQLCE). I deleted everything inside App_Data/TEMP and it fixed it. I've no idea if this is anything to do with the examine index as per Dan's suggestion above, but I had used the back-office search facility just prior to setting up the MNTP data type, which I think does do something with the Examine index.
Thank you, Dan. Solved my problem
EDIT: Turns out there were just parts of the website that I missed out while publishing. Would still like to know why this happened in the first place.
Has anyone found what is actually causing this? It is happening on my site and deleting the App_Data/TEMP directory didn't solve my problem. I'm running Umbraco 4.7.2 with uComponments 3.1.0.
A bit more background... my site was running fine until something triggered certain parts of the site to disappear. Went through various attempts to fix it by "Republish entire site", rebuilding indexes, deleting App_Data/TEMP directory. Finally got the site back but had to manually publish the entire site. Now site is running fine however all the MNTP (in content section) are empty.
i just had the same experience.
My MNTP are all empty right now, the selections are there but nodetree on the left where missing.
but after an apppool recycle it all worked again.
The call with the error in looked like this :
I have a similar problem with 4.11.1! the problem is content tree is working fine on some clients and does not work at all in some other clients! also in IE9 it does not show at all!
I've tried clearign temp/clientdependency and various workarounds here and there but still no change in this behaviour!
I'd appreciate any help I can get!
Sorry it was a dumb mistake of me!!!
I was getting this issue too, tried most steps suggested including deleting the umbraco.config file in the App_Data folder along with the contents of the TEMP folder without success. Also tried recycling the App pool which also made no difference.
What finally worked for me was republishing the whole site using http://MYDOMAIN/Umbraco/dialogs/republish.aspx?xml=true rather than just using the 'Republish entire site' option on the content root.
Had the same problem. And this MYDOMAIN/Umbraco/dialogs/republish.aspx?xml=true also fixed my problem
Republishing isn't a great option if you have a large content tree (takes too long). Anyone got any real fix ideas?
Had the same issue/error in de console log.
There was a node created which had a 'SingleOrDefault' in the code and was only allowed to be created once.After deleting the node (which only can be done in umb 6.1.6. through the database due a bug), my issue was solved.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted