|
Wednesday 21 April 2004 4:05:10 am
Hi, We are in the process of developing an extranet application.
In principle there are 2 approaches:
1. the user contributes items, and has the option to edit items he/she contributed.
2. the user contributes items which then become property of the extranet community and can no longer be edited by the individual who contributed the item
We prefer the first approach but run into a number of problems:
1. Once a version has gone through a workflow system past the approval of an editor, is the version still owned by the person who originally contributed it? If not, we can not give an overview of all items contributed by a user...
2. We want to make sure the user who contributes an item through the frontend is not faced with the full functionality of the system in terms of versioning etc.
However, the full versioning functionality should remain available to the editor of the site. In other words: we want to be able to disable versioning for certain usergroups. Users of particular groups should not edit a copy of the live version, but the live version itself. Does anyone know if this is this possible? 3. We want to display a list of objects per user per status (published), a modified version of object_count_by_user_id (http://ez.no/ez_publish/documentation/reference/data_fetching/content). In this way we could at least give the user some feedback about what he/she published. Has anyone done this before? Thanks for your time,
Regards,
Sebastiaan
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.
|
