As a rule, we try to guide people to a document's published_url rather than the platform URL. This has always been a little iffy, but page embeds are uniquely vulnerable to completely blocking document access. Imagine someone:
Uploads a doc
Embeds a page on Article Page
Pixel Ping records Article Page as the document’s detected_remote_url
detected_remote_url feeds published_url
The page embed uses published_url for all interface links back to the "full document"
Now visitors to the page embed on Article Page, who try to click “Read full document on DocumentCloud”, keep getting sent back to the same Article Page they’re on
Gross. We should untangle how this all works, but until then, page embed needs to just send people to the full document on the platform.
As a rule, we try to guide people to a document's
published_urlrather than the platform URL. This has always been a little iffy, but page embeds are uniquely vulnerable to completely blocking document access. Imagine someone:detected_remote_urldetected_remote_urlfeedspublished_urlpublished_urlfor all interface links back to the "full document"Gross. We should untangle how this all works, but until then, page embed needs to just send people to the full document on the platform.