Skip to content

[BUG] Trim colon from binds to prevent Named parameter "text_ma_xxx" does not have a bound value error on matchAgainst search #141

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

RayTM
Copy link

@RayTM RayTM commented Jul 25, 2025

While testing the matchAgainst strategy, i ran into the following error: Named parameter "text_ma_0" does not have a bound value. This results in the SearchFilter with matchAgainst being un-useable.

This seems to happen as the binds are getting added to the QueryBuilder. To fix this problem, the colon which is previously used for the parameter, needs to be removed before adding it to the Query.

Tested on macOS 15.5 with TYPO3 13.4.14 and PHP 8.3.

RayTM added 2 commits July 24, 2025 13:51
…not have a bound value` error on matchAgainst search
…y finished words, resulting in a wider range of results. Useful for searches, that need to include word combinations
@RayTM
Copy link
Author

RayTM commented Jul 25, 2025

I additionally added the option to use IN BOOLEAN MODE in my most recent commit. This was necessary for a use-case, where i needed to search for mutliple partially finished words, e.g. "key" which will now find key in itself and keyboard, but also other words enter in the search!

This is not actually related to the bug, if you don't see the need for extending the search, kindly disregard that! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant