Portal Engine Questions on portal engine and web parts.
Version 7.x > Portal Engine > Versioning for web parts View modes: 
User avatar
Member
Member
beau.cowan-rrpartners - 7/19/2013 12:36:57 PM
   
Versioning for web parts
I'm playing around with some of the features of the CMS and one of the most recent items I've been working with has been versioning.

I can go to a document and roll it back to a version that was done in the past, but I'm not seeing much of a change in this. I get that it is keeping information about the document iteself, but the web part options don't seem to be saving.

Most of the data for our pages is stored in our web parts. When I go to "View Version" after doing a change to the web part, I can see that the most recent change I did goes to all of the versions, so none of my data is being recorded in the version history.

I didn't know if there was a feature that I needed to turn on or if I was missing something when I was creating my web parts.

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 7/19/2013 5:35:13 PM
   
RE:Versioning for web parts
Looking at your post I'm a bit confused. Are you simply talking about updating a webpart on a page or updating the webpart itself in the Site Manager>Development>Webparts? I'll guess that you are updating just the page.

It is updating and saving the information. You may need to modify the settings for versioning in CMSSiteManager>Settings>Version & Synchronization>Object Versioning. In the Version History section, there are 4 values, the third one might be the one you are concerned with. Its Save to last version if younger than X minutes. You might update that to a lower value if you want to see immediate results and more version history. Otherwise all changes within that time frame will be stored in one version.

User avatar
Member
Member
beau.cowan-rrpartners - 7/23/2013 4:48:30 PM
   
RE:Versioning for web parts
I've been playing around with the suggestion that you gave, and I'm still not getting the results that I was hoping for. And since there is a bit of confusion, let me describe what we do a little better.

Instead of saving the data for a web page on the document object, we use webparts. So all blogs, contact info, or image being put onto the site through webparts. If we want to revert the page to a previous version, using old data, then rolling back the page is not working. Every version has the most current webpart associated with them.

Now, I tried using your suggestion in the SiteManager, but I was unable to produce any results. I set it all the way down to 0, and was still unable to get anything that I desired. After doing some research, it would seem that I would need to have a layout saved in order to use this feature, which I also tried, but was also unsuccessful.

If there are any other ideas, please let me know.

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 7/24/2013 6:41:03 AM
   
RE:Versioning for web parts
Let me clarify a bit.

The webpart in CMSSiteManager>Development>Webparts is the base object you are using instances of on page templates. This is where you set the definition of the webpart (name, location in file system, description, properties, etc.). This is versioned as an object.

The webpart you place on a page template in the CMSDesk is an instance (or snapshot at that time) of the definition of the webpart you have defined in the CMSSiteManager. This is the definition of a page template and gives how you an idea of how it all works together.

If you make a change to the webpart properties on a page, you will see in content staging in the CMSDesk that you will have a task that states Update page template "template name". When you go to CMSSiteManager>Development>Page templates, you will see in the versions tab that there is also a new version.

If you make a change to the content say in the editable text webpart, that is stored in the document itself and IS versioned in the (PageName)>Properties>Versions under the column DocumentContent.

I'm not sure what webparts you are using to display your content but a webparts properties are all saved to a page template and NOT a document. There are only a few unique webparts that store their content to a document for instance the Editable Text and Editable Image webparts. Whatever is entered/saved in the documents "Edit" tab will be saved with the document. Whatever is entered/saved in the documents "Design" tab is saved with the page template.

Hope I didn't confuse you more.