Hi. We're currently trying to figure out if Umbraco could be a solution for the client that we have.
For this client, we're creating a member driven content site. It's an informational site consisting of many organizaitons and events. Each Member can either create or update a single organization that they are a part of. (many to one relationship....each organization can have many members, but a member can only be a part of one organization). All changes to an organizations information will need to go through workflow and be approved by an administrator.
Members can also create events for the organization. They can add/edit/delete events. Events will then go through workflow.
On the front end, users will be clicking through different categories and viewing the organizations/events that are displayed as part of that category. An organization can be in many categories.
This would be off a clean install of Umbraco (so unless 4.1 comes out soon...it'll use 4.0.4.1)
Are the "members" of the organization updating the information using the umbraco back-end or through protected areas on the front end? In umbraco terms are they "members" or "users"? If they are users, you can use the normal permissions and start node model to give them access. If they are more "members" you would need write a bit more custom code to get things done....but it can be done.
Umbraco can certainly do the job, though you'll have some fun custom bits to implement. I'd definitely use members with a login to let them manage their information.
You'll want to become familiar with the relationship api (see umbraco.tv episodes... excellent!), which will resolve a lot of what you're thinking about. And /base will be invaluable I think for handling a lot of this (again, the the great umbraco.tv episodes for /base).
The workflow is probably the most challenging feature, depending on how complex it is. Event handlers are probably the key here though someone may have a better solution if you let us know what kind of system you're thinking of. You might even be able to use the membership provider and handle escalation through a custom membership provider (active directory or sql server, for instance).
In many respects, the codegarden10.com site is an example of the kind of thing you want to do unless I misunderstand you.
This site uses quite a complex setup but we let users manage their profiles etc via Umbraco but also uses a SOAP/REST interface to update profiles on our community site too.
As Doug has suggested /base is very handy in getting Ajax stuffs to work although if you're using <=4.0.3 you can get access to the membership API so just be weary of that.
If you want to ask any questions about what we've done or how we've done it on Central Station give me a shout and I'll try to help out.
Creating an advanced member area
Hi. We're currently trying to figure out if Umbraco could be a solution for the client that we have.
For this client, we're creating a member driven content site. It's an informational site consisting of many organizaitons and events. Each Member can either create or update a single organization that they are a part of. (many to one relationship....each organization can have many members, but a member can only be a part of one organization). All changes to an organizations information will need to go through workflow and be approved by an administrator.
Members can also create events for the organization. They can add/edit/delete events. Events will then go through workflow.
On the front end, users will be clicking through different categories and viewing the organizations/events that are displayed as part of that category. An organization can be in many categories.
This would be off a clean install of Umbraco (so unless 4.1 comes out soon...it'll use 4.0.4.1)
Thanks,
C
Are the "members" of the organization updating the information using the umbraco back-end or through protected areas on the front end? In umbraco terms are they "members" or "users"? If they are users, you can use the normal permissions and start node model to give them access. If they are more "members" you would need write a bit more custom code to get things done....but it can be done.
-Chris
At this point, I hadn't decided which to do. I assumed that they would be members using a protected area on the front end.
Thanks,
Chad
Hi, Chad,
Umbraco can certainly do the job, though you'll have some fun custom bits to implement. I'd definitely use members with a login to let them manage their information.
You'll want to become familiar with the relationship api (see umbraco.tv episodes... excellent!), which will resolve a lot of what you're thinking about. And /base will be invaluable I think for handling a lot of this (again, the the great umbraco.tv episodes for /base).
The workflow is probably the most challenging feature, depending on how complex it is. Event handlers are probably the key here though someone may have a better solution if you let us know what kind of system you're thinking of. You might even be able to use the membership provider and handle escalation through a custom membership provider (active directory or sql server, for instance).
In many respects, the codegarden10.com site is an example of the kind of thing you want to do unless I misunderstand you.
cheers,
doug.
Hi Chad
We've implemented some of what you've detailed in http://www.thisiscentralstation.com/
This site uses quite a complex setup but we let users manage their profiles etc via Umbraco but also uses a SOAP/REST interface to update profiles on our community site too.
As Doug has suggested /base is very handy in getting Ajax stuffs to work although if you're using <=4.0.3 you can get access to the membership API so just be weary of that.
If you want to ask any questions about what we've done or how we've done it on Central Station give me a shout and I'll try to help out.
Jon
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.