Load ZetaJS assets from CDN for document editing

[erseco]

Summary

• define the default CDN endpoint for ZetaJS assets and surface a reusable browser-mode message
• update the ZetaJS converter to detect CDN usage, adjust PDF generator handling, and expose config helpers
• enqueue a module loader on the document editor to preload CDN assets and guide the admin UI when PDF export stays browser-side

Testing

• php -l resolate.php
• php -l includes/class-resolate-zetajs.php
• php -l includes/class-resolate-document-generator.php
• php -l includes/class-resolate-admin.php

---

https://chatgpt.com/codex/tasks/task_e_68ecb8a07e8c8322a6bf2659a6177b5f

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback

[chatgpt-codex-connector]

Default CDN constant disables configured ZetaJS CLI PDFs

Defining RESOLATE_ZETAJS_CDN_BASE to a non‑empty URL by default makes Resolate_Zetajs_Converter::is_cdn_mode() return true on every install, so generate_pdf() now always returns the browser‑only error and the PDF button is disabled even when RESOLATE_ZETAJS_BIN was already configured. Existing sites that previously produced PDFs via the local CLI will regress unless administrators manually override this constant to an empty string. Consider leaving the CDN base undefined by default or only setting it when the CDN mode is explicitly enabled so server-side conversions keep working out of the box.

Useful? React with 👍 / 👎.