17

Sitecore doesn't expose the version manager [you've shown] on templates. However, you can use the DB Browser (~/sitecore/admin/dbbrowser.aspx) and manage items, templates, etc. that way. Simply point your browser to http://instance/sitecore/admin/dbbrowser.aspx: Then navigate to the template you're looking to modify and select the version you're after and ...


11

I found some code from John West some time back and made that into a module on Github. You could take the below snippet I converted to PowerShell and make it a report. # Create a list of field names on the Standard Template. This will help us filter out extraneous fields. $standardTemplate = Get-Item -Path "master:" -ID "{1930BBEB-7805-471A-A3BE-...


10

There was a bug in earlier Sitecore 8.2, fixed in 8.2 Update 5 (rev. 170728) A deleted language version of an item in the master database exists in the web database after publishing.​ ​Smart Publishing does not unpublish invalid item versions.​ See the information in the release notes: https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/82/...


7

Make sure to check "publish subitems" when publishing parent folder. To verify if the item was removed from the web database, switch to web database from Sitecore Desktop and see if your page is there. Open .../sitecore/shell/ in the browser and on the bottom right corner of the screen there is a button to switch database. Switch back to master database ...


7

If you use Sitecore PowerShell Extensions you can make this process faster by wrapping it in an EventDisabler SPE has a Remove-ItemVersion cmdlet that lets you select the language(s) versions and also the max number of recent versions to keep. This means you don't need to archive and restore the needed versions. This code assumes v4+ of SPE: New-...


7

While this is technically possible (by hooking into the publish:end event), I think this might have some unexpected implications. Let me run you through a couple of examples. With workflow disabled: Let's say I have the Home item on version 1. I publish it, and hook into the publish:end event. This will now create version 2. I'm not going to change ...


6

Media items are created as Unversioned by default. Make sure that you have created a media item that uses the Versioned media template, e.g. /sitecore/templates/System/Media/Versioned/File. When you upload the file, select the "Upload Files (Advanced)" option: And then select the "Make uploaded media items versionable" option: There is also config setting ...


6

Another way to do this is using Sitecore Powershell Extenstions. There is a cmdlet called Remove-ItemLanguage, this removes the specified language version from the item. Example that removes the German version of a template: Get-Item master:\templates\User Defined\MyTemplate | Remove-ItemLanguage -Language de-de You could create a script that would load ...


4

When you upload a new picture you need to fill checkbox : Make media library versionable : More details you can find here: https://doc.sitecore.net/sitecore_experience_platform/content_authoring/media_items/using_media_items/upload_a_file_to_the_media_library


4

Consider retrieving the list of candidates for removal, comparing with the web database, then remove. This SSE answer provides a sample script at comparing version between master and web and showing as a report. When it comes to publishing, only the latest publishable version will be in the web database, not all 10. A possible script workflow could be the ...


3

From what I recall, you need a few things in place: Non-admin users (admins will bypass workflow) Two-step workflow (draft & final) that automatically approves on the save. This is the OOTB 'new version on save' approach. Versioned media. You can't version with unversioned media. However, a warning on auto-versioning. If you get a lot of edits this is ...


3

Yes you can Tagging is a field that is stored as __Semantics and it is not shared between item versions. I ran a quick test. Version 2, untagged. Version 1, tagged And searching for this tag Returns only Version 1, as expected. And final proof I tagged both versions. Further reading: Content Tagging with Sitecore 7


3

Express migration tool does not migrate your old archived items, So your option here is to manually move these data in SQL tables, You can check this answer here where they used SQL queries to migrate the archived items, You use the same approach, There are no breaking changes in the tables schema, but make sure you try this first in a non-production ...


3

To add on @Chris Auer answer, you may find below the code snippet showing where you should perform the change. You need to override the OnLoad method of the GalleryVersionsForm class from the namespace Sitecore.Shell.Applications.ContentManager.Galleries.Versions in the assembly Sitecore.Client.dll. public class GalleryVersionsExtensionForm : ...


3

It's completely different in Experience Editor. When you click on any of the versions, there is a request to /-/speak/v1/ExperienceEditor/SelectVersion.js It builds an url for selected version, checks if the item has presentation details and finally it calls code similar to: var url = ExperienceEditor.Web.setQueryStringValue(ExperienceEditor....


