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
When I have a failed publication (state: Failed/Error) the workspace link leads to a 404 and the state link leads to the roles-acceptance page. Both of these end points are dead ends.
To reproduce a failed publication, use the following.
(Note, this failure path may not exist forever, see Connexions/cnx-publishing#71 for details.)
| Book With Issue (BWI)
|- Page One (PO)
|- Page Two (PT)
Create a book with two pages (as shown above).
Publish the book.
Copy the link to PO.
Edit PT to include the link to PO *. (For good measure add a keyword to the book so that it is edited as well.)
Publish
The workspace now shows the state as "Failed/Error". If you grab the publication id and look at the publishing response you'll see the error is an InvalidReference.
This error is valid since I don't think publishing knows about any other domains besides cnx.org and legacy.cnx.org.
This issue needs to answer the questions How do I recover my content? now that it is in a broken state.
See also, Connexions/cnx-authoring#190, which was the original issue. It was later determined to be a webview issue.
The text was updated successfully, but these errors were encountered:
When I have a failed publication (state: Failed/Error) the workspace link leads to a 404 and the state link leads to the roles-acceptance page. Both of these end points are dead ends.
To reproduce a failed publication, use the following.
(Note, this failure path may not exist forever, see Connexions/cnx-publishing#71 for details.)
This error is valid since I don't think publishing knows about any other domains besides cnx.org and legacy.cnx.org.
This issue needs to answer the questions How do I recover my content? now that it is in a broken state.
See also, Connexions/cnx-authoring#190, which was the original issue. It was later determined to be a webview issue.
The text was updated successfully, but these errors were encountered: