Content published but not Media, despite IP restriction in place #281
Description
Describe the bug
This is a bit of a bug/question/feature request...
We have a setup where we have Local > Staging > Production servers.
Staging and Production are behind Cloudflare and Production has IP restriction in place on the /umbraco route.
Local to Staging pushes fine.
When pushing from Staging to Production, content nodes were pushed to Production but the media within those nodes was NOT pushed to Prodution. This then resulted in "null reference errors" on the front-end trying to display the images with Slimsy, and nodes in the backoffice failing to render with a "failed to get content with id" error (iirc). Even sibling nodes that weren't pushed. Ancestor nodes were fine.
Unable to calculate version "<!DOCTYPE html> <html> <head> <title>Sign in ・ Cloudflare Access</title>...
url | [redacted]/umbraco/uSyncReceive/uSyncReceiveApi/Enabled
SourceContext | uSync.Publisher.Publishers.SyncRealtimePublisher
ActionName | uSync.Publisher.Controllers.uSyncPublishApiController.CheckServer (uSync.Publisher)
RequestPath | /umbraco/backoffice/usync/usyncpublishapi/CheckServer/
Our Staging IP was not whitelisted (on production) for this push, so how was any content able to be pushed at all? I would have expected nothing to push. Are there other routes that uSync uses?
Once we had identified this issue and resolved the setup, when trying to push again, uSync reported "no changes" despite none of the media files having been pushed. Is there some sort of reference/tracking in place or is it just looking at content?
Feature request - In this scenario it would have been handy to have a "Force push" button to run the push again.
Version (please complete the following information):
- Umbraco Version: 13.7.2
- uSync Version 13.2.5
- uSync.Complete Version 13.1.7
Expected behavior
If the target server is "unavailable" then it shouldn't be possible to push anything.
All content and media should be pushed, not just content.
If content or media is not pushed (physically on the target) it should be possible to push.
I don't have any screenshots as was firefighting a broken production site.