2

So the problem was in the .EndEdit() call. By calling .EndEdit(false, true) you are essentially telling Sitecore two things: Do not update revision, revision date and so on. In other words, try and "hide" that the update took place Disable events for this update So basically you did pretty much everything you could, to try and hide the fact that you were ...


2

Sitecore supports to use Unversioned and Versioned templates for Media Items. All these templates you can find /sitecore/templates/System/Media Versioning for Media items the same as a standard items versioning. You can easily to set Publishing Restrictions and use your Media item. <setting name="Media.UploadAsVersionableByDefault" value="false" /> ...


2

I don't think that is a correct solution for you to use Publishing Restrictions. Sitecore documentation: If you specify a date range for when an item or item version is publishable, it does not mean that the item is published on the start date and removed again on the end date. Instead, it means that the item is available for publishing and ...


2

You don't need to manipulate with workflow state of newer versions or with publishing restrictions. You can use Sitecore API and PublishOptions.PublishDate property. Just pass the datetime when your chosen version was created as the constructor argument like: new PublishOptions(..., ..., version.Statistics.Created); And pass it to PublishItemContext: var ...


2

It is possible by playing with one of those two things: You can set the Publishable option of version 3 to false. If you have workflow configured in this item, you or the author can set the version 3 back to the draft state.


2

Your code loops over all the versions in the selected language: foreach (Sitecore.Data.Items.Item version in languageItem.Versions.GetVersions()) If you want to show only the latest version, just remove that line. If you want to show all the particular versions of the item, change the variable you use in the loop from languageItem to version: foreach (...


2

It is possible, but not simple. The dialog in your screenshot is located here: {webroot}/sitecore/shell/Applications/Content Manager/Galleries/Versions/Gallery Versions.xml And the code beside is: Sitecore.Shell.Applications.ContentManager.Galleries.Versions.GalleryVersionsForm,Sitecore.Client To change this, you would need to create your own code beside ...


2

In terms of SXA then: How to remove a version of the data source on a single click of removing version of the page (associated version of the data source items). There is no such automation on the SXA side, you will need to implement it on your own. Is there any setting in Sitecore for adding/removing version for data source when we add a version of the page....


2

The best I can see if to override the code beside for \sitecore\shell\Applications\Content Manager\Galleries\Versions\Gallery Versions.xml. It is currently set to Sitecore.Shell.Applications.ContentManager.Galleries.Versions.GalleryVersionsForm. This would allow you to insert some code as the next version gets loaded.


1

By default, when you apply a workflow on an item and it has been updated, a new version should be created for this item. As your page has a workflow and not your component datasource, it is the expected behaviour that the version is not incremented. Now, if you have a workflow on the page, when the user will need to update it, he/she will require to Lock ...


1

ItemManager.AddFromTemplate method creates an item with 1 version already. And from what I remember, it creates the child item in the language of the destination parameter (3rd one), where you pass parent item. It means that if you pass en version of the parent to the AddFromTemplate method, it will create en version of the item. Try to get ar version of ...


1

As discussed in comments, should avoid serialising content that is in production and that is being used by content editors. The following is mentioned on Unicorns readme file on github. NOTE: When deploying to a Content Editing or Content Delivery server, the Unicorn configuration should be trimmed down from development. Each config file in App_Config/...


1

When a user creates an item, Sitecore creates a version in the current content language and initiates the workflow for that version. After that item completes its workflow, if a user edits the item in that language, Sitecore creates a new version and initiates its workflow. In some cases when working as a Sitecore administrator, Sitecore does not create new ...


1

In terms of auto-publishing at a specific time this is a really good module and it supports versions: https://marketplace.sitecore.net/Modules/S/Sitecore_Scheduled_Publish.aspx?sc_lang=en See my answer here for more info on the module: Scheduled publish/unpublish strategy With regard to maintaining multiple urls for different versions of an item. This is ...


1

You'll find several blog posts on how to upgrade, but I can provide here the initial steps. Open the documentation page of the Sitecore version you want to update to and download the upgrade guide. In your case, open https://dev.sitecore.net/Downloads/Sitecore_Experience_Platform/82/Sitecore_Experience_Platform_82_Update3.aspx. Check the prerequisites in ...


Only top voted, non community-wiki answers of a minimum length are eligible