Idea Delivered

Republish in the Publishing Queue is available as of SDL Tridion Sites 9.1. Thank you for the idea and feedback!

Republish option in Publish Queue

How about a "Republish" or "Redo" option on the publish queue items? Sometimes a transaction fails (and get fixed in the background) which require republish. Currently you have to locate the page or sg again in the tree, and then click on the publish dialog. Then reselect all the publish properties, and hit publish. It will save a lot of click if you can simply right click on the item in the publish queue and select republish.

Note: this was the most voted for idea on the former SDL Tridion Ideas site (submitted by Hendrik Tredoux); it got 32 votes there.

This functionality has been made available as an extension already:

If you think that providing this functionality Out Of The Box adds a lot of value: vote for this idea (and let us know why).

Rick Pannekoek
Parents

  • Some additional questions where we're looking for some context from the community.

    1. Should the ability to “republish” via a context menu to resubmit a Publish transaction (with no dialogue), be restricted to the same user that submitted the original (i.e. previous) Publish transaction?
    2. Should this republish context menu option be available for both failed and successful transactions? In other words is this only for republishing failed items?
    3. Finally, what's the expectation for a transaction with scheduling options to:
      1. Publish at a later date
      2. Unpublish at a given time

    Would a "republish" even be avaialble on scheduled transactions, or might "redo" attempt to somehow replace scheduled transactions?

    I suspect limiting the option to failed requests simplifies exactly when the republish option should be available.

Comment

  • Some additional questions where we're looking for some context from the community.

    1. Should the ability to “republish” via a context menu to resubmit a Publish transaction (with no dialogue), be restricted to the same user that submitted the original (i.e. previous) Publish transaction?
    2. Should this republish context menu option be available for both failed and successful transactions? In other words is this only for republishing failed items?
    3. Finally, what's the expectation for a transaction with scheduling options to:
      1. Publish at a later date
      2. Unpublish at a given time

    Would a "republish" even be avaialble on scheduled transactions, or might "redo" attempt to somehow replace scheduled transactions?

    I suspect limiting the option to failed requests simplifies exactly when the republish option should be available.

Children
  • in reply to Alvin Reyes

    1) :Seems I can't edit/remove my response below. - feel free to delete

  • in reply to Alvin Reyes
    1. I don't believe so. I've often been tasked with fixing something (restarting a deployer) and then publishing the previously failed items; waiting for the original user (cross timezones) often isn't an option.
    2. So the usecases I have seen that would support including successful transactions
        a) when wanting to republish previously published items _but to a different target_
        b) when I've been testing specific content whilst changing templates and/or content or for mass publishing tests
        c) when there're multiple failed items before and after a successful item and using CTRL+Click is too much hassle (i.e. I just shift click the broader selection of items)

    3.   a) I guess it depends on why the item failed.
            i) If this was set to pre-render and it failed on rendering or transporting then I'd like to be able to re-trigger the same intention to render now and schedule per the first attempt;
            ii) If this was set to pre-render and it failed on deployment then I suspect there's now a sense of urgency to get this on the intended target and the schedule is now irrelevant.
        b) There's no pre-render here so I'd suggest the same as (ii) above