Administrating directories, sites, users and rights
Hi. Quite confusing topic for a quite confusing question.
I haven't started using umbraco yet, just thought i would ask this first. Before fiddeling too much in vain.
I am planning on having a site for contact information, documents, statistics etc (connected to our systems in the back) for several users, each user seeing and handling different content.
I am thinking of having each users "site" in a subdirectory to the main site, lets say www.site.com/user1/ and www.site.com/user2/. Where each users site contais a couple of tabs and pages for it's statistics and whatever info. Of course user2 should not be able to acces /user1/* etc. And from the main site is only a login-prompt redirecting users to their respecive directory when logging in.
Of course I would like (my super duper Admin-account) to administrate this from only one instance of umbraco, needing only one place to go to, to add/remove/chage content, styles or whatever, for_every_ users "site".
Does this look feasible? Does it seem logical at all?
Wow, I can hardly understand my own post... am I making some kind of sense? Hope you guys can give some response or ideas :)
Honestly, I've done something similar in a sense that I've been building a site where each registrar got his 'own' pages to publish projects and personal info. It can be done quite easily using standard asp.net controls (for handling the registration process) and the umbraco api (for creating the node tree structure - for example, creating a home directory for each new registrar)
I'm not sure if umbraco is the perfect for this kind of apps (Remember, umbraco is a cms system and not really a community site per se), but it sure can be done. In fact, I've already done something similar. Feel free to ask more questions if you'd like to go on.
Yes, i want the registrars to have their own pages and to only be able to view their own pages, somewhat like a community, but very limited for the user (more static pages). The administration of the site should basically only be available to me. The users should not be able to manage their pages. I'm a bit worried about the user management though, maybe umbracos users-part is basically meant for the admin-controlpanel-part of umbraco itself, and not for using/browsing the site?
Also i'm planning on having lots of interaction towards our own .net-based systems, e.g. our bug tracking system and statistics, so the users will not be posting stuff on umbraco-based pages, but rather in our system - integrated in the site. From what i see, umbraco will be exstensible enough to allow me to create my own .net methods to interact with our systems, most of them using SOAP etc.
I'm looking at umbraco because of the fact that it is built on .net, and I need a central place for managing the look and content of the site.
Administrating directories, sites, users and rights
Hi. Quite confusing topic for a quite confusing question.
I haven't started using umbraco yet, just thought i would ask this first. Before fiddeling too much in vain.
I am planning on having a site for contact information, documents, statistics etc (connected to our systems in the back) for several users, each user seeing and handling different content.
I am thinking of having each users "site" in a subdirectory to the main site, lets say www.site.com/user1/ and www.site.com/user2/. Where each users site contais a couple of tabs and pages for it's statistics and whatever info. Of course user2 should not be able to acces /user1/* etc.
And from the main site is only a login-prompt redirecting users to their respecive directory when logging in.
Of course I would like (my super duper Admin-account) to administrate this from only one instance of umbraco, needing only one place to go to, to add/remove/chage content, styles or whatever, for_every_ users "site".
Does this look feasible? Does it seem logical at all?
Wow, I can hardly understand my own post... am I making some kind of sense? Hope you guys can give some response or ideas :)
Hi,
Honestly, I've done something similar in a sense that I've been building a site where each registrar got his 'own' pages to publish projects and personal info. It can be done quite easily using standard asp.net controls (for handling the registration process) and the umbraco api (for creating the node tree structure - for example, creating a home directory for each new registrar)
I'm not sure if umbraco is the perfect for this kind of apps (Remember, umbraco is a cms system and not really a community site per se), but it sure can be done. In fact, I've already done something similar. Feel free to ask more questions if you'd like to go on.
Cheers,
/Dirk
Thanks for the fast reply.
Yes, i want the registrars to have their own pages and to only be able to view their own pages, somewhat like a community, but very limited for the user (more static pages). The administration of the site should basically only be available to me. The users should not be able to manage their pages. I'm a bit worried about the user management though, maybe umbracos users-part is basically meant for the admin-controlpanel-part of umbraco itself, and not for using/browsing the site?
Also i'm planning on having lots of interaction towards our own .net-based systems, e.g. our bug tracking system and statistics, so the users will not be posting stuff on umbraco-based pages, but rather in our system - integrated in the site. From what i see, umbraco will be exstensible enough to allow me to create my own .net methods to interact with our systems, most of them using SOAP etc.
I'm looking at umbraco because of the fact that it is built on .net, and I need a central place for managing the look and content of the site.
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.