---
title: "Errors publishing to a target space page with page restrictions"
canonical: "https://support.appfire.com/space/CPCL/1163624974/Errors%20publishing%20to%20a%20target%20space%20page%20with%20page%20restrictions"
format: markdown
---
> Macro (aura-html)


## Scenario

As a space administrator, when publishing some previously published and synced pages

- one page displays a publishing error

![cpc_error_message_couldnotcopypage.png](media://9c1aa667-fb26-4621-9471-b77d3dd0745f)

- another page adds a number and bracket to the target space page name

![cpc_onpage_pagename_number_appended_.png](media://0a4a4551-764d-4e15-92c6-18a107ae28e1)

## Problem

A user, including the space administrator, publishing a source space page for the first time to a target space requires **view** and **edit **permission in the target space and the source space. 

Adding page-level restrictions to the published page in the target space affects further publishing actions if the user publishing the page is not included in the added page restrictions.

> Macro (excerpt-include)



## Solution

If the original target page restrictions are removed for the publishing user

- the publishing user has **view** and **edit** permission for the **Project Teams** page and the **Project Teams (2)** page
  - any publishing action is conflicted with two pages in the target space
  - the source page cannot be published and synced
  - an unexpected error message is displayed

Publishing conflicts are removed by deleting *one of these two pages* in the target space.

**One - delete original published page**

- delete the original target space page **Project Teams**
- publish and sync the source page again

The target space page name is updated and the appended **(2)** is removed.

> 📝 The target space page history before the publishing conflict is lost as the original target space is deleted.

**Two - delete the newly published page and remove restrictions on the original published page**

- delete the appended target space page **Project Teams (2)**
- remove the page restrictions for the publishing user on the original target space page **Project Teams**
- publish and sync the source page again

The original target space page is published and synced.

> 📝 The target space page history before the publishing conflict is retained.