Linking properties to members and editing front and back office
Hi, new to umbraco and considering using it for a new project. The major part of this is allowing members to create properties on the front end which can then be approved or verified by an admin user in the back office.
I've had a play about and can create a relationship and/or use the member picker to manage the one to many relationship. I can use a content app for the member type to display all owned properties for a member and open an editor for that property from the member view.
However I really don't want the preview (can use EditorModel Events to remove this), publish or scheduled features. I really need to control the visibility front end via my custom status and showing these extra buttons will confuse back office users. I'm not sure if I can shoehorn the publish feature to work especially as the properties will be editable front and back end concurrently.
Am I trying to force this, will it work, is there a better way?
Linking properties to members and editing front and back office
Hi, new to umbraco and considering using it for a new project. The major part of this is allowing members to create properties on the front end which can then be approved or verified by an admin user in the back office.
I've had a play about and can create a relationship and/or use the member picker to manage the one to many relationship. I can use a content app for the member type to display all owned properties for a member and open an editor for that property from the member view.
However I really don't want the preview (can use EditorModel Events to remove this), publish or scheduled features. I really need to control the visibility front end via my custom status and showing these extra buttons will confuse back office users. I'm not sure if I can shoehorn the publish feature to work especially as the properties will be editable front and back end concurrently.
Am I trying to force this, will it work, is there a better way?
Thanks for your help
George
is working on a reply...