Forum Replies Created

Viewing 15 replies - 1 through 15 (of 601 total)
  • Hi @snowdragon97!

    Here’s the updated code that now supports both desktop and mobile menus. Although it will eventually be integrated into the FiboSearch core, I don’t have a confirmed release date at this time. In the meantime, please apply it separately to all websites.

    @media (min-width: 960px) {
    #menu-footer-menu {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-pack: end;
    -ms-flex-pack: end;
    justify-content: flex-end;
    }
    }

    @media (max-width: 959px) {
    .menu-primary ul.menu-smart a.dgwt-wcas-enable-mobile-form {
    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    bottom: 0;
    }

    .dgwt-wcas-search-wrapp {
    margin: 0;
    padding: 5px 36px;
    }
    }

    Best regards,
    Kris

    Hi @snowdragon97!

    I noticed that when I use a special browser add-on and paste my code into the custom CSS section, the search box changes the background color. This confirms that the CSS code is correct.

    You might want to try adding the code directly in your theme’s CSS & JS settings, as your current theme may not fully support the native WordPress solution. To do this, navigate to:

    1. WP Admin → Uncode → Theme Options → CSS & JS
    2. Then, paste the provided CSS code into the CSS field.

    For further guidance, here’s a link to the theme documentation that explains this option in more detail:
    Uncode CSS & JS Documentation

    Best regards,
    Kris

    Hi @leebrewerftl!

    Here’s what you can do more:

    1. Backup your database
    2. Try to use a plugin called Database Collation Fix. This should convert tables to the right format. As the author says:

    The Database Collation Fix tool converts database tables using ‘utf8mb4_unicode_520_ci’ or ‘utf8_unicode_520_ci’ Collation Algorithms to a more portable ‘utf8mb4_unicode_ci’ collation on a once daily basis. It also modifies any column-specific collation statements, not just the default table collation. This means that you can install this plugin and it will continue to monitor all of your database tables and convert them to the more portable Collation Algorithm automatically.

    Dave Jesch

    If the above steps don’t resolve the issue, you can always contact your hosting provider for assistance. They can analyze the database, identify the problem, and potentially fix it for you.

    Best regards,
    Kris

    Hi @shandysuta!

    I checked the code from the mentioned topic, and it’s still working as expected. It correctly sorts products by date. Please ensure the following:

    1. The code is placed in the functions.php file of your child theme or added as a Snippet in the Code Snippets plugin.
    2. You are using the free version of FiboSearch, as this code does not work in the premium version.

    If the above code still doesn’t work for you, try this alternative:

    add_filter( 'dgwt/wcas/search_results/output', function( $output ) {
    if ( isset( $output['suggestions'] ) ) {
    usort( $output['suggestions'], function ( $a, $b ) {
    if ( isset( $a['type'] ) && $a['type'] == 'product' &&
    isset( $b['type'] ) && $b['type'] == 'product' ) {

    $date_a = get_post_field( 'post_date', $a['post_id'] );
    $date_b = get_post_field( 'post_date', $b['post_id'] );

    return strtotime( $date_b ) - strtotime( $date_a );
    }

    return 0;
    } );
    }

    return $output;
    } );

    The implementation process remains the same as described above.

    Best regards,
    Kris

    Hi @mhabeeb!

    Thanks for reporting this. We will fix it in a future version. When it is ready, we will let you know in this thread.

    Best regards,
    Kris

    Hi @riffraffno!

    The latest version of the plugin (v1.30.0) fixes the issue with FiboSearch and the Flatsome theme on mobile. Just update to the newest version, and it should work fine now.

    Best regards,
    Kris

    Hi @leebrewerftl!

    This issue arises because the query utilizes the LIKE operator with text containing special characters, such as SOCとは, which are part of the utf8mb4 character set.

    To resolve this problem, verify the database configuration in the wp-config.php file to ensure it is correctly set. Specifically, check the following:

    define( 'DB_CHARSET', 'utf8mb4' );
    define( 'DB_COLLATE', 'utf8mb4_unicode_ci' );

    Best regards,
    Kris

    Hi @atlantis1525!

    You’re correct, the category archive page is not controlled by FiboSearch. It’s likely managed by the Elementor page builder. I recommend checking Elementor templates, particularly those for Product Category, Shop, or Product Archive. These categories are styled as H3 within the .page-description class, so you should find them in the Elementor template.

    It’s also worth checking Appearance → Widgets, your theme/child theme, or Code Snippets, as the content might be placed there.

    In the meantime, here’s a quick CSS fix that will hide the element until you find the proper solution:

    .post-type-archive-product .woocommerce-products-header .page-description {
    display: none !important;
    }

    Let me know if you manage to fix the problem!

    Best regards,
    Kris

    Hi @snowdragon97!

    Have you set the color in WooCommerce → FiboSearch → Search Bar (tab) → Other Colors (section)? Please refer to this screenshot for guidance. Make sure to update the settings there first.

    However, remember that your theme might still override the background settings. To ensure the background displays correctly, you can use the following CSS:

    html:not(.dgwt-wcas-overlay-mobile-on) .dgwt-wcas-style-pirx.dgwt-wcas-style-pirx-compact .dgwt-wcas-sf-wrapp input[type=search].dgwt-wcas-search-input {
    background: #0a0a0a !important;
    }

    Paste it into Appearance -> Customize -> Additional CSS. If you aren’t familiar with custom CSS, take a look at this video.

    Best regards,
    Kris

    Hi @teszilla!

    We tried integrating FiboSearch with GTranslate but ran into two major issues:

    1. GTranslate doesn’t store translations in a database. They’re generated on the fly, so we can’t operate on the dynamic data. Even the GTranslate plugin author acknowledges this in their article.
    2. GTranslate doesn’t allow any control over its translations. We often got strange or nonsensical results, making it impossible to use effectively.

    Best regards,
    Kris

    Hi @snowdragon97!

    Use the following CSS to resolve the issue:

    #menu-footer-menu {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: end;
    -ms-flex-pack: end;
    justify-content: flex-end;
    }

    Paste it into Appearance -> Customize -> Additional CSS. If you aren’t familiar with custom CSS, take a look at this video.

    Best regards,
    Kris

    Hi @snowdragon97!

    It appears you are using the default version of the search bar on the mobile version, which may not provide optimal performance. I recommend switching to the “Overlay on Mobile” feature, specifically designed for mobile devices. Here are its key benefits:

    • Better search experience
    • More streamlined UX
    • Easy to find suggestions and results
    • Minimalistic layout compliant with many modern designs

    How to activate it?
    To activate this feature, please go to WooCommerce → FiboSearch → Search bar → scroll down to the “Appearance” section

    You can read more about FiboSearch Mobile Overlay here.

    To enhance the user experience with our mobile overlay, consider relocating the search engine from the mobile menu to the header. Embedding it as a magnifying glass or search icon (positioned next to the main menu icon) would provide more intuitive access. Here’s a screenshot to illustrate the idea.

    Let me know if the described solution works for you and if you need help moving the search engine to the header.

    Best regards,
    Kris

    Hi @trevellfr!

    Yes, I believe this is necessary for FiboSearch to function properly. However, the amount of CSS involved isn’t substantial. In fact, nearly all of it is actively used, and the FiboSearch styles file itself is compact, minified, and weighs just 37 KB.

    Best regards,
    Kris

    Hi @atlantis1525,

    It seems this issue might be caused by the HUSKY Filter plugin. By default, the search page is /search/?s=vint&post_type=product&dgwt_wcas=1. However, after applying any sorting option, it redirects to the subpage /swoof/name-vint/?s=vint&post_type=product&dgwt_wcas=1&orderby=date.

    To resolve this, please check the plugin settings under WooCommerce -> Products Filter -> Advanced -> Options. Try setting the “Disable swoof influence” option to “Yes” and see if it fixes the issue. For reference, here’s a screenshot.

    Let me know how it goes!

    Best regards,
    Kris

    Hi @valletinformatique44!

    By default, FiboSearch calculates product scores using several factors, which determine their ranking in the autocomplete list. A higher score results in a higher position. Based on the Baymard Institute’s guidelines and recent UX research, we generally recommend not altering the default sorting in autocomplete. This approach ensures a user-friendly and intuitive experience.

    However, if you choose to customize the product sorting, you can do so by using dgwt/wcas/search_results/output the filter. The below example shows how to sort products by results alphabetically (A-Z).

    // Sort search results alphabetically
    add_filter( 'dgwt/wcas/search_results/output', function( $output ) {
    if ( isset( $output['suggestions'] ) ) {
    usort( $output['suggestions'], function ( $a, $b ) {
    if ( isset( $a['type'] ) && $a['type'] == 'product' &&
    isset( $b['type'] ) && $b['type'] == 'product' ) {
    if ( $a['value'] != $b['value'] ) {
    return $a['value'] <=> $b['value'];
    }
    }
    });
    }

    return $output;
    } );

    You have two ways to add this code to your theme:

    1. Open the functions.php in your child theme and add the code at the end.
    2. or install the Code Snippets plugin and apply this code as a snippet.

    Best regards,
    Kris

Viewing 15 replies - 1 through 15 (of 601 total)