Thought of one more type of component: Child Content Picker
Of course i thought of it while working on a new umbraco site. I have a site with a lot of nodes (i mean a lot of a lot of nodes) and it is split up between 3 seperate domains with different articles on each. In one spot I want to be able to select about 6 articles from the children of the current node but when i use the content picker it shows all nodes. when i use the ultimate picker it displays way too much at once (there are thousands of pages) since the display types you can choose are usually ones that will either load everything at once or have you guess at what the name of the page is.
So the idea i have is a content picker with the standard popup just like the regular content picker, but instead of showing all folders for the entire site, it only shows folders that are the children of the node you are currently on.
i dont know how hard or easy that would be to impliment because right now it was just an idea of mine.
On the multi node tree picker you can specify a start node id. that should work for you.
A feature request for multi node tree picker has been to select a node from the current node but this would require XPath which is very expensive against non-published content.
sorry rich, i fixed the issue just before you pressed submit on your original comment and when i edited mine i realized that you had replied so i had to edit thanking you for the reply to the message that no longer appeared ... that makes sense right?
anyway this xpath textbox in the nodepicker. can i write currentnode in there and get it to work the way i want?
Sebastiaan Janssen, Both of those would be useable if I had a smaller sample size. Unfortunately due to the large number of pages on this site populating a list of items would be a bad idea. A content picker would be much more useful when it comes to giving the admins something to browse through. Otherwise I will have a listbox of some kind that extends for about 1000 lines
I think the Tribal package works with the umbraco.config file instead of hitting the database so it should be really very fast. Obviously it would then only work on published content, is that going to be a problem for you?
looking at the image examples of how it would look, the real problem is a user going in and understanding the original structure of the site. The pages on my site are in folders that basically make up some of the categories of their original site. Also the fact that there are 1000s of pages would mean that the list box on the left would be thousands of items long which wouldnt be very good for the user interface for them.
... ummm... let me screenshot one folder for you then you can see the length of things i am talking about here... don't blame me for the sheer length of how many pages are in one article folder, i didnt organize these things i just imported them begrudgingly (i warned them this would happen but no one listened).
So yeah, judging by the shortness of the scroll thumb, you can see that i am dealing with a lot of stuff here. that is only one of the completed folders which is why i wanted to use a treeview so that they could have everything minimized at first and slowly expand until they got to the section they wanted, only loading that content that is relevant to them at the time. And this is just one drilled down folder of one of the 3 sites i have on this install.
just covered up names of things for privacy's sake
Thought of one more type of component: Child Content Picker
Of course i thought of it while working on a new umbraco site. I have a site with a lot of nodes (i mean a lot of a lot of nodes) and it is split up between 3 seperate domains with different articles on each. In one spot I want to be able to select about 6 articles from the children of the current node but when i use the content picker it shows all nodes. when i use the ultimate picker it displays way too much at once (there are thousands of pages) since the display types you can choose are usually ones that will either load everything at once or have you guess at what the name of the page is.
So the idea i have is a content picker with the standard popup just like the regular content picker, but instead of showing all folders for the entire site, it only shows folders that are the children of the node you are currently on.
i dont know how hard or easy that would be to impliment because right now it was just an idea of mine.
With the axendo picker and tribal xpath node relations you can specify some xpath (and even the currentPage variable) to do just that!
On the multi node tree picker you can specify a start node id. that should work for you.
A feature request for multi node tree picker has been to select a node from the current node but this would require XPath which is very expensive against non-published content.
Agreed that it would be a fantastic feature to be able to specify the start node dynamically or via XPath/currentPage
Reason being is that my client can add / edit the nodes being picked out by MNTP so at build time I don't node the value of the start id.
Rich
Should add that MNTP rocks! as does all of the uComponents.
The other way I was trying to get around this was to dynamically add/edit data types but never found a way of doing so.
Rich
there is an xpath textbox in the nodepicker. can i write currentnode in there and get it to work that way?
nevermind the stuff that was written here... the reasoning for the problem was me being too tired to think rationally -_-
im good now, thanks for the reply
You have to create a new DataType then select type of uComponent you want.
Rich
Edit - this post now makes no sense as you edited your reply :)
sorry rich, i fixed the issue just before you pressed submit on your original comment and when i edited mine i realized that you had replied so i had to edit thanking you for the reply to the message that no longer appeared ... that makes sense right?
anyway this xpath textbox in the nodepicker. can i write currentnode in there and get it to work the way i want?
Sebastiaan Janssen, Both of those would be useable if I had a smaller sample size. Unfortunately due to the large number of pages on this site populating a list of items would be a bad idea. A content picker would be much more useful when it comes to giving the admins something to browse through. Otherwise I will have a listbox of some kind that extends for about 1000 lines
It would be better if it was in a treeview setup.
I think the Tribal package works with the umbraco.config file instead of hitting the database so it should be really very fast. Obviously it would then only work on published content, is that going to be a problem for you?
looking at the image examples of how it would look, the real problem is a user going in and understanding the original structure of the site. The pages on my site are in folders that basically make up some of the categories of their original site. Also the fact that there are 1000s of pages would mean that the list box on the left would be thousands of items long which wouldnt be very good for the user interface for them.
But with Xpath, you'd be able to filter that down to a few nodes.. right?
... ummm... let me screenshot one folder for you then you can see the length of things i am talking about here... don't blame me for the sheer length of how many pages are in one article folder, i didnt organize these things i just imported them begrudgingly (i warned them this would happen but no one listened).
So yeah, judging by the shortness of the scroll thumb, you can see that i am dealing with a lot of stuff here. that is only one of the completed folders which is why i wanted to use a treeview so that they could have everything minimized at first and slowly expand until they got to the section they wanted, only loading that content that is relevant to them at the time. And this is just one drilled down folder of one of the 3 sites i have on this install.
just covered up names of things for privacy's sake
is working on a reply...