This website uses cookies to personalize your experience. By using this website you agree to our cookie policy.

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Live search: wrong ordering #47504
    Ideaz20Ideaz20
    Participant

    You cannot access this content.

    Ideaz20Ideaz20
    Participant

    Hi,

    IE8 support is turned off, so no more segfaults. I’m attaching the backtrace. IMHO the loop might be unavoidable if search shortcode is in searchform.php because of the way get_search_form() function works. Maybe add a warning to the IE8 toggle?

    Best regards

    in reply to: Frontend Search Settings: Any post type #31306
    Ideaz20Ideaz20
    Participant

    Hello,

    installed, but it doesn’t correctly splice the values. The code should probably be:

    array_splice( $this->values, $position, 0, array($new) );

    If the last value is not an array it is typecasted to one which means that the structure is not preserved.

    Here is one last question about the original problem: is it possible to also override parameters for the search page results? Ajax load works great, but on search page the above filter seems to be ignored.

    Best regards

    in reply to: Frontend Search Settings: Any post type #31300
    Ideaz20Ideaz20
    Participant

    Hello,

    thanks! This works perfectly.

    While trying to set a position for this item, we have discovered a possible bug. If you set position parameter to anything, it will throw an Warning:

    Warning: array_splice() expects parameter 1 to be array, null given in /ajax-search-pro/includes/classes/frontend/filters/class-asp-filter.php on line 64

    $original is NULL

    This issue is present in 4.20.3

    Best regards

    in reply to: Frontend Search Settings: Any post type #31287
    Ideaz20Ideaz20
    Participant

    Hello,

    ok, that’s unfortunate.

    One of the ideas was also changing options to radio buttons and adding a filter to asp_pre_get_front_filters with:

    array(
                    'field' => 'cpt',
                    'value' => 'any', // or '', or 'post_type1,post_type2,post_type3'
                    'label' => 'Any',
                    'default' => true,
                   'selected' => true
    )

    But none of this is recognized and it just fallbacks to “post”. Is there anything else we can try in the value field, or it just allows single value with one of the post_types selected in source?

    Best regards

Viewing 5 posts - 1 through 5 (of 5 total)