How to publish all versions of an item to Web DB (Sitecore 8.0+)












0















The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.



I'm using Sitecore 8.2.170407



After reading this article, I tried to do several things:




  • Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work

  • Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
    Image of patch class and Image of patch config
    That didn't work either.

  • Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.


I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6



Have any of you been in the same situation before? How did you solve the issue?



If you need more information, please let me know.



Thanks in advance






sitecore sitecore8







share|improve this question


















  • 1





    Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

    – Jay S
    Nov 22 '18 at 15:15











  • You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

    – Casper
    Nov 23 '18 at 7:57













  • Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

    – Jay S
    Nov 23 '18 at 15:39











  • Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

    – Casper
    Nov 26 '18 at 7:11











  • I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

    – Casper
    Nov 26 '18 at 7:16
















0















The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.



I'm using Sitecore 8.2.170407



After reading this article, I tried to do several things:




  • Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work

  • Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
    Image of patch class and Image of patch config
    That didn't work either.

  • Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.


I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6



Have any of you been in the same situation before? How did you solve the issue?



If you need more information, please let me know.



Thanks in advance






sitecore sitecore8







share|improve this question


















  • 1





    Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

    – Jay S
    Nov 22 '18 at 15:15











  • You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

    – Casper
    Nov 23 '18 at 7:57













  • Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

    – Jay S
    Nov 23 '18 at 15:39











  • Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

    – Casper
    Nov 26 '18 at 7:11











  • I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

    – Casper
    Nov 26 '18 at 7:16














0












0








0








The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.



I'm using Sitecore 8.2.170407



After reading this article, I tried to do several things:




  • Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work

  • Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
    Image of patch class and Image of patch config
    That didn't work either.

  • Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.


I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6



Have any of you been in the same situation before? How did you solve the issue?



If you need more information, please let me know.



Thanks in advance






sitecore sitecore8







share|improve this question














The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.



I'm using Sitecore 8.2.170407



After reading this article, I tried to do several things:




  • Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work

  • Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
    Image of patch class and Image of patch config
    That didn't work either.

  • Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.


I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6



Have any of you been in the same situation before? How did you solve the issue?



If you need more information, please let me know.



Thanks in advance






sitecore sitecore8




sitecore sitecore8






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 9:09









CasperCasper

53




53








  • 1





    Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

    – Jay S
    Nov 22 '18 at 15:15











  • You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

    – Casper
    Nov 23 '18 at 7:57













  • Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

    – Jay S
    Nov 23 '18 at 15:39











  • Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

    – Casper
    Nov 26 '18 at 7:11











  • I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

    – Casper
    Nov 26 '18 at 7:16














  • 1





    Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

    – Jay S
    Nov 22 '18 at 15:15











  • You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

    – Casper
    Nov 23 '18 at 7:57













  • Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

    – Jay S
    Nov 23 '18 at 15:39











  • Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

    – Casper
    Nov 26 '18 at 7:11











  • I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

    – Casper
    Nov 26 '18 at 7:16








1




1





Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

– Jay S
Nov 22 '18 at 15:15





Can you explain what problem you are trying to solve? It seems you have chosen to solve the problem with all versions in the web DB, but that doesn't work. There may be another way to solve the problem... What are you attempting to do?

– Jay S
Nov 22 '18 at 15:15













You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

– Casper
Nov 23 '18 at 7:57







You are correct about the problem I'm trying to solve. My case is simply: I have 3 versions of an item. I publish the item, and all 3 versions will be visible in the web DB.

– Casper
Nov 23 '18 at 7:57















Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

– Jay S
Nov 23 '18 at 15:39





Sorry Casper, I meant, WHY are you needing 3 versions in the web DB? There may be another way to meet the WHY without needing 3 versions.

– Jay S
Nov 23 '18 at 15:39













Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

– Casper
Nov 26 '18 at 7:11





Thanks for answering Jay. I appreciate your time. Our customer wants to have the opportunity to create content before hand, meaning they can create content for, lets say, 1 month ahead. With Sitecore's lifetime feature, they would set the start date and end date for a specific version. I would think that unless there are versions in WEB db, lifetimes wouldn't work. Do you suggest another way?

– Casper
Nov 26 '18 at 7:11













I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

– Casper
Nov 26 '18 at 7:16





I take that back. I clearly didn't research this enough. Sorry for taking your time. Have a great day!

– Casper
Nov 26 '18 at 7:16












2 Answers
2






active

oldest

votes


















1














You can't.



The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.






share|improve this answer
























  • Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

    – Casper
    Nov 23 '18 at 7:56





















0














Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.



All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.



Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427313%2fhow-to-publish-all-versions-of-an-item-to-web-db-sitecore-8-0%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    You can't.



    The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.






    share|improve this answer
























    • Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

      – Casper
      Nov 23 '18 at 7:56


















    1














    You can't.



    The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.






    share|improve this answer
























    • Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

      – Casper
      Nov 23 '18 at 7:56
















    1












    1








    1







    You can't.



    The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.






    share|improve this answer













    You can't.



    The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 22 '18 at 14:29









    Mark CassidyMark Cassidy

    5,5251728




    5,5251728













    • Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

      – Casper
      Nov 23 '18 at 7:56





















    • Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

      – Casper
      Nov 23 '18 at 7:56



















    Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

    – Casper
    Nov 23 '18 at 7:56







    Thanks for answering back. Would I need to reinvent the WHOLE publishing process or is it possible to only modify the RemoveOtherVersions process (which is what I tried to do without any luck)?

    – Casper
    Nov 23 '18 at 7:56















    0














    Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.



    All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.



    Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.






    share|improve this answer




























      0














      Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.



      All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.



      Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.






      share|improve this answer


























        0












        0








        0







        Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.



        All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.



        Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.






        share|improve this answer













        Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.



        All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.



        Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 26 '18 at 13:07









        Jay SJay S

        7,02722947




        7,02722947






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427313%2fhow-to-publish-all-versions-of-an-item-to-web-db-sitecore-8-0%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -

            Popular posts from this blog

            Costa Masnaga

            Image
            .mw-parser-output .avviso .mbox-text-div>div,.mw-parser-output .avviso .mbox-text-full-div>div{font-size:90%}.mw-parser-output .avviso .mbox-image div{width:52px}.mw-parser-output .avviso .mbox-text-full-div .hide-when-compact{display:block} Questa voce o sezione sull'argomento Lombardia non cita le fonti necessarie o quelle presenti sono insufficienti . Puoi migliorare questa voce aggiungendo citazioni da fonti attendibili secondo le linee guida sull'uso delle fonti. Segui i suggerimenti del progetto di riferimento. Costa Masnaga comune Localizzazione Stato   Italia Regione Lombardia Provincia Lecco Amministrazione Sindaco Sabina Panzeri (Al centro il cittadino) dall'08/06/2009 Territorio Coordinate 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Coordinate: 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Altitudine 318 m s.l.m...
            Read more

            Fotorealismo

            Image
            Guerrino Boatto, Venice's St. Barnaba Church and canal Il fotorealismo è un genere di pittura basato sull'uso di una o più fotografie dalle quali l'artista prende le informazioni necessarie da utilizzare poi nel processo della creazione dell'opera, in genere ad olio o ad acrilico, al fine di avere un aspetto finale il più simile possibile alla fotografia. Indice 1 Storia 2 Lista dei fotorealisti 3 Note 4 Voci correlate 5 Altri progetti Storia | Il fotorealismo è un movimento che nasce negli Stati Uniti d'America alla fine degli anni sessanta [1] sulla scia della Pop Art [2] [3] [4] , e insieme condividono il carattere reazionario verso la travolgente ascesa dei media, che alla metà del ventesimo secolo si trasforma in un fenomeno di massa talmente imponente da minacciare il valore dell'immagine nell'arte. [5] [6] Ne consegue così che, colto il gesto d'inizio che fu della Pop Art, i fotorealisti aprono ad un ...
            Read more

            Sidney Franklin

            Image
            Questa voce sull'argomento registi statunitensi è solo un abbozzo . Contribuisci a migliorarla secondo le convenzioni di Wikipedia. Sidney Franklin, foto di Carl Van Vechten Oscar alla memoria Irving G. Thalberg 1943 Sidney Franklin , all'anagrafe Sidney Arnold Franklin , (San Francisco, 21 marzo 1893 – Santa Monica, 18 maggio 1972), è stato un regista, produttore cinematografico e attore statunitense. Il 20 giugno 1963, si sposò con l'attrice australiana Enid Bennett. Il matrimonio durò fino alla morte dell'attrice, il 14 maggio 1969 [1] Indice 1 Filmografia 1.1 Regista 1.2 Aiuto regia (parziale) 1.3 Produttore 1.4 Attore (parziale) 2 Note 3 Altri progetti 4 Collegamenti esterni Filmografia | Regista | The Baby , co-regia Chester M. Franklin (1915) The Rivals , co-regia Chester M. Franklin (1915) Little Dick's First Case , co-regia Chester M. Franklin (1915) Her Filmland Hero , co-...
            Read more