FAQ & Troubleshooting

Find answers to common questions and solutions to typical issues when running and configuring the ReportBurster Portal.

Table of Contents

1. The Portal won’t start. What should I check?
2. The first startup takes a long time or the Admin login page is not loading.
3. The Portal still isn’t loading. What next?
4. My custom content type is not working end-to-end (documents not showing, publishing fails, etc).
5. Still stuck?

1. The Portal won’t start. What should I check?

• Docker Engine Required
  The Portal runs inside Docker containers. Make sure Docker is installed and running on your machine.
• Check Docker Installation
  If the Portal does not start, verify your local Docker installation and that you have permission to run containers.

2. The first startup takes a long time or the Admin login page is not loading.

• Initial Provisioning
  The very first time you start the Portal, it will take longer because it needs to download images and provision the environment (install plugins, create database, etc).
• Be Patient
  If the Admin login page is not coming up, give it several minutes—especially on slower machines or networks.

3. The Portal still isn’t loading. What next?

• Check the Logs
  Review the logs for errors.
  • For Docker: docker compose logs
  • For Portal: check the logs in the logs-wp and logs-db folders.
• Look for errors or failed steps during provisioning or startup.

4. My custom content type is not working end-to-end (documents not showing, publishing fails, etc).

Each content type (e.g., payslip, invoice, certificate) must have:

• The content type created in the portal (with all expected fields and correct field types).
• A single-<type>.php template for single document view.
• A page-my-documents.php (or similar) template for listing documents.
• A script to publish documents from ReportBurster to the portal via the REST API.

Troubleshooting steps

• Check the content type:
  Is it created in the portal? Does it have all the expected fields with the correct types?
• Check the templates
  Are single-<type>.php and page-my-documents.php present and adapted for your fields?
• Check the publishing script
  Is the script customized for your content type and fields? Does it handle user creation and access as needed?
• Check access and roles
  Are the correct IFs for user creation, group/role assignment, and access control present in your scripts?
• Use AI to review
  Use the AI tools to double-check and review your scripts and templates based on your content type structure and business rules.

5. Still stuck?

• Double-check each step above.
• Search the documentation for your error message or scenario.
• If you’re still having trouble, reach out for support with your logs and a description of your setup.
• If still not working, please don't hesitate to Contact us

With careful review and the help of AI tools, most issues can be quickly identified and resolved!