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
Since updating to Craft 5.5, element queries using :notempty: for Link field params no longer work as expected – i.e. a query like craft.entries.section('news').someLinkField(':notempty:').all() that would return entries with a value in a Link field someLinkField prior to 5.5, no longer returns any entries.
I tested this on Craft 5.4.10.1 as well, so it appears to be an unintended change in 5.5?
Steps to reproduce
Create a Link field with the handle someLinkField (all settings at their defaults) and add it to an entry type's field layout
Create an entry and give it a value for the Link field (I set the Link field type to "URL" and added a URL like https://www.example.com. Save the entry.
Hi, thanks for reporting! If you need to get past that quickly, you can resave the elements that use the Link field. For example: php craft resave/all --with-fields=someLinkField.
What happened?
Description
Since updating to Craft 5.5, element queries using
:notempty:
for Link field params no longer work as expected – i.e. a query likecraft.entries.section('news').someLinkField(':notempty:').all()
that would return entries with a value in a Link fieldsomeLinkField
prior to 5.5, no longer returns any entries.I tested this on Craft 5.4.10.1 as well, so it appears to be an unintended change in 5.5?
Steps to reproduce
someLinkField
(all settings at their defaults) and add it to an entry type's field layouthttps://www.example.com
. Save the entry.Expected behavior
Passing
:notempty:
to a Link field query param should return entries with a value in that field.Actual behavior
No entries are returned.
Craft CMS version
5.5.0.1
PHP version
8.2.24
Operating system and version
14.6.1 (DDEV v1.23.5)
Database type and version
MySQL 8.0.36
Image driver and version
No response
Installed plugins and versions
None
The text was updated successfully, but these errors were encountered: