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
Describe the bug
Running a findImages GQL query using image_filter.title doesn't appear to return any results. I've tried a number of modifiers includes EQUALS, INCLUDES, INCLUDES_ALL (not supported), and MATCHES_REGEX, but no results are returned.
To Reproduce
Steps to reproduce the behavior:
Go to Stash playground.
Run a findImages query by title for an image that you've confirmed exists in your database.
Confirm the result count is zero.
Screenshots
The first screenshot shows the image with the given title does exist in the database.
The second screenshot shows searching for one of those images by title doesn't work. The same thing happens for INCLUDES (pictured), EQUALS, and MATCHES_REGEX.
Stash Version: 0.27.2:
Docker:
OS: Synology NAS
Browser Chrome
Version 133
The text was updated successfully, but these errors were encountered:
The option to set the basename as the title during a scan was removed in the files refactor. Now it is always left as null during the scan, which will return the basename in the graphql query. The titleFromFilename plugin can set the basename as the title if that is behavior you want.
Describe the bug
Running a
findImages
GQL query usingimage_filter.title
doesn't appear to return any results. I've tried a number of modifiers includes EQUALS, INCLUDES, INCLUDES_ALL (not supported), and MATCHES_REGEX, but no results are returned.To Reproduce
Steps to reproduce the behavior:
findImages
query by title for an image that you've confirmed exists in your database.Screenshots
The first screenshot shows the image with the given title does exist in the database.
The second screenshot shows searching for one of those images by title doesn't work. The same thing happens for INCLUDES (pictured), EQUALS, and MATCHES_REGEX.
Stash Version: 0.27.2:
Docker:
The text was updated successfully, but these errors were encountered: