Helix Quickpack Error During Setup (Warning: SessionHandler::read()) - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Helix Quickpack Error During Setup (Warning: SessionHandler::read())

E

Ernst

Helix Framework 2 years ago

Hello

I'm trying to install the newest version of the Helix Quickpack. Unfortunately I get the following error:

Warning: SessionHandler::read(): open(/*valid-path-to-config-files*/sess_2b2779716840adb3ee956eceda30d813, O_RDWR) failed: No such file or directory (2) in /*path-to-my-helix-installation*/libraries/vendor/joomla/session/src/Storage/NativeStorage.php on line 478

Warning: session_start(): Failed to read session data: user (path: /*valid-path-to-config-files*) in /*path-to-my-helix-installation*/libraries/vendor/joomla/session/src/Storage/NativeStorage.php on line 478

It seems that the Joomla setup included in the Helix Quickpack is looking for a dedicated session file which doesn't exist.

Must say, that installing a plain Joomla on the server is without troubles.

Any idea what the reason could be for that? Reminds me of a problem with other Quickpack installs where a user with a certain ID can't be found. Looks to me like there are settings from a developer environment that do not exist on the target system.

But in the end, I have no idea, which is why I'm glad for support.

Ernst

0
2 Answers
E
Ernst
Accepted Answer
2 years ago #114296

After the hosting provider was initially unable to help, further clarification revealed that the problem was after all related to CPanel and the support for multiple PHP versions on the same hosting.

So the problem is almost solved.

Well, almost, because at the end of the installation you still get the error message "Installation failed", but if you ignore that and log into the Joomla backend, everything works as it should.

Therefore, this support request can be considered as solved.

0
Mehtaz Afsana Borsha
Mehtaz Afsana Borsha
Accepted Answer
Support Agent 2 years ago #114350

Hi

Thanks for contacting us and glad to know that it is solved. You can now close this post by accepting the answer.

-Regards.

0