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

Fatal Error in XAMPP setup #3627

Closed
dwainehohne opened this issue Dec 5, 2017 · 10 comments
Closed

Fatal Error in XAMPP setup #3627

dwainehohne opened this issue Dec 5, 2017 · 10 comments

Comments

@dwainehohne
Copy link

dwainehohne commented Dec 5, 2017

On what page in the application did you find this issue?

After running the setup

On what type of server is this running? Dedicated / Shared hosting? Linux / Windows?

XAMPP - macOS

What version of PHP is the server running?

7.1.1.11

What browser (and version) are you running?

Safari 10.0.3

What version of SQL Server are you running?

?

What version of ChurchCRM are you running?

2.9.1

Receiving error message reading:
Fatal error: Uncaught Exception: An invalid configuration name has been requested: bHSTSEnable in /opt/lampp/htdocs/churchcrm/ChurchCRM/dto/SystemConfig.php:310 Stack trace: #0 /opt/lampp/htdocs/churchcrm/Include/Header-Security.php(24): ChurchCRM\dto\SystemConfig::getBooleanValue('bHSTSEnable') #1 /opt/lampp/htdocs/churchcrm/Include/HeaderNotLoggedIn.php(4): require_once('/opt/lampp/htdo...') #2 /opt/lampp/htdocs/churchcrm/Include/LoadConfigs.php(31): require('/opt/lampp/htdo...') #3 /opt/lampp/htdocs/churchcrm/Include/LoadConfigs.php(70): system_failure('Could not conne...') #4 /opt/lampp/htdocs/churchcrm/Include/Config.php(61): require_once('/opt/lampp/htdo...') #5 /opt/lampp/htdocs/churchcrm/index.php(6): require_once('/opt/lampp/htdo...') #6 {main} thrown in /opt/lampp/htdocs/churchcrm/ChurchCRM/dto/SystemConfig.php on line 310

I am not clued up on code at all so would appreciate any help I can get.
Thanks

@crossan007 crossan007 self-assigned this Dec 5, 2017
@crossan007
Copy link
Contributor

Please check the contents of src/ChurchCRM/dto/SystemConfig.php - specifically line 221 - It should have the bHSTSEnable setting.

Alternatively, please try removing and unzipping the application again - it's possible a file was corrupted.

@crossan007 crossan007 added this to the User Support milestone Dec 5, 2017
@pedrofveloso
Copy link

pedrofveloso commented Jan 13, 2018

@dwainehohne follow the steps 18, 19, 20 and 21 of this tutorial https://github.com/ChurchCRM/CRM/wiki/Installing-xampp-for-ChurchCRM
Use the same password you used to configure the churchCRM, at database tab.
If you dont remember the password you used to setup the database, just configure your mysql password following those steps... and after that go to .../htdocs/Include/Config.php and set the USER and PASSWORD values with the same credentials you used to configure your mysql.

I hope it helps.

God bless you all

@crossan007
Copy link
Contributor

crossan007 commented Jan 13, 2018

@pedrofveloso so, are you saying that a misconfigured database will cause the bHSTSEnable setting to throw an error?

@pedrofveloso
Copy link

@crossan007 Apparently yes... i'm not 100% sure, because PHP is not my speciality... but that solution worked, here.

After configure the database the error did not happened anymore. Then I could see the login screen and use the ChurchCRM.

I tried this because I thought it was very strange to put a database password (at churchCRM setup screen) without setting another previously in phpmyadmin.

@estefanodesign
Copy link

I have similiar problem

After running the setup

Receiving error message reading:
Fatal error: Uncaught Exception: An invalid configuration name has been requested:
bHSTSEnable in C:\xampp\htdocs\churchcrm\ChurchCRM\dto\SystemConfig.php:308 Stack trace:
#0 C:\xampp\htdocs\churchcrm\Include\Header-Security.php(24): ChurchCRM\dto\SystemConfig::getBooleanValue('bHSTSEnable')
#1 C:\xampp\htdocs\churchcrm\Include\HeaderNotLoggedIn.php(4): require_once('C:\xampp\htdocs...')
#2 C:\xampp\htdocs\churchcrm\Include\LoadConfigs.php(31): require('C:\xampp\htdocs...')
#3 C:\xampp\htdocs\churchcrm\Include\LoadConfigs.php(75): system_failure('Could not conne...')
#4 C:\xampp\htdocs\churchcrm\Include\Config.php(61): require_once('C:\xampp\htdocs...')
#5 C:\xampp\htdocs\churchcrm\index.php(6): require_once('C:\xampp\htdocs...') #6 {main} thrown in C:\xampp\htdocs\churchcrm\ChurchCRM\dto\SystemConfig.php on line 308

server to running
XAMPP - Windows

PHP Ver.
7.1.9

What browser (and version) are you running?
Google Chrome
Version 63.0.3239.132 (Official Build) (64-bit)

Database server
Server: 127.0.0.1 via TCP/IP
Server type: MariaDB
Server version: 10.1.26-MariaDB - mariadb.org binary distribution
Protocol version: 10
User: churchcrm@localhost
Server charset: UTF-8 Unicode (utf8)

Web server
Apache/2.4.27 (Win32) OpenSSL/1.0.2l PHP/7.1.9
Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: b396954eeb2d1d9ed7902b8bae237b287f21ad9e $
PHP extension: mysqliDocumentation curlDocumentation mbstringDocumentation
PHP version: 7.1.9

phpMyAdmin
Version information: 4.7.4, latest stable version: 4.7.7

ChurchCRM ver.
2.10.3

Thanks for solution

@boluak
Copy link

boluak commented Jan 24, 2018

Have you followed the steps outlined by @crossan007 and @pedrofveloso above?

@estefanodesign
Copy link

@boluak Yes i have except 'bHSTSEnable setting', cause i don't get it.
But the problem still appear

@boluak
Copy link

boluak commented Jan 25, 2018

Seems your mysql server is not running or you are unable to login.
Pls run xampp control to confirm this.. See this link for help.
https://github.com/ChurchCRM/CRM/wiki/Installing-xampp-for-ChurchCRM

@boluak
Copy link

boluak commented Jan 25, 2018

screenshot_20180125-125407

@crossan007
Copy link
Contributor

I think that this is a "first run issue" and will go away after the database schema has been installed.
Option 1) manuallyrun the install.SQL file against your database with PHPMyAdmin (or command line)
Option 2) Temporarily comment out line 4 of HeaderNotLoggedIn.php so that Header-Security is not used

@DawoudIO DawoudIO modified the milestones: User Support, 2.10.4 Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants