If you could add something to Kentico, what would it be and why?

Select which culture of a document to sync

On multi-cultural sites, almost all of the time you only want to stage / sync one culture version of a document to the live site.

Currently this is not possible, and all culture versions of the document are staged across.

I would like to see either:

a) each culture change shown as a separate staging item in the queue
b) ability to define which cultures to stage when performing a sync
c) or both?

Open to suggestions on implementation.

167 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    James Bloor shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    Hello!

    We are currently exploring this idea and we would like to hear your comments on the following technical proposal:

    When a staging task for a page is logged, culture code of the culture version will be loggged as a separate database field. This information will be used to filter the staging tasks for a specific culture version. There will be a dropdown list filter availbale in the Staging application on Pages tab as well as a column in the listing to identify the culture.

    This way administrator can synchronize only pages in selected culture. Please note that dependencies such as missing parent node for a selected culture version will be handled the very same way as any other dependencies – system ends with an error complaining about missing dependency. You need to make sure that all dependent objects are synchronized in correct order.

    Thanks for your comments!

    David Komarek
    Product Owner

    16 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Matt Kayan commented  ·   ·  Flag as inappropriate

        It would also be great if we could filter by culture on the Staging app's "All Tasks" tab as well, but I understand that may be problematic if there are objects managed by Content Staging which do not have a culture setting.

      • Matt Kayan commented  ·   ·  Flag as inappropriate

        Hi Martin,
        This has come up for us with a site that may roll out multiple cultures over time, but doesn't want to initially push all content for a given culture from staging to production until all content is translated on staging.

        The idea of allowing staging tasks to be filtered on culture sounds like a winner to me.

      • Bizo commented  ·   ·  Flag as inappropriate

        4 years from the request...157 votes....
        Kentico 10 is out and we are still waiting this feature...please just do it! :-)

      • Nik commented  ·   ·  Flag as inappropriate

        That proposal makes sense. It would be better still if each culture's edit were also a distinct staging task. So staging the content directly (via the tree view) would benefit from a drop-down, but I would also prefer to see separate staging tasks.

      • Andrea commented  ·   ·  Flag as inappropriate

        The proposal is fine for us. The dropdown list filter will be useful when we need to publish updates only ifrom one culture in a multi-language site. Thanks!

      • Nik commented  ·   ·  Flag as inappropriate

        This has become a critical issue in our workflow. We support multiple sites localized in dozens of languages with different stakeholders in charge of different content. Without the ability to discretely push content on a culture-by-culture basis, we have had to migrate from one localized site to numerous single-culture sites, with the obvious administrative overhead.

        The current localization/staging process is only suitable for a site with a streamlined and unified editing process. As soon as it's decentralized, this model fails.

        Workflow would be an approach except that preview is not dynamic enough on sites where it's not a one-document = one-page model (e.g. dynamic/HTML 5 sites).

      • James Bloor commented  ·   ·  Flag as inappropriate

        Hi Martin,

        Just wondered if ~100 votes is enough to give this a bump?

        I agree that in an ideal world all languages would be in 'sync' but in reality this doesn't happen - as Andrea states.

        As Kentico's clients get more international, I imagine this will become an important feature.

        Thanks

      • Andrea Mancini commented  ·   ·  Flag as inappropriate

        Hi Martin,
        yes your workflow is the right choice, but in the real world translations can be late or some languages are more important than others for our business. So we go online only with italian while translator works on english version.

        Even when we correct mistakes or errors in articles they are often language-based and we publish only the article X in the Y language. This happens while in the DEV enviroment some people working on new releases or features so it's difficult understand and publish tasks to production.

      • AdminMartin Hejtmanek (Chief Technical Officer, Kentico) commented  ·   ·  Flag as inappropriate

        Hi, what is the reason to publish to production content only for one specific language? Can you describe the specific overall process you are using in more details? Doesn't it make more sense to publish everything consistent to a certain point-in-time, so that the production content is consistent in all languages?

      • James Bloor commented  ·   ·  Flag as inappropriate

        Hi Martin,

        The problem we face is that clients almost always want to 'publish' content on their staging servers so they can share it with their teams. That results in documents not ready for the live site entering in the staging queue.

        It's a bit different from workflow since the document has probably been approved, but it's still not ready to be synchronised to the live site.

        Thanks

      • AdminMartin Hejtmanek (Chief Technical Officer, Kentico) commented  ·   ·  Flag as inappropriate

        Hi, could you please describe the particular scenario where you would use this functionality? Isn't it better to use workflow to say which version of the document is ready for publishing o production and which still needs to be approved first? Or am I missing something?

      Feedback and Knowledge Base