×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Content History
Ioannis
New Member
Posts: 10
10 år 7 måneder siden #33
af Ioannis
Content History blev oprettet af Ioannis
Hello,
I wonder if you have any plans to include the content history (introduced in J3.2) feature and if yes, can you define a date?
Thanks in advance
I wonder if you have any plans to include the content history (introduced in J3.2) feature and if yes, can you define a date?
Thanks in advance
Venligst Log på eller Opret en konto for at deltage i samtalen
Ioannis
New Member
Posts: 10
10 år 7 måneder siden - 10 år 7 måneder siden #38
af Ioannis
Besvaret af Ioannis på emne Content History
Hi Andres,
I don't think it's that hard.
Take a look at this: docs.joomla.org/Using_Content_History_in_your_Component
You have to "loop" through the tables and create the sql statement so as to insert new record(s) to #__content_types table. That's it. The rest are taking care by Joomla.
The best example of content history usage is of course "com_content". K2 or easyblog or other well known components cannot adapt so quick to new changes (I can understand that) so they cannot be taken as "best practice".
Also, I know that is hard for you to incorporate every new Joomla feature, so consider my thoughts only as suggestion for future work. Component Creator is already #1.
Keep up the good work.
Best
--Ioannis
I don't think it's that hard.
Take a look at this: docs.joomla.org/Using_Content_History_in_your_Component
You have to "loop" through the tables and create the sql statement so as to insert new record(s) to #__content_types table. That's it. The rest are taking care by Joomla.
The best example of content history usage is of course "com_content". K2 or easyblog or other well known components cannot adapt so quick to new changes (I can understand that) so they cannot be taken as "best practice".
Also, I know that is hard for you to incorporate every new Joomla feature, so consider my thoughts only as suggestion for future work. Component Creator is already #1.
Keep up the good work.
Best
--Ioannis
Sidste redigering: 10 år 7 måneder siden ved Ioannis.
Venligst Log på eller Opret en konto for at deltage i samtalen
Ioannis
New Member
Posts: 10
10 år 7 måneder siden #39
af Ioannis
Besvaret af Ioannis på emne Content History
To conclude my thoughts...
I wouldn't expect for example to support (at this stage) the new MVC (like e.g. com_config does)
I wouldn't expect for example to support (at this stage) the new MVC (like e.g. com_config does)
Venligst Log på eller Opret en konto for at deltage i samtalen
Randy Carey
Junior Member
Posts: 23
10 år 4 dage siden #532
af Randy Carey
Besvaret af Randy Carey på emne Content History
I want to cast my vote for content history. I think most clients have some expectation that they can revert back to previous settings/content, and I want to meet those reasonable expectations.
Using the same documentation that was referenced, I have integrated this feature into a component generated here. I think it took me less than an hour my first time around (to test and get it right), so when I feel content history is important for the client, I will add it. But there are several little repetitive details for one to do this manually - most which I wish I could have automated. The main thing that I would want to declare is which fields should be maintained as history and how many versions to keep. To be realistic, I do see that adding more complexity to the interface for Component Creator, so perhaps those details are hidden unless we toggle on that we want content history.
I do realize that this is not a simple feature to add. But I also feel it is an important capability that Joomla has recently offered.
Using the same documentation that was referenced, I have integrated this feature into a component generated here. I think it took me less than an hour my first time around (to test and get it right), so when I feel content history is important for the client, I will add it. But there are several little repetitive details for one to do this manually - most which I wish I could have automated. The main thing that I would want to declare is which fields should be maintained as history and how many versions to keep. To be realistic, I do see that adding more complexity to the interface for Component Creator, so perhaps those details are hidden unless we toggle on that we want content history.
I do realize that this is not a simple feature to add. But I also feel it is an important capability that Joomla has recently offered.
Venligst Log på eller Opret en konto for at deltage i samtalen
Tid til at oprette siden: 0.051 sekunder