I still think you try to do wrong stuff with the #__content table. You should not store items from 3rd party extensions in that table if it's not supposed to show up in the article manager (and in frontend).
You should instead use your own tables and models to do that.

ContentModelArticles as well as the #__content is a class from the component com_content. It's not meant to be useable by other extensions for their own stuff.

Not sure how I feel about this one. On the one hand, yes it makes com_content extendable, but on the other hand, none of our existing components really fit into a UCM or CCK style model today and this one patch wouldn't really make a big difference in the long run.

As @Bakual said, each component should not be using another component's tables to store their data in, and I'll caveat that with saying that it should only happen if the table is clearly defined for shared use (things like our extensions table or the UCM tables being examples). As com_content is a really concrete implementation, it isn't suitable for this purpose IMO.

I agree with @Bakual also. It seems that you are trying to use #__content table (an extension table) instead of using #__ucm_content table that can be used an extended because it's part of the libraries/base system.

If we remove com_content from core your extension would be broken. I'm against allowing users to do this because it adds dependencies where we shouldn't and it's promoting bad coding practices. A step in the wrong direction.

So here

Hi guys,

Thanks for your input. I understand your points but if the categories table was designed for multiple extension use then why have categories without items? I understand and originally looked into the UCM tables when designing the extension but from my research concluded (as did others) that it is too early to use these tables yet as they are still undergoing heavy development and haven't settled down yet.

Joomla usually give fair notice when depreciating tables & classes so I'm fully prepared to move the extension's data across to the UCM tables once their design pattern has settled down.

Regards,

Paul

As said, com_categories is designed to be used by components. It does nothing on its own. It's a service component.

com_content on the other hand is a regular component, not meant to be reused by other components.

What you should do is create your own database tables and models for your extension. Not try to use existing ones from other components.

I'm closing this PR as already three members of PLT voted against it.
Thanks anyway for your contribution and time!