You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Call to protected method ApiPlatform\\Doctrine\\Orm\\Filter\\SearchFilter::splitPropertyParts() from scope ApiPlatform\\Doctrine\\Orm\\Filter\\AbstractFilter
#6787
Description
When I try to filter by a relation, ie &relation.id=2 it throws this error. Yesterday it was working just fine, there hasn't been any changes related to this. Today it throws the error. Unexplicably. Running PHP 8.3.13
How to reproduce
This is what the ApiFilter attribute looks like
when I filter by year (simple filter) it works. but if I filter by a relation, for example municipality.id, it breaks.
Possible Solution
Additional Context
I tried on another computer, same PHP version, all the same, and it works. But in my current computer, where it was totally working yesterday, now it throws Call to protected method ApiPlatform\\Doctrine\\Orm\\Filter\\SearchFilter::splitPropertyParts() from scope ApiPlatform\\Doctrine\\Orm\\Filter\\AbstractFilter
The text was updated successfully, but these errors were encountered:
API Platform version(s) affected: 4.0
Description
When I try to filter by a relation, ie
&relation.id=2
it throws this error. Yesterday it was working just fine, there hasn't been any changes related to this. Today it throws the error. Unexplicably. Running PHP 8.3.13How to reproduce
This is what the ApiFilter attribute looks like
when I filter by year (simple filter) it works. but if I filter by a relation, for example
municipality.id
, it breaks.Possible Solution
Additional Context
I tried on another computer, same PHP version, all the same, and it works. But in my current computer, where it was totally working yesterday, now it throws
Call to protected method ApiPlatform\\Doctrine\\Orm\\Filter\\SearchFilter::splitPropertyParts() from scope ApiPlatform\\Doctrine\\Orm\\Filter\\AbstractFilter
The text was updated successfully, but these errors were encountered: