Add Simple Version Content Management to Joomla ! When a content is updated in frontend, a backup version is saved. You can restore this version with the component. Simple and Easy !!!
New Version 1.0.3:
-*-*-*-*-*-*-*-*-
- Replace all
Report this listing
| How do you guys make it work at Joomla! 1.x by lanfong, April 23, 2008 |
|
1 of 1 people find this review helpful:
Hi guys
After reading the comments, there's seems no real solution for me to get the extension running properly.
I saw that I have to download com_xx.zip and bot_xx.zip and install component first and then mambot. When I installed both, I can see that my db has a table called "content_back".
However, when I edit a page, it didn't store to the db. at the backend admin control panel, I am able to see the versions of each article, but I can't go back to previous version since it's not storeing to the database. Anyone has any idea???
|
| Very useful bot by daprakas, March 21, 2008 |
|
Very useful.. I am running this with the pacth of mysql backup.. Works without any issue.....
|
| vital function...too bad it's not being supported by Pixelate, March 20, 2008 |
|
1 of 1 people find this review helpful:
A vital idea, which for some unknown reason is not a core feature in Joomla!
Every client I have that uses Joomla! I have to tell them to copy the text in the WYSIWYG text box to a text file just in case they mess up the text.
Unfortunately, we are now fully into Joomla! 1.5 and this feature still isn't in Joomla! and this plugin hasn't been updated in over a year.
Great idea...too bad it is a dead project.
|
| Must have for any CMS by Gunner10, January 21, 2008 |
|
1 of 1 people find this review helpful:
I don't understand how any CMS can go without some kind of version control, and though I've only just installed this extension, it already seems to fulfil this vital requirement.
Just want to quote this other review though again:
Just a tip for the developer: I substituted the line 37 or so in the mambot with this line:
if (($option == 'com_content') && (($task == 'save')||($task == 'apply_new')))
... just because it should include the apply_new task as many users edit content in this way and could bypass versioning and block the content.
I've done that, as otherwise you don't get versions created when users click "apply".
|
| Very Needed by edgecast, November 28, 2007 |
|
1 of 1 people find this review helpful:
Lest I appear ungrateful I must say this is a great component. One feature that would make it even better would be the ability to link to a particular version. Say user one agreed to terms version 1 and user two agreed to terms version 2. It would be nice if I could provide the respective links.
Great work!
|
| how can we have a community site without version control? by pedropablo, September 5, 2007 |
|
1 of 1 people find this review helpful:
Just because this is the only free product to implement a so critical feature, it deserves the 5 stars.
The latests beta test version is really cool:
simple and clean to install, you don't have to worry about installing the component and the module
stores every previous version of content
works as if it wasn't there
Great work!! This is the extension you need if you plan to allow your users to modify content from the frontend. With this and a very simple acl tweak to joomla, you can convert you joomla content in an actual wiki (and joomla lacks of a good one, by the way), which is perfect for a community site
Just a tip for the developer: I substituted the line 37 or so in the mambot with this line:
if (($option == 'com_content') && (($task == 'save')||($task == 'apply_new')))
... just because it should include the apply_new task as many users edit content in this way and could bypass versioning and block the content.
|
| New version on Joomlacode by ccrosaz, May 4, 2007 |
|
1 of 1 people find this review helpful:
A new version of the component (and his bot) is available on the new Joomla forge (http://joomlacode.org/gf) for testing.
Please try it and report any bug or trouble.
With Thomas PAPIN, we try to find a solution for back-end backups, but actually it is simply not possible.
You can propose change or evolution on the forge or on the French developers club Joomlagora.org
|
| Great extension, but a bit more "how to" please? by jamskee, April 7, 2007 |
|
This seems to be exactly what I have been looking for after i discovered articles went missing when i tried to save in joomla... so thank you to the developer!
NB: Yes you do need to install the component 1st and then the bot which i used version 1.02 from the developers website...
@ supercmo
Can you please explain your patch in a bit more detail as i dont seem to follow what i need to add/replace and also which files need updating, as you specify 2 files in the middle of your instructions but one doesnt have any info under it...
Any help to get this working for me will be greatly appreciated.
Cheers
|
| Far better than nothing by ekorn, March 3, 2007 |
|
1 of 1 people find this review helpful:
A simple component that can save the day when either the editor (me) or the editor (plugin) screws up. Version 1.0.3 no longer requires the "short open tags" PHP directive.
|
| Agree with Scoot by hangbill, February 3, 2007 |
|
My experience is same as Scoot's; only the last change is saved. Wrote to author but no reply. Does not work on my setup.
|
| Great - almost perfect by vince, February 1, 2007 |
|
Well done! At last someone has realised this was a real need for any CMS
Just beware, if you do roll-back to a previous version, it does delete the newer versions. :-(
Maybe the next update of this add-on will take care of this?
|
| A component and bot must be installed by merka, December 25, 2006 |
|
1 of 1 people find this review helpful:
This is a very usefull extensions but needs some documentation and/or installing instructions. The latest version 1.0.3 when downloaded provides file com_versioning_v1.0.3.zip. If you install this as a component, the administration backend will display number of previous versions for documents but will NOT show nor store any previous version. I have almost given up but then I noticed that the previous version downloads file pack_versioning_v1.0.2.zip. And behold, this package holds com_versioning_v1.0.2.zip and bot_versioning_v1.0.2.zip - so you need also install a mambot!
I have installed bot_versioning_v1.0.2.zip and com_versioning_v1.0.3.zip together and the versioning finally works.
|
| Great Start by youtzyd, December 17, 2006 |
|
I thought this component was a great start to a revision control system. With a few modifications this has changed my mind for content management in favor of Joomla!. I don't, however understand the review about adding the ability to save a revision when editing content from the backend. I think it's a great idea, but what do the numbers mean above the lines of code??
|
| Works for me by sharon98, December 15, 2006 |
|
Maybe the next version of Joomla will have something more robust for versioning, but this component is enough to give my users some peace of mind that they can recover previous versions of their content.
|
| Not working by scoot, December 6, 2006 |
|
1 of 1 people find this review helpful:
There's no documentation provided on how to use this component/bot.
The only access appears to me to be in the backend, where the component provides a list of content items. I've run several tests to change content items, using both the front end and the back end editor,and each time Versioning reports the last edit as the original, and shows no backups!
|
<< Start < Prev 1 2 Next > End >>
Results 1 - 15 of 21
|