Known Issues

Hidden Point Studio • Product Status

Known Issues

Track active bugs, regressions, temporary workarounds, compatibility problems, unresolved support patterns, and recently fixed issues across BeaconWP, modules, theme packs, storefront tools, and Hidden Point Studio platform pages.

View Issues Support Module Support Changelog
Open Issues Current problems that are confirmed, reported, or under active review.
Workarounds Temporary steps users can take while a proper fix is being built or tested.
Monitoring Issues believed fixed but still being watched for repeat reports or edge cases.
Resolved Recently fixed problems that may still be useful for users checking update history.
Support Center Get routed to the correct support path for product, account, license, or module issues. Module Support Report module-specific bugs, update problems, compatibility issues, and settings trouble. Changelog Review recent fixes, new releases, beta changes, and product updates. Developer Forum Discuss technical causes, integrations, hooks, filters, pack behavior, and reproducible bugs.

Current Issue Tracker

Replace these sample issue cards with real active issues, workarounds, and fix status notes.

Known Issues

Forum pages may show only header/footer if the wrong template is selected

Area: WordPress page templates
Open

Some forum/member pages may appear blank or may only show the Hidden Point Studio header and footer if assigned to a template that does not render page content.

  • Workaround: use a page/content template that renders the page body.
  • Confirm the page is published and not scheduled.
  • Confirm the forum shortcode or HTML block exists in the page content.

Generic support links need matching destination pages

Area: site navigation
Monitoring

New member and support pages use shared navigation links such as Documentation, Changelog, Known Issues, Members, and Support. These pages should exist before the links are pushed broadly.

  • Confirm `/documentation/`, `/changelog/`, `/known-issues/`, `/members/`, and `/support/` exist.
  • Check page slugs after publishing.
  • Clear cache after adding or renaming pages.

Forum module output placeholders must be replaced

Area: forum pages
Open

Forum landing pages currently include placeholder shortcode blocks. Those placeholders must be replaced with the actual Forum Module shortcode, block, or rendered output for each forum section.

  • Replace placeholder text with the real forum shortcode or block.
  • Confirm each forum slug matches the forum module configuration.
  • Verify access control for private areas like Staff, Founder, and Agency spaces.

Public pages should not expose internal-only areas

Area: access control
Monitoring

Pages such as Staff Portal, Founder Hub, Founder Preview Lab, Agency / White Label, and private module support areas should be protected before public navigation makes them easy to find.

  • Confirm access rules are applied before launch.
  • Hide private links from public visitors where possible.
  • Use direct support for private billing, license, and account issues.

Resolved sample entry

Area: example status card
Resolved

This is a sample resolved issue card. Replace it with a real fixed issue when the first confirmed fix is ready to document.

  • Use resolved cards for recent fixes users may still search for.
  • Link to the changelog entry when available.
  • Remove old resolved entries once they are no longer useful.