×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Content History
Ioannis
Nouveau membre
Posts: 10
il y a 10 ans 6 mois #33
par Ioannis
Content History a été créé par 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
Connexion ou Créer un compte pour participer à la conversation.
Andres Maeso
Membre platinium
Posts: 338
il y a 10 ans 6 mois #37
par Andres Maeso
Andrés Maeso
Customer relations manager at Joomla Component Creator.
Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
Réponse de Andres Maeso sur le sujet Content History
Hello Ioannis
I've made a quick search and looks like implementing version control to components will be a big task. Even K2 or easyblog haven't implemented it yet. We will keep researching how to do it, but we can't really estimate a date.
We are always on the lookout for Joomla updates, but please, feel free to provide with any information on version control for third part components you may find.
I've made a quick search and looks like implementing version control to components will be a big task. Even K2 or easyblog haven't implemented it yet. We will keep researching how to do it, but we can't really estimate a date.
We are always on the lookout for Joomla updates, but please, feel free to provide with any information on version control for third part components you may find.
Andrés Maeso
Customer relations manager at Joomla Component Creator.
Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
Connexion ou Créer un compte pour participer à la conversation.
Ioannis
Nouveau membre
Posts: 10
il y a 10 ans 6 mois - il y a 10 ans 6 mois #38
par Ioannis
Réponse de Ioannis sur le sujet 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
Dernière édition: il y a 10 ans 6 mois par Ioannis.
Connexion ou Créer un compte pour participer à la conversation.
Ioannis
Nouveau membre
Posts: 10
il y a 10 ans 6 mois #39
par Ioannis
Réponse de Ioannis sur le sujet 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)
Connexion ou Créer un compte pour participer à la conversation.
Andres Maeso
Membre platinium
Posts: 338
il y a 10 ans 6 mois #40
par Andres Maeso
Andrés Maeso
Customer relations manager at Joomla Component Creator.
Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
Réponse de Andres Maeso sur le sujet Content History
Thanks Ioannis! It's definitively a feature we would love to have. We will think about the best way of doing it.
More requests will help to rush it!
More requests will help to rush it!
Andrés Maeso
Customer relations manager at Joomla Component Creator.
Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
Connexion ou Créer un compte pour participer à la conversation.
Randy Carey
Membre junior
Posts: 23
il y a 9 ans 11 mois #532
par Randy Carey
Réponse de Randy Carey sur le sujet 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.
Connexion ou Créer un compte pour participer à la conversation.
Temps de génération de la page : 0.059 secondes