1

Closed

CommonPart should not always contain an owner and we should be able to manage content without ContentPart ?

description

When we add CommonPart to a ContentType, it automatically adds creation/modification dates and an owner.
But sometimes, we don't need an owner, or let's say that the system, or the websiter or the company is the owne.

I tried removing CommonPart, but the corresponding contents are no more manage in the content manager of the admin menu ????

The turn-around is to create a 'system owner', but it is not a good practice and will present some problem sooner or later.

Ideally we should be able to:
  • manage content without commonPart
  • separate CommonPart in CommonDatePart and CommonOwnerPart
....for futur release ?
Closed Mar 26, 2013 at 9:01 PM by sebastienros
By design in Orchard. We rely on that bug.

comments

BertrandLeRoy wrote Feb 21, 2013 at 2:11 AM

Why? Why do you care that there is an owner, particularly as the editor for it can be hidden?

There is no way we are removing common part.

CSADNT wrote Feb 21, 2013 at 7:08 AM

Let's suppose you want to give data visibility according the owner or role criteria.
For all the system content, useful content (a currency in an e-commerce package for example), everybody should have direct and faster access to it, without authorisation control overlay...

BertrandLeRoy wrote Feb 22, 2013 at 6:34 AM

I don't understand. How does removing Common give "direct and faster" access? What authorization control overlay?

CSADNT wrote Mar 27, 2013 at 12:03 AM

Ok, will live with it.

CSADNT wrote Mar 27, 2013 at 11:52 PM

Just realized there was a typo in my title

CommonPart should not always contain an owner and we should be able to manage content without CommonPart ?