bvfbarten Posted June 1, 2023 Share Posted June 1, 2023 Hi, I just did a fresh install of 3.0.218 twice and received this error message both times. Using php -S localhost:8000 as my server. I am using php version 8.2.6 on ubuntu. Note, I did install 3.0.210 and it worked. I was at the point of the install where I set an admin user, and tell it to delete the install files, I received this error message. Hmm… Fatal Error: Uncaught Error: Call to a member function get() on null in wire/modules/Inputfield/InputfieldSelector/InputfieldSelector.module:625 #0 wire/modules/Inputfield/InputfieldSelector/InputfieldSelector.module (1819): InputfieldSelector->sessionSet() #1 wire/core/Inputfield.php (435): InputfieldSelector->setAttribute() #2 wire/modules/Inputfield/InputfieldSelector/InputfieldSelector.module (224): Inputfield->__construct() #3 wire/core/Modules.php (700): InputfieldSelector->__construct() #4 wire/core/Modules.php (1211): Modules->newModule() #5 wire/core/Modules.php (1023): Modules->loadModule() #6 wire/core/Modules.php (407): Modules->load() #7 wire/core/ProcessWire.php (557): Modules->init() #8 wire/core/ProcessWire.php (315): ProcessWire->load() #9 index.php (52): ProcessWire->__construct() #10 {main} thrown (line 625 of wire/modules/Inputfield/InputfieldSelector/InputfieldSelector.module) This error message was shown because: site is in debug mode. ($config->debug = true; => site/config.php). Error has been logged. 1 Link to comment Share on other sites More sharing options...
zoeck Posted June 1, 2023 Share Posted June 1, 2023 I have the same problem, freshly downloaded 3.0.218 DEV version @ryan is there a problem here with the current version? /edit: reverted to 3.0.217 DEV and it's working... 1 Link to comment Share on other sites More sharing options...
ryan Posted June 5, 2023 Share Posted June 5, 2023 @bvfbarten @zoeck I'm not sure why this error didn't appear in earlier versions, but the issue was that the InputfieldSelector module (when installed) was attempting to access the $session API variable before the API "ready" state. I noticed the same issue here and it should already be fixed in 3.0.219, though please let me know if you still run into an error. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now