Alex, Orchard Modules are not necessarily "Content Types" or "Content Parts". You can create a new "Content Part" or "Content Type" module for Orchard, for example a DateTime Field part or a Navigation content type but they are not always "Types" or "Parts".
The only out of the box way I could think of doing this quickly would be create a new "Role" from the Users tab that just allows this role to edit content types. This would then not allow these users to do anything else but edit/add content types. You would need to overwrite the Orchard Core code base to add permissions to the content types and parts as it is not out of the box functionality. You could probably add some override view files in your theme as well to check permissions on rendering as well. I am pretty new to Orchard but thought I could try and help :) Arra On Sat, Apr 30, 2011 at 11:27 AM, Alex Loret de Mola <[email protected]>wrote: > Hey Guys, > > Okay, so we're over here at Give Camp New England, working with a nonprofit > called Project Warehouse, who's looking to basically provide a site that > lets users: > > * Create pages for their humanitarian efforts > * Let people search for said efforts by various mechanisms > * "Follow" humanitarian efforts that have been posted by other users > > And other features that (to me) somewhat resemble Facebook Groups. > > The idea was brought up to try Orchard, and we've been giving it a go but > we've been running into resistance: > > * Modules appear to have the end goal of creating "Content Parts" and > "Content Types", but it looks like Content Types end up being creatable only > through the Admin interface... which isn't useful if regular users of the > site need to create these content types. > > * We need these content types to be "owned" by the users who create them... > if I was wiring this up in straight-up MVC I would know exactly what to do, > but trying to do it through the best practices of Orchard I'm at a loss. I > don't see any documentation anywhere for an API to existing entities (such > as user information)... I imagine I could manually wire up relationships > between them theoretically, but I'm not quite sure how to do that without > fundamentally breaking Orchard (and essentially "rolling my own" > implementation and persistence mechanisms that happen to be sitting in the > same URL path as Orchard and manually querying for data from Orchard's > tables to make the relationships), but that feels like a terrible hack. > > So what is the "best practice" for this notion of regular (non-Admin) users > being able to create this data? I appreciate any input you can provide, > thanks! > > -Alex > --- You are currently subscribed to orchard-discuss as: > [email protected]. To unsubscribe send a blank email to > [email protected]. -- Arra J. Derderian President / Engineer Cloud Construct, LLC 617-201-6138 www.cloudconstruct.com --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected].
