select2_ajax is adding _text on search filter

[smzapp]

Using "backpack/crud": "^6.7", Script Model is expected to have more than 100k records. Therefore, to execute filter should be done using ajax request and not just a dropdown. However, when I select from the ajax result, it appends _text on the URL affecting the search result. How to fix this?

// Crud Controller

    protected function filterScriptByFields()
    {
        $this->crud->addFilter([
            'name' => 'script_number',
            'type' => 'select2_ajax',
            'label' => 'Script Number',
        ], tenant_url('/script/fetch?field=script_number'), function ($value) {
            $this->crud->addClause('where', 'script_number', $value);
        });

// OtherController

    public function fetchScript(Request $request)
    {
        $term = $request->input('term'); // from select2
        $field = $request->input('field');
        $query = Script::query();

        if ($term) {
            $query->where($field, 'like', '%'.$term.'%');
        }

        return $query->get()->pluck('id', 'script_number');
    }

// Model

class Script extends Model
{}

[backpack-ai-bot[bot]]

The issue you're experiencing—where the select2_ajax filter appends a _text parameter to the URL (e.g., script_number_text)—is a known behavior in Backpack. This can cause artifacts in the URL and potentially affect your filtering logic or results.

Why does this happen?

Backpack's select2_ajax filter, when a value is selected, appends both the value and its display text (with a _text suffix) to the URL. This is intended for display purposes but can interfere with filtering if not handled properly.

How to fix or mitigate this

1. Ignore the _text parameter in your filter logic

When defining your filter's callback, ensure you only use the actual value (not the _text parameter) for filtering. Your current code already does this, so you are safe on this front.

2. Remove artifacts from the URL

Backpack maintainers have addressed this issue in recent updates. Specifically, PRs and issues (remove select2_ajax filter artifacts left behind in url, Select2 filter fixes) have fixed the problem where _text artifacts remain in the URL after clearing or changing filters.

Solution:

• Make sure you are using the latest version of Backpack CRUD (at least 4.2 or higher, or the version where the fix was merged).
• If you are on an older version and cannot upgrade, you can manually patch the filter JavaScript to ensure it removes the _text parameter when the filter is cleared or changed.

3. Example: Defensive filter callback

If you want to be extra safe, you can check for null or empty values in your filter callback:

$this->crud->addFilter([
    'name' => 'script_number',
    'type' => 'select2_ajax',
    'label' => 'Script Number',
], tenant_url('/script/fetch?field=script_number'), function ($value) {
    if ($value) {
        $this->crud->addClause('where', 'script_number', $value);
    }
});

This ensures that only valid values are used for filtering, and any _text parameter is ignored.

4. Upgrade and test

If you still see _text artifacts after clearing filters, upgrade Backpack to the latest version, as this has been fixed in recent releases remove select2_ajax filter artifacts left behind in url.

---

Summary:

• The _text parameter is a known artifact; it should not affect filtering if your callback only uses the value.
• Upgrade Backpack to the latest version to ensure this artifact is properly removed from the URL.
• If you cannot upgrade, ensure your filter logic ignores the _text parameter and consider patching the JS as per the PRs above.

References:
remove select2_ajax filter artifacts left behind in url
Select2 filter fixes

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): select2_ajax Filter issue
Github Issue (closed): [Bug] select2_ajax filter and select2_from_ajax field pagination not working
Github Issue (closed): Ajax for select2
Github Issue (closed): [Bug] Clear Filters doesn't reset 'setModel'
Fetch Operation PRO|Using FetchOperation with select2_ajax filter
Filters PRO|Select2_ajax Part 2
allow select2 ajax filter to work with fetch operation
Github Issue (closed): filter on name doesnt work in select2_ajax
Github Issue (closed): select2_from_ajax not working when editing existing record
Github Issue (closed): [Bug] select2_from_ajax_multiple not clearing searched string on select
Github Issue (closed): [4.0.58] select2_ajax filter breaks "Remove filters" button (again)
Select2 filter fixes
remove select2_ajax filter artifacts left behind in url