[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[4.x]: Relational field exists condition #16203

Closed
dusan-stojnic opened this issue Nov 25, 2024 · 4 comments
Closed

[4.x]: Relational field exists condition #16203

dusan-stojnic opened this issue Nov 25, 2024 · 4 comments
Labels
bug craft4

Comments

@dusan-stojnic
Copy link

What happened?

Description

When trying to filter element index with relational field has a value condition, an error occurs.

Steps to reproduce

  1. Navigate to any element index where elements field layout has relational field.
  2. Try to filter out elements where that relational field has a value

Expected behavior

Get a list of elements that match condition

Actual behavior

Server error occurred flash message

Craft CMS version

4.13.3 & 4.12.9

PHP version

8.2.20 & 8.2.23

Operating system and version

Linux 5.15.167.4-microsoft-standard-WSL2 & Linux 6.1.0-23-amd64

Database type and version

MariaDB 10.4.34 & MySQL 8.0.39

Image driver and version

Imagick 3.7.0 (ImageMagick 6.9.11-60)

Installed plugins and versions
@dusan-stojnic
Copy link
Author

While checking, I found that namespace is missing from some parts of the query in existsQueryCondition method in BaseRelationalField. Adding the namespace fixes the error, but there were still no results.

@i-just
Copy link
Contributor
i-just commented Nov 25, 2024

Hi, thanks for reaching out! I can’t replicate this behaviour. Could you enable safeMode and check if the issue persists? Could you please check the logs (storage/logs/web*.log) and share the stack trace for this error?

@dusan-stojnic
Copy link
Author

After trying safeMode and some more debugging, figured out it was one of the plugins that caused the issue, sorry for the hassle.

@i-just
Copy link
Contributor
i-just commented Nov 26, 2024

Thanks for the update. Glad you got to the bottom of it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug craft4
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@i-just @dusan-stojnic