Unable to point deployment to a different content GUID #2400
Comments
|
Perhaps adding an option to the context menu under the triple dot button is the way to go that does the same flow as the "Update Previous Deployment" link. |
|
We can offer the functionality in the triple dot menu |
|
The description on this issue needs a slight adjustment; @dotNomad to update (this is about the URL, not the content type necessarily). Removing from 1.10. |
dotNomad
changed the title
Updated the description and title 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the
update previous deploymentoption is selected, and that flow followed, the pre-deployment will now be pointing to that content GUID.However, if the wrong URL / GUID is provided, there is no way to re-run the
update previous deploymentflow to select a new location to deploy.If a deploy is done it may error due to a different content-type, but if the content type is the same it may override the content as expected.
The workaround here is to create a new deployment.
It may be intentional behavior to not allow a deployment pointing to a Content GUID to not re-directed to a different Content GUID. We will need to decide that when picking up this issue.
The text was updated successfully, but these errors were encountered: