-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call to a member function routeData() on null #10025
Comments
More insights:
Same on PHP 8.3 and 8.2. |
I've just upgraded from beta4 to 5.0.2 and now I'm seeing this same error in the CP where there was no error before. No error occured on a couple of empty collecitons. Clearing the stache fixed the issue and it's not reappeared... yet. |
@jasonvarga is there a known workaround for this? I'd like to start creating websites on v5 🙂❤️ |
I'm on 5.1.0 and had the same issue. Clearing the stache fixed the issue for me too. |
Clearing the stache ( |
We are having the same problem, our deploy script is very broken now. somehow it only happens on our production server (that should be identical to our staging server). not sure what is causing the difference yet |
I figured out that it happens when people try to access a statamic page in the time between |
I can confirm this. Had the same problem. After clearing the caching, you first need to wait for the Stache to warm. After that everything is working fine. |
Also having the same issues on 5.2.0 I upgraded from 4.51.0...everything >4.51.0 was causing this issue for me as well. I did however get it to load up once on 5.2.0 using The tree view times out loading but list view seems to be fine for me. |
Also hitting this same issue on v4.57.2. |
Fixes statamic#10025 Since the entry() method might return `null` calling `routeData()` would fail, because there was no `null`-check. This commit adds a null-check and also makes sure, that routeData always returns an array, which is required by the UrlBuilder.
Fixes statamic#10025 Since the entry() method might return `null` calling `routeData()` would fail, because there was no `null`-check. This commit adds a null-check and also makes sure, that routeData always returns an array, which is required by the UrlBuilder.
Really? That might help narrow things down. Can you post the stack trace? |
Fixes statamic#10025 Since the entry() method might return `null` calling `routeData()` would fail, because there was no `null`-check. This commit adds a null-check and also makes sure, that routeData always returns an array, which is required by the UrlBuilder.
Fixes statamic#10025 Since the entry() method might return `null` calling `routeData()` would fail, because there was no `null`-check. This commit adds a null-check and also makes sure, that routeData always returns an array, which is required by the UrlBuilder.
@jasonvarga Added below for you, as others have said it looks like a cache clear and stache warm fixed for me (at least i'm assuming it was that part of our deploy script).
|
What URL are you on when you get that error? |
@jasonvarga We were hitting this when viewing the "Experiences" collection on the "Yachting US" site, the collection wouldn't load at all and just fired the error. URL would have been something like this: https://pelorustravel.com/cp/collections/experiences?sort=order&order=desc&page=1&perPage=50&filters=eyJzaXRlIjp7InNpdGUiOiJ5YWNodGluZ191cyJ9fQ%3D%3D&columns=title%2Csite%2Cslug%2Cdate%2Cstatus |
Bug description
New v5 installation with statamic/cli.
Going to Collection Pages in the CP works fine the first time after a
php artisan cache:clear
, but on subsequent loads I get this error message.How to reproduce
Install Statamic 5.0.0.
Go to CP -> Collections -> Pages.
Reload the page.
Check the browser Dev Tools Network tab.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: