-
Notifications
You must be signed in to change notification settings - Fork 78
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
After Taxonomies and terms switch to eloquent driver error occurs #354
Comments
Are you able to share the full stack trace for this error? |
Hi @duncanmcclean, here you go:
|
Yes, you're right it seems to be passing a site object instead of a handle. However whats strange is that none of those locale methods are touched by eloquent driver, we don't modify the localised term in any way so why you're seeing this on eloquent but not with file based terms is a bit of a mystery. Beyond the switch to eloquent is there anything further you have done to extend Statamic? As we are struggling to see the issue ourselves - are you able to provide a basic repository showing the issue that we can use to understand where the source of the problem is coming? |
"Beyond the switch to eloquent is there anything further you have done to extend Statamic?" No this was a simple page showing the categories. Unfortunately at this time I do not have the time to setup a basic repo. But I will do that as soon as I find the time for this. |
Apparently I had to put "taxonomy:" in front of categories. This is well explained in the v2 docs (https://v2.statamic.com/tags/taxonomy). Why everything worked before moving them to the database I don't know.
|
ok - so its working as expected now? |
Yes it is. |
Bug description
Illegal offset type in isset or empty. Seems somewhere an object is passed to OffsetExists in Collection?
How to reproduce
Switch tot eloquent driver for taxonomies and terms. The antlers code then leads to the error "Illegal offset type in isset or empty"
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: