Hey everyone, We’ve run into a problem after migrating some Confluence pages from Server to Cloud. Here’s the setup: * We’re using Page Properties / Page Properties Report that reference fields from other pages. * The result is a nice table with links + values automatically pulled in. * To filter these results, we’re using the Aura Table Filter plugin. The issue: * On migrated pages, when a user hits Modify, Confluence says the page needs to be converted. * After conversion, some elements inside those pages end up wrapped in a legacy-editor container. * Once that happens, the Aura Table Filter no longer recognizes the values. So in short: Migrated pages → require conversion → content wrapped in legacy-editor → table filter breaks. Questions: * Is this a known limitation with Aura Table Filter when handling legacy-editor content? * Is there a recommended workaround (like re-creating the references, bulk conversion, or stripping the legacy container)? * Has anyone else faced this post-migration issue, and how did you resolve it? Thanks in advance for any tips, BR, Federico

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Aura Table Filter not recognizing values after page conversion from server → cloud

Federico Viviani

Hey everyone,

We’ve run into a problem after migrating some Confluence pages from Server to Cloud. Here’s the setup:

We’re using Page Properties / Page Properties Report that reference fields from other pages.
The result is a nice table with links + values automatically pulled in.
To filter these results, we’re using the Aura Table Filter plugin.

The issue:

On migrated pages, when a user hits Modify, Confluence says the page needs to be converted.
After conversion, some elements inside those pages end up wrapped in a legacy-editor container.
Once that happens, the Aura Table Filter no longer recognizes the values.

So in short:
Migrated pages → require conversion → content wrapped in legacy-editor → table filter breaks.

Questions:

Is this a known limitation with Aura Table Filter when handling legacy-editor content?
Is there a recommended workaround (like re-creating the references, bulk conversion, or stripping the legacy container)?
Has anyone else faced this post-migration issue, and how did you resolve it?

Thanks in advance for any tips,

BR,

Federico

Accepted answers

Philip Feldmann - appanvil

Hi @Federico Viviani

Philip from Aura Apps here. Thank you for making us aware of this issue, dealing with legacy content can often times be challenging.

From just reading your post, we believe that we know what the issue is and the team has already deployed a fix that might take care of the issue. Could you please check on your end whether the problem persists? If it does, please reach out to our service desk so that we can take the next steps and recreate your exact setup on our end: Aura service desk.

Best regards,

Philip

All comments

Philip Feldmann - appanvil

Hi @Federico Viviani

Philip from Aura Apps here. Thank you for making us aware of this issue, dealing with legacy content can often times be challenging.

Best regards,

Philip

Federico Viviani

Hi @Philip Feldmann - appanvil ,

Thanks for your reply - do you mean that I should check with no action on our side?

Should this work when pages are converted from legacy-editor or also before conversion?

Thanks!

Federico

Philip Feldmann - appanvil

Hi @Federico Viviani

Exactly, no action should be necessary on your end. If you're still experiencing problems, let's take this discussion to our service desk so that we can track the necessary steps: https://appanvil.atlassian.net/servicedesk/customer/portal/13

Best,

Philip

Stiltsoft support

Hi @Federico Viviani ,

We've reacted to the "Table Filter" part of your question - are you referring strictly to the Aura Table Filter app?

We mean that you are talking about migration "from Server to Cloud".

Do you mean migrating from a Data Center instance to Cloud? Cause our Table Filter, Charts & Spreadsheets for Confluence app works both on DC&Cloud (and fully supports the migration). And as far as we can see, Aura Table Filter is developed only for Cloud. Aren't you mixing the two apps up? Seems that the macros have similar names.

Or are you referring to the Legacy Editor -> New Editor page conversion on Cloud using the Aura Table Filter plugin? Then it seems that it is not a case for our team to investigate.

If you've meant smth else that we can help you with, please give more details.

Federico Viviani

I am not sure on how things went but I think that users started using Aura Table Filter only after the Server -> Cloud migration was completed, so I think this is the intended usage.

I am referring to the editor migration which seems (to me, might be wrong) not directly related to plugins.

Thanks and BR,

Federico

Stiltsoft support

If the app wasn't installed on your Server instance, the situation makes sense.

What concerns the editor migration: as we see, Aura Table Filter runs on Atlassian (uses Forge). And Forge-based macros generally do not work in the Legacy editor (you'll see blank spaces).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

filter

table

table-filter

table-filter-and-charts

table-filter-charts-spreadsheets

table-toolbox