Log in Request my site

Publish your site

This article covers publishing your site, the copy of your Staging to Production, the site your visitors see. You will be able to read the changes before publishing, start the publication, react if it fails and tell which data goes online.

Before you start

  • Publishing the site requires the Administrator role and the Can publish option. Invite a member and choose their role explains how to give them. The Publish menu appears for every administrator. Without the Can publish option, the publish screen shows you the changes and tells you at the top that your account does not have this right. Only a site owner can give it to you. Other roles do not see this menu.
  • You publish from your Staging, in its administration bar. The Production is not administered.
  • Publishing sends the entire site. A page whose redesign is not finished goes with it, unless you write it in a new version.
  • The site goes to Production only with its six required templates published on the Staging.

Publish to Production

  1. In the administration bar of your Staging, open the Publish menu then click Publish to production. The Publish website to production screen opens.
  2. Review the Changes going to production list. Each content type has a line with its number of changes, for example Pages 2 changes.
  3. To see the detail of a type, click its line. It expands to show its content.
  4. Check I confirm that I want to publish this website. The Publish to production button becomes clickable.
  5. Click Publish to production. The screen shows each step, then the message Site published to Production.
The Publish the site to Production screen: the Changes to publish to Production list with the Legal documents group expanded, its columns Change, Title, Text, Last saved by, Date and Open, the Pages and Projects groups collapsed, then the I confirm that I want to publish this site checkbox and the Publish to Production button, grayed out.

You can close the tab during publication. The work continues on the server. If you reopen the screen, it shows the current step.

Once the publication is finished, each administrator of the site receives the notification Your site … has been published to Production.

Publish the required templates first

Six templates must be published on the Staging for the site to go to Production: Home page, Pages, Single Item (any type), 404 (Not Found), Modal and Side panel. Without one of them, part of the site would display badly online. A page opened in a modal, for example, would take the pages template, with the site’s header and footer inside the window.

As long as one is missing, the Publish website to production screen shows at the top, before the list of changes, the notice The site cannot go to Production: required templates are not published. Publish them first on the Staging: followed by the list of missing templates. The list of changes stays displayed. The I confirm that I want to publish this website checkbox and the Publish to production button stay grayed out.

  1. In the notice, click the name of a template. Its editor opens. A template that did not exist is created as a draft.
  2. Choose a creation in the catalog, or compose the template with your blocks.
  3. Publish the template.
  4. Return to the Publish website to production screen. When the six templates are published, the notice disappears. Check the box then click Publish to production.

A draft template does not count. The same templates are the first six steps of the Setup checklist box on the dashboard. Decide the appearance with templates describes them.

Understand why the button stays grayed out

When you cannot publish, the Publish website to production screen gives the reason at the top, as soon as it opens and before the list of changes. The list stays displayed below. If two reasons apply together, both notices are shown.

The notices that prevent publishing
NoticeReasonTo publish
Your account does not have the right to publish this site. An owner of the site can give it to you with the Members button of your Lovely Render dashboard.You are an administrator of the site without the Can publish option.Ask a site owner to check Can publish for you with the Members button of the site’s card on the Dashboard. An administrator who has this right can also publish the site.
The site cannot go to Production: required templates are not published. Publish them first on the Staging:One of the six required templates is not published.Publish each template in the list, as described in the Publish the required templates first section.
An operation is in progress on this site: followed by a step, for example An operation is in progress on this site: restoring to Production…A restore, the assembly of a version or an export of the site is in progress. The list of changes is hidden meanwhile.Wait for the operation to finish. The screen updates by itself and says how it ended, for example Restored to Production.
The publication did not start. Reload the page, then publish again.Your click did not go through, for example because your session expired.Reload the page. If a reason prevents you from publishing, its notice appears at the top.

Read the changes before publishing

The list sorts the content by type: your pages, each of your content types, your categories, your compositions and your templates. Your legal documents come first and their group opens expanded. In this group, the Text column gives the edition that the publication will create.

The columns of an expanded group
ColumnContent
ChangeThe label of the effect of the publication on this content item.
TitleThe content item’s title.
Last saved byThe last person to have saved this content item. When an AI wrote for a member, the cell shows both names, for example “Julie Garnier, with Claude”.
DateThe date of this last save.
OpenEdit opens the content item in the editor. View opens its page, Preview its preview when it is not published.
The labels of the Change column
NoteEffect of the publication
NewThe content item appears online.
ModifiedThe content item is online and its Staging version replaces it.
WithdrawnThe content item is online and will no longer be. You put it back to draft or made it private.
DeletedThe content item is online and will no longer be. You moved it to the trash.
Draft, Draft, pending review, PrivateThe content item stays offline.
New versionThe new version of a published content item stays offline. The published content item goes as it is.

A draft does not go online. To put it online with this publication, open it with the Edit link and publish it in the editor before publishing the site.

Under the content, the The design changed: line lists the parts of the design that differ from the Production. These parts are Colors, Fonts & text sizes, Spacing & corners, Logo, Favicon / app icon, Design images, SVG icons, Animations, Site styles or Custom CSS.

Understand what publishing does

A click on Publish to production starts three steps in this order. During each one, the screen shows Publishing in progress: followed by the step, for example Publishing in progress: backing up the Production…

The steps of a publication
Step shownEffect
Backing up production…Your Production is copied to the Backup, the third copy of your site, before it is touched.
Publishing staging to production…Your content, your design and your settings are copied to Production. Internal links are rewritten to your domain name. Your media are shared by both: they are not copied.
Saving the version…The site as it was online before this publication is saved as a site version. You can go back to it from the version history.

The new Production is prepared next to the live one, then replaces it at once. Your visitors see the old site until that instant, then the new one. They never see a half-replaced site.

At each publication, the published, changed or removed addresses are sent to the search engines that follow the IndexNow protocol.

React to a publication that fails

If the copy fails along the way, the screen shows Publishing in progress: rolling back… and your Production returns to the copy made at the first step. Your live site stays the one from before the publication. The message Publication failed. Publish again. If it fails again, write to us. appears.

  1. Reload the Publish website to production screen and start the publication again.
  2. If it fails again, write to us. We look for the cause with you.

Your site’s history keeps each attempt, for example Publication to Production: failed, Production restored.

Know what goes online

Publishing copies what you build. The data your visitors produce stays in the copy where it was born.

The data copied by publishing
DataCopied to Production
Pages, posts, entries, terms, menus, compositions and templatesYes
Languages and translationsYes
Design, fonts, logo and iconsYes
Redirects and settingsYes
MediaShared by the Staging and the Production, never copied
Requests received by your formsNo
Visit statisticsNo
Google Search Console and Bing dataNo

A request sent by a visitor stays in your Production, even after ten publications. The Statistics screen and the request list each have a Production view and a Staging view.

See also

Updated on

All documentation pages