25 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Stefan | dpdk commented  ·  December 15, 2010 5:20 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @CraZy675; About the Core component com_content; They will recieve all my votes if they would completely refactor the whole - outdated - component and data structure!

  First, look what's in the name com_CONTENT; With such a name for a Core component, it should provide THE uniform solution of data storage in Joomla! Not only for it's own basic content (Types), but for all component who need to store "sets of data".

  No matter what type of data it would be. In it's Basic form, it should always be simplified to a content-item (just like a Node in Drupal).

  Com_content in it's current form is 100% static data input. In a way, com_content is just the same like all the other - non CCK like - component, who are storing their own sets of data within their self sufficient data structures.

  Back to the subject; Besides all the data-input variations in which this com_content component can be extended with. The functionality of Content Versioning would be a different extension of the com_content component than it's content-elements.

  In a way it will be a relational copy of the same com_content storage-table. Having only a relational band with the basic com_content item, it can rely on the same resources (content-elements) of the "Primairy" content-item.

  (Looking at this, the extension of com_content with the ability of "Translations" would be of the same setup as versioning. Based only on relationship, and not the complete copy of the data structure.)

• CraZy675 commented  ·  December 15, 2010 4:32 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Yes! com_content is part of the core. This must be included with com_content and not a third party. 99% of these other requests can (and already have) been solved by third parties.

  I'd like to encourage everyone to vote for this feature.

  I also recall a google summer of code project about this as well as a few blog postings around the net.

• Stefan | dpdk commented  ·  December 6, 2010 12:35 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  With such a functionality to be added/turned on to sertain part of the content, it would the first real Native Joomla! Wiki attempt in history.

  For now - when clients asked for a Wiki - you just wouldn't do that within Joomla!, you would probably go for an external solution.

• Hidabe commented  ·  November 29, 2010 2:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I remember one Google Summer Code Project about it... in progress, where is it?

• k0nan commented  ·  November 27, 2010 3:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  having a content update history - like last saved at, last edited by, published at, unpubslihed by - would be better. than for sure someone could extend this functionality with content versioning and content revisioning