Closed RyanDrewniak closed 1 year ago
jackmcdade
commented
1 year ago Hey there, this error usually is because an entry is referencing a blueprint or an entry link that doesn't exist anymore. You can check out this other issue here where they were able to track it down: https://github.com/statamic/cms/issues/8374
RyanDrewniak
commented
1 year ago It was really strange to debug. The problem was related to a switch from the default "Posts" collection to a new "Blogs" collection. There were indeed old references to the old "posts" blueprint that was since changed to "blogs".
Strangely though, the issue did not appear when editing those posts which would have used that blueprint. They appeared on a completely unrelated collection editing flow and with the physical output of the non-broken collection on the front end.
I can confirm that this problem is indeed user/developer error and not a bug.
Thank you so much @jackmcdade for the flag and support, here! I really appreciate it!
jackmcdade
commented
1 year ago Happy to help! Can you explain that completely unrelated collection editing flow so we can fix the error there too (like we did where you expected to run into an issue)?
RyanDrewniak
commented
1 year ago Happy to help! Can you explain that completely unrelated collection editing flow so we can fix the error there too (like we did where you expected to run into an issue)?
As part of the starter kit that I had implemented, there was a "Posts" collection, with a blueprint specific to it. As part of the project, I was renaming "Posts" to "Blogs", but had missed the blueprint identification change on each of the posts (I changed the blueprint name to "blogs" but failed to update the individual content entry files).
The issue only became present when:
If there was a more verbose/explicit indication of the content ID up-front, that could perhaps have made it easier to track down the core issue.
My take-away for long term support is: when making changes to collection & blueprint names, ensure that the corresponding content entry files also reflect those name changes. In short, update all of the following:
resources / blueprints / collectionscontent / collectionscontent / collections (i.e. content / collections / blogs / my-first-post.md)Additionally, this process becomes substantially more intricate when dealing with multisites that have pre-existing content. Doing full code repo/folder search & replace checks will save lots of headaches.
Bug description
I've moved a site to a new folder structure (just updated the folder name for the webroot directory where my Statamic site is set up), and now I'm getting the following error when trying to view the front-end of the site(s), and when trying to edit the entries in the collections:
Call to a member function field() on nullI'm able to access the control panel, I can edit the blueprints, but the collections appear to be inexplicably borked.
Here's where the stacktrace error seems to be coming from:
Call to a member function field() on null {"userId":"18fe6c9b-c5a9-4f9c-a238-0b79ca5de81f","exception":"[object] (Error(code: 0): Call to a member function field() on null at /var/www/ssc-multisite/vendor/statamic/cms/src/Entries/Entry.php:519)I tried clearing running:
php artisan cache:clearphp artisan config:clearphp please stache:clearDoes anyone know where I'm going wrong?
How to reproduce
Call to a member function field() on nullerrorCall to a member function field() on nullerrorLogs
Environment
Installation
Starter Kit using via CLI
Antlers Parser
runtime (new)
Additional details
This should just be a basic 5 site multisite installation, using the Landtamic starter kit