Is Data Tables for Confluence compatible with Confluence Server or Confluence Data Center?

Right now, we only support Confluence Cloud, if you are interested in a server version, please contact us.

Why are embedded (preview) images are not rendered?

If embedded (preview) images are not rendered, you might need to change the browsers’ cookie settings as “third-party cookies” are required for authentication. Depending on the browser, you need to allow these cookies for the address of your Confluence instance (for example https://your-company.atlassian.net) as follows:

• In Firefox: Add the address as “Exceptions for Enhanced Tracking Protection” (under “Settings > Privacy & Security”).

• In Chrome: Add the address under “Sites allowed to use third-party cookies” (under “Settings > Privacy and security”).

• In Edge: (Temporarily) allow third party via the eye icon in the address bar when viewing a Confluence page with broken images.

After changing the settings, you might need to clear the browsers cache and reload the Confluence page.

Why is the “Table state saving and restoring” feature not working?

Due to technical limitation in the Atlassian Confluence Cloud infrastructure the “Table state saving and restoring” requires “3rd party cookies” to be enabled in the client’s browser. The “Data Tables for Confluence” app needs to be embedded as iFrame that loads the content from the domain confluence-datatables.weweave.net. As this domain differs from the domain the actual Confluence Cloud instance is running on, the browsers detects the app as 3rd party content.

To enable “3rd party cookies” for your Confluence instance, you can follow the steps described in “Why are embedded (preview) images are not rendered?”.

Are there any known problems?

If you're using sub-macros in your tables, you might experience issues due to the underlying architecture. Please let us know which of your sub-macros aren't working – we're constantly striving to improve the app.