Skip to content
Fulstech Docs

Troubleshooting and Support

Confirm that Better Pages is installed and enabled under Manage apps. Reload the Confluence editor, open Insert elements, and search for Better Pages. The current catalog contains 19 authoring macros.

Better Pages says a subscription is required

Section titled “Better Pages says a subscription is required”

Ask a Confluence administrator to open Manage apps and start or renew the Marketplace evaluation or subscription. The Marketplace listing shows the current evaluation and pricing terms. An inactive license blocks Better Pages editing and app tools without deleting existing Confluence content or Forge-hosted app data.

A Button, Card, Banner, or Progress step does not open

Section titled “A Button, Card, Banner, or Progress step does not open”

Edit the component and verify the destination. Supported values are a selected Confluence page, an https:// address, a relative path beginning with /, an anchor beginning with #, or a valid mailto: address. Credentials, protocol-relative URLs, javascript:, and local-file schemes are rejected.

A tab is missing or shows the wrong content

Section titled “A tab is missing or shows the wrong content”

For new pages, one Tabs macro owns the complete group. Open its configuration, confirm every tab is present and uniquely named, and choose one default tab. After saving, keep each rich-content block under its matching generated heading inside the same macro body.

Deleting a tab also deletes its owned heading section. If the page contains older adjacent Tabs macros, leave that compatibility content intact or rebuild it deliberately as one current tab group; do not mix the two authoring models.

Footnotes or references are missing from a summary

Section titled “Footnotes or references are missing from a summary”

Publish the page before checking the final order. A summary collects compatible items above it, stopping at the previous summary in the same page scope. Move the summary after the items it should collect.

Open the macro editor and reselect the source. For uploads, confirm the file type and size; for page attachments, verify the reader can access the page; for Brand Kit assets, confirm the kit is published. A stock result may become unavailable at its source and can be selected again.

Interactive controls look correct but do not respond

Section titled “Interactive controls look correct but do not respond”

Test the published page, not only the Confluence editor placeholder. Reload the page, then try pointer and keyboard interaction. Confirm the app is enabled and that no browser content blocker is removing Atlassian Forge frames.

Open Smart Designer from the published page’s byline. The editor launcher is a safe preview because Forge cannot replace the surrounding unsaved editor draft. If the source page changed, reload the source, rebuild the staged canvas, and apply it again.

Review the completed-operation list and refresh the inventory. Confluence permissions and page state are checked immediately before each operation, so a batch can stop after earlier items succeeded. Do not rerun the full selection until you identify which pages already changed.

An administrator setting reports a conflict

Section titled “An administrator setting reports a conflict”

Another administrator saved a newer revision, or Atlassian egress consent is in progress. Reload, review the current state, and save again.

Submit bugs and feature requests through the Fulstech support portal. Include the site and page URL, Better Pages feature, expected and actual result, reproduction steps, and a screenshot with sensitive information removed. Never include passwords, tokens, or confidential content that is not required.