Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: minor: mod_rewrite presence not properly detected when using CGI instead of apache module #6910

Closed
grayeul opened this issue Mar 19, 2024 · 0 comments · Fixed by #6911
Closed

Comments

@grayeul
Copy link
Contributor

grayeul commented Mar 19, 2024

Description

If you are using a CGI interface for php ( e.g. php-fpm ) then the apache_get_modules() method is not available, and therefore the initial setup page falsely reports a problem because it cannot detect proper rewrite operation via mod_rewrite. This also shows up on a running server, in the Admin/Debug page -- as can be seen in the Softaculous dynamic demo.

  • ChurchCRM version: 5.6.0
  • PHP version the server running: PHP 8.1
  • DB Server and Version the server is running: MariaDB 10.3

Steps To Reproduce

This shows up immediately, if you are using php-fpm as a separate service to handle php.

Expected behavior

Since the apache server is properly handling processing of the .htaccess files, and rewriting in general, the expected behavior is not to falsely report an error.

Screenshots and/or logs

N/A

Debugging Steps

  • What has been done to debug the issue so far?
    • The error is due to the way mod_rewrite is being checked in AppIntegrityService.php
    • A potential fix (at least for some linux-hosted environments) is forthcoming.
@grayeul grayeul added the bug label Mar 19, 2024
@grayeul grayeul self-assigned this Mar 19, 2024
@grayeul grayeul linked a pull request Mar 19, 2024 that will close this issue
12 tasks
@DAcodedBEAT DAcodedBEAT added this to the 5.7.0 milestone May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants