Re: Extending a plugin content type

I think, yes. System was always meant for things that did not originate in
the project, but its purely a preference thing. This practice is not
enforced in any way. Many developers just like to have all their types in
one place, ie. types

GB

On Monday, December 17, 2012, Jørgen Skogås wrote:

> When extending core types best practice is to use the
> projectFolder/packages/system folder. Should the system folder be used when
> extending plugin content types also?
>
> --
> You received this message cos you are subscribed to "farcry-dev" Google
> group.
> To post, email: farcry-dev-/[email protected] <javascript:_e({}, 'cvml',
> 'farcry-dev-/[email protected]');>
> To unsubscribe, email: farcry-dev+unsubscribe-/[email protected]<javascript:_e({}, 'cvml', 'farcry-dev%2Bunsubscribe-/[email protected]');>
> For more options: http://groups.google.com/group/farcry-dev
> --------------------------------
> Follow us on Twitter: http://twitter.com/farcry
>
>
>

-- 
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: farcry-dev-/[email protected]
To unsubscribe, email: farcry-dev+unsubscribe-/[email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry