devchris79
devchris79
How strange, we recently had a problem throwing an error on that same line. For us it turned out that the .htaccess file was missing some lines and the cache...
I can revert to the default built in cache from the backend flush the cache and everything works fine, then I removed the htaccess entry and it fell back to...
I appear to have some errors relating to when the issue occured in /pub/error_log (I didn't even know that file was there before now) ``` [02-Aug-2022 09:56:16 UTC] PHP Warning:...
I think the fix from @Hexmage in #35812 would sort the issue.
@richardreen, I think @Hexmage has a small error from his suggested fix in the other issue thread, he is missing a closing bracket from the if statement: > Fix is...
@Hexmage I just had this issue, I initially tried the fix you suggested but it still reported errors for me. I got to the root for my instance, we use...
@Hexmage It would certainly seem that is the case. I am guessing the data provider function getConfigData isn't retrieving an intended null. Maybe the data array element is there but...
@Hexmage Do you now have an additional entry in your env.php? Something like: , ‘cache’ => [ ‘graphql’ => [ ‘id_salt’ => ‘SALTHERE’ ] ]
@Hexmage I think your original fix is what's required, I think that I had two issues going on at the same time with Litespeed cache loss provoking your issue.
@richardreen, I think @Hexmage has a small error from his suggested fix below, he is missing a closing bracket from the if statement: > Fix is changing line 89 from...