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
  • in reply to Jonathan Williams

    The main use case is for editors who publish one or more items to Staging and then want to republish all of these to Live without having to go and find the individual items (or put them in a bundle).

  • I implement the GUI extension for this whereever possible.

  • I've asked some users (as we have an extension in place). The feedback was that most of the publishing issues are infra/DevOps related so when there's a problem publishing (usually in Transport or Deployment) they ping DevOps who reply "it's fixed". There could be items in there published to STAGE, some to PROD, some to QA etc. - they don't want to have consider that - their aim is to change a failed into a success. As such they simply want to 'Resend to publish queue'. Some did suggest a Review/Republish option which may allow them to "up" the priority for example.

  • in reply to Dominic Cronin

    Out of the example extensions and from what you've seen with users, is the desire to be able to only republish from the Publishing queue, without any further user interaction? Or have the extensions required the user to revisit settings in the Publishing dialogue before creating a new Publishing request (transaction)?

  • This is an idea that has proved itself. Since Hendrik originally proposed it, there have been, to my knowledge, three implementations of an extension. One by me on the old extensions framework, then Bart did one on Anguilla when it was new, and then later did another one on Alchemy. This functionality doesn't seem to have a downside - and as far as I can see, the only reason it never made it into the product was the availability of extensions. Apart from anything else, I'd like to see /that/ logic turned on its head. The fact that people implement a feature as an extension is evidence that there's a case for the feature. (Obviously, not all features are for everyone.) These days, with the move to the cloud, creating extensions involves more administrative effort than previously, and isn't always possible for everyone. Let's get the good ones into the core product!