We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
feat: Integrate GitHub Discussions for community support - Update Help.md with 12 GitHub Discussions links as primary support channel - Add GitHub Discussions link to Home.md support section - Update Troubleshooting.md to redirect users to Discussions for help - Add 'Help vs Bug Reports' section to Bug-Reporting-and-Diagnostics.md - Add Discussion header banner to FAQs.md - Create GitHub-Discussions-Setup.md with complete setup guide - Create DISCUSSIONS-IMPLEMENTATION-SUMMARY.md with implementation details GitHub Discussions configured with 6 categories: - General Questions - Installation Issues - User Support - Administrator Questions - Developer Questions - Troubleshooting This separates community support questions from bug reports, improving issue triage and community engagement. Wiki documentation now consistently directs users to appropriate Discussion categories based on their question type. 19 total Discussion links added throughout wiki. Ready for GitHub repository admin to enable Discussions in settings.
docs: remove all references to PHP versions before 8.2 - Removed all mentions of PHP 7.0, 7.1, and other pre-8.2 versions from documentation - Updated ChurchCRM-Application-Platform-Prerequisites.md to clarify PHP 8.2+ is absolute minimum - Added 'Tested Versions' section documenting verified PHP versions (8.2, 8.3, 8.4) - Referenced GitHub Actions CI workflow for complete test matrix - Simplified Install---Self-Hosted-Linux.md and Installing-on-CentOS-7.md to only show PHP 8.2+ instructions - Removed legacy/end-of-life notes that referenced old PHP versions Documentation now presents PHP 8.2+ as the only supported version with no references to obsolete versions
docs: consolidate system requirements and remove version hardcoding - Create comprehensive ChurchCRM System Requirements page as single source of truth - Update PHP requirement from 8.1 to 8.2 across all documentation - Update database requirement to MySQL 5.7+ or MariaDB 10.2+ - Remove all hardcoded version numbers from non-prerequisite documentation - All docs now reference ChurchCRM-Application-Platform-Prerequisites.md - Remove outdated references to PHP 7.x and old database versions - Simplify installation instructions to be version-agnostic - Reduce maintenance burden by centralizing all version specifications Files changed: - ChurchCRM-Application-Platform-Prerequisites.md: Comprehensive new requirements guide - Installation.md, Home.md, Quick-Start.md: Point to requirements file - Development.md, Docker.md: Generic references with anchor links - Self-Hosting-on-Linux.md, Install---Self-Hosted-Linux.md: Updated with generic refs - Self-Hosted-on-RockyLinux.md: PHP 8.2 installation command - Installing-on-CentOS-7.md, Installing-LAMP-and-ChurchCRM-on-Azure.md: Generic version refs - FAQs.md: Remove outdated PHP 7 upgrade FAQ
Reformat
Due to the frequency of questions about security keys missing from config.php and how to set up maps in ChurchCRM, they have been added to the FAQ.
Grammatical correctness
Linked the new file permissions page in so we have a single canonical source of truth.
Amended file permissions to reflect the same instructions as the 500 error page.
Fixed formatting for default user/password.
Added note about the default user/password - we see this question often on Gitter chat :)
More small typos fixed. Sorry :(
Small typo fixed
Closes Issue #4152
Revert "Added FAQ for managing the letterhead/logo" This reverts commit 14deb821e1ddc896c364bcf4d9a67f82daec6b64.
Added FAQ for managing the letterhead/logo
Updated FAQs (markdown)
Created FAQs (markdown)