Reporting Bugs

All bugs and issues are tracked via GitHub Issues:

github.com/ADamCarraway/journalphp/issues

Before Creating an Issue

• Make sure the issue reproduces on the latest version from the repository (git pull).
• Search existing issues — the bug may already be known.
• Confirm it is actually a bug, not a configuration question — those are best asked in issues too.

What to Include in a Report

1. Problem Description

What happened? What was expected? How does the actual behavior differ from the expected?

2. Steps to Reproduce

Describe the sequence of actions that leads to the bug. The more precise, the easier to fix.

1. Go to /...
2. Click "..."
3. Fill in "..." with "..."
4. Observe the error

3. Environment

Parameter	Example
Deployment method	docker-compose.yml or docker-compose.prod.yml
Version / commit	git log --oneline -1
Browser	Chrome 124, Firefox 126, Safari 17
OS / Platform	macOS 14, Ubuntu 22.04

4. Logs

Attach a relevant log snippet:

• Laravel: storage/logs/laravel.log
• Containers: docker compose logs app
• Horizon: /horizon → Failed jobs (access configured in admin → Access, /admin-panel/system/access)
• Browser console: DevTools → Console (especially for frontend errors)

5. Screenshots

If helpful, attach a screenshot or screen recording — especially for visual bugs.

How to Write a Good Title

❌ Doesn't work
❌ Error when publishing
✅ Publish button unresponsive when post contains a poll block

A good title is already half the solution.

Feature Requests

Feature suggestions are also accepted through Issues. Add the enhancement label (if available) and explain why this is needed and how it should work.