Staging
How to improve our content stage system?
-
Implement staging profiles
At this moment Kentico logs about every mutation made in the system. It creates sync tasks for 'global' objects for all staging server definitions.
However there are situations in which developers freely excercice with the objects, testing ideas, developing but not yet finishing, removing objects and later adding them again etc. etc.
Some Kentico installations may consist of 10, 20 or maybe even 100 sites, maintainability of export history or synchronization tasks becomes difficult, time-consuming and error-prone.
The idea idea is this: everything must be updated eventually, but the developers should be able to control this knowing that his object… more
29 votesplanned ·
AdminJaroslav Kordula
(Admin, Kentico CMS)
responded
We plan to improve the staging module in version 7 or later.
-
In Content Staging add username to Object and Document tasks
In Content Staging add the user's name that made the change to an object or document in the task list. That way when you have more than one person syncing objects you can trace who generated the object or document change.
18 votesplanned ·
AdminJaroslav Kordula
(Admin, Kentico CMS)
responded
We plan to improve the staging module in version 7 or later.
-
Upgrade Content Staging to use WCF
Upgrade Content Staging to use WCF and remove all dependencies on Web Services Enhancements (WSE) 3.0 so that Content Staging will run in a Medium Trust environment.
13 votesplanned ·
Michal Neuwirth (Product Manager)
responded
We are thinking about WCF support.
-
Content Staging Default
It would be great if you could setup content staging to have a default when you go to synch instead of "All". I have a developer box setup to synch up and down to staging and a production that is one direction synch to staging. I can see my content authors accidentally choosing ALL and pumping stuff to my dev box I may not be ready for.
1 voteunder review ·
AdminJaroslav Kordula
(Admin, Kentico CMS)
responded
Awaiting reply