You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the setup process, you are provided with an option to have a privacy page automatically created. The page is created successfully but is missing the site name. So instead of "[site_name] is committed to safeguarding your privacy..." you just get "is committed to safeguarding your privacy". It is easily rectified by editing the page, and in addition the Privacy Policy tab in the Tools area displays the site name correctly, so it seems the issue is only with the Setup Wizard.
The testing was done using WordPress 4.9.5 along with plugins that could potentially manipulate the site title, though likely just on the front end and not the admin. Regardless it would be prudent to replicate the issue to make certain it was not due to an external influence.
The text was updated successfully, but these errors were encountered:
I encountered the same behaviour when first running the setup wizard. Additionally, other dynamic values set by the wizard weren't rendered. Everything was fine on second run, although it appears to generate the content for use, rather than updating the page directly. Which may be by design, but it's not clearly explained if that's the case.
During the setup process, you are provided with an option to have a privacy page automatically created. The page is created successfully but is missing the site name. So instead of "[site_name] is committed to safeguarding your privacy..." you just get "is committed to safeguarding your privacy". It is easily rectified by editing the page, and in addition the Privacy Policy tab in the Tools area displays the site name correctly, so it seems the issue is only with the Setup Wizard.
The testing was done using WordPress 4.9.5 along with plugins that could potentially manipulate the site title, though likely just on the front end and not the admin. Regardless it would be prudent to replicate the issue to make certain it was not due to an external influence.
The text was updated successfully, but these errors were encountered: