Skip to content

Conversation

andren
Copy link
Contributor

@andren andren commented Aug 20, 2025

Addresses #77

Before

See issue above

After

image

Page 4* is from confluence endpoint A, and page 2* is from confluence endpoint B. Page 2* is now being skipped due to not having access, instead of halting the export process.


If the exporter detects a link to an external Confluence endpoint, it could try to use the existing credentials to authenticate. If not successful, it could prompt for additional credentials to successfully export the page, or it could simply skip it.

I think the above approach would require a deeper redesign (how would we start the auth-flow mid-export?), so I took the simpler approach of skipping that external page.

@andren andren force-pushed the dev/andren/external-confluence-link-workaround branch from bd17588 to e7d6fa4 Compare September 4, 2025 08:55
@andren andren force-pushed the dev/andren/external-confluence-link-workaround branch from e7d6fa4 to 7834e6d Compare September 8, 2025 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant