I’m all for more details in supports requests, but this is not a bug issue on the repo. From @pamtbaau’s well-sourced reply and the original post, we can infer the following:
- Grav is throwing a fatal error, which we know and love as the “Crikey!” dumps.
- From the other post, Linux on GoDaddy, incidentally shared.
- From the second sentence and original post, this is a raw installation of Grav + Admin (previously just Grav). The error would not occur on an upgrade unless PHP changed in between.
- On all pages where Grav spawns a session, by default it does it everywhere.
- Permission-lock PHP’s temp-folders, or change their location.
- “Bug” is visible everywhere and always, unless sessions are disabled.
- Lines 5-7 of the original post.
- Probably, particularly the permissions set on
/home/content/86/4795186/tmp/ and php.ini in use by the PHP that runs Grav.
That level of detail, whilst helpful for a deep debug, is a bit over the top for something that should be quickly recognized as a PHP-issue. The keys being “Crikey!”, meaning Grav refuses to continue, the
session_start() error, and the information
No such file or directory.
@k64 The aforementioned permissions in the docs should be examined, and if that does not help you need to find out why PHP cannot create or write to its temporary-folders. If you are unfamiliar with configuring PHP, or do not have access to it on your shared hosting (which is uncommon), contact your host. Even GoDaddy once upon a blue moon gets on of its technicians in for a helping hand.