Workaround for 32KB Content Property Limit to Index a 5MB LaTeX Document in a Custom ACE Macro

Confluence Development Confluence Cloud
, ,
1

Hi everyone,

I’m building a custom Confluence Cloud macro using Atlassian Connect Express (ACE) to index and display content from large LaTeX documents (up to 5MB). My goal is to attach metadata to pages via content properties, make them searchable with FTS and CQL, and render them dynamically in the macro. However, I’ve hit the 32KB limit for content properties, which isn’t enough to store or index the full document or even a meaningful chunk of it.

Has anyone found a workaround for this limitation? I’m considering options like:

  • Splitting the document into smaller parts across multiple content properties.

Ideally, I’d like the macro to still leverage Confluence’s search/indexing capabilities while handling the 5MB LaTeX content. Any ideas, examples, or alternative approaches would be greatly appreciated!

2

Probably don’t build a Connect app as they’re deprecating it next year: Announcing Connect End of Support: Timeline and Next Steps

Yeah the 32KB limit is a joke.

Some options:

  1. Chunk the data and spread across multiple content properties
  2. Store and retrieve as a Confluence attachment (limit is set by org admin)
  3. Wait for this to go live: RFC-72 : Forge Object Store
3 Likes