PDF Snapshot

Changelog

1.0.3

• Faster, more reliable generation for large or image-heavy pages. Images embedded in the PDF are now actually resized on the server to match the “Max image width” setting (previously only a display size was capped, so Dompdf still had to download and decode the original full-resolution file). Generation also now runs as a background job instead of blocking the whole request: the button shows “Generating…” and the PDF appears automatically once ready, so a large page can no longer time out mid-generation.
• Fixed “Full themed page” capture producing an unstyled, incorrectly-laid-out PDF instead of matching the live page: the site’s own stylesheets were failing to load during capture in some environments (e.g. behind certain proxy/container setups) and silently falling back to no theme CSS at all. Also fixed the PDF not applying colors, fonts, or spacing that a theme defines via CSS custom properties (common in modern block themes) — Dompdf’s PDF engine doesn’t support those directly, so they’re now resolved to their real values before rendering. Also fixed content occasionally running off the edge of the page when the live theme uses fixed desktop-width containers; every element is now kept within the printable page width. Also fixed the WordPress admin toolbar sometimes appearing inside the generated PDF when the person clicking “Download PDF” was logged into wp-admin at the time. Also fixed some images on the page (typically smaller thumbnails, like related-post images) showing up as broken-image icons in the PDF instead of loading correctly.

1.0.2

• Fixed “Full themed page” capture ignoring the requesting visitor’s own login/membership status. The server-side page fetch used to be completely anonymous, so a membership or content-restriction plugin (e.g. MemberPress, Restrict Content Pro) would see it as a logged-out visitor and serve the restricted/paywall version — or in some setups, redirect away entirely, producing an empty PDF — even for a genuinely authorized member. The fetch now forwards the requesting visitor’s own cookies, so the captured page correctly reflects what they’d actually see: the full content if they have access, or the paywall message if they don’t.
• Fixed a related case where the PDF could still render as a blank/white page: some restriction plugins redirect an unauthorized visitor to a login or upgrade page instead of showing a paywall message inline. The fetch no longer follows redirects blindly — it now detects a redirect away from the requested page and falls back to a direct content capture (so unauthorized visitors still correctly get the real paywall/restriction message in their PDF) instead of silently capturing the wrong page or producing an empty result.

1.0.1

• Moved the settings screen’s button-style toggle and color-picker initialization out of an inline <script> block into a properly registered/enqueued admin script, per WordPress.org plugin guidelines.

1.0.0

• Initial release.