- Issue created by @Chris64
- Status changed to Needs review
10 months ago 10:16pm 31 January 2024 - Status changed to Active
10 months ago 2:45pm 1 February 2024 - πΊπΈUnited States smustgrave
Don't see anything to review.
But will need steps to reproduce this issue.
Will also have to do some research about why that variable is empty, hopefully the steps help with that. Usually just putting an isset() could be masking a larger issue
- Status changed to Postponed: needs info
9 months ago 1:31pm 22 February 2024 - π«π·France Chris64 France
Usually just putting an isset() could be masking a larger issue
Agree with this principle. And the other part.
Original code reinstalled. But the problem does not happen any where. Therefore not possible for me actually to get more information about the issue...
- π¨πSwitzerland saschaeggi Zurich
This happens to me as well on 11.x-dev and the proposed solution seems to fix the problem
- πͺπΈSpain marcoscano Barcelona, Spain
I was kind of able to reproduce this by installing the Minimal profile, then applying a recipe that enabled gin + gin_toolbar + navigation (and imported config '*' from the navigation module).
- π¨π¦Canada laura.j.johnson@gmail.com Toronto
I am also running into this by installing the Minimal profile and then applying a recipe that enables gin + gin_toolbar + navigation and importing config '*' from the navigation module.
- π¬π§United Kingdom dakala Fairford, Glos
Same setup here - minimal profile, recipe with gin etc. Until this morning, everything was fine. Then I noticed I'd been using the dev version of gin, so I upgraded to the RC. Immediately, my site was broken with the error in this issue. A search for the error brought me here. When I reverted back to the dev version of gin, the error was gone. Perhaps gin is the source of this?