Hi,
I have reviewed the settings in your plugin All in One SEO and the AIOSEO ▸ Search Appearance ▸ Remove Query Args option is what was removing the required pagination url:

I disabled this setting and tested when logged out and the pagination is now working correctly.

Best regards,
Mike

Hi,
Thanks for the link to your site, I have not seen a custom menu item with a “search icon” option before:

the reason it only shows until the slider shows is because it is hidden by “display:none opacity:0” once the slider shows, this could be a “lazy load” conflict, I see that you are using JetPack & possibility so other plugins that could cause this, although I don’t know what the default behavior for FiboSearch is.
Try disabling your other plugins to ensure there is not a conflict, then check the FiboSearch options, if this doesn’t help try using the FiboSearch shortcode instead of the custom element.

Best regards,
Mike

Hi,
Thank you for your patience, I have just found this thread and have reviewed it, typically this situation is not typically covered by our support because sorting though what an agency has done to create your custom theme can be tricky.
As I recall back in july I was tring to assist you with a issue you were having, I updated your custom theme for you and left it as it was to hear back from you that all was well, as I recall many issues came up after the update and we worked on them, I don’t specific remember how it all ended, but nonetheless we are here now.
So I have changed your wp-config.php to define(‘DISALLOW_FILE_EDIT’, true); to allow the theme file editor to show again, and I have modified your “enfold-child” with your “Kropik Child” files then I activated your “enfold-child” and imported your “Kropik Child” theme settings, and cleared your cache a bunch of times and the new Enfold theme seemed to work while I was logged in, but not when I was logged out.
After much research it looks like the agency that created this theme for you created it is such a way the theme adds meta data to the WordPress database that is used for WPML to show the correct pages, I don’t fully understand the reason, but changing to the “Enfold” teme seems to break this and I don’t know how to move this meta data to the new Enfold database.
So I enabled the “Kropik Child” and your site is working correctly again.
Unfortunately I believe you will need to contenue to manuly update or to will need to hire a developer that understands what the original developer did and why, I have not seen this before.
Sorry that I couldn’t be more help.

Best regards,
Mike

Hey Silje,
Thank you for the link to your site, does your ‘FiboSearch’ plugin offer a shortcode to display the search field? If so you could add a header widget area for it, please see our documentation here. Another option mat be to add the ‘FiboSearch’ shortcode as menu item, in the navigation label.
Then to hide the default search icon you can disable it at Enfold Theme Options ▸ Main Menu ▸ General ▸ Append search icon to main menu

Best regards,
Mike

Hi,

Thank you for the inquiry.

You can modify or override the themes/enfold/searchform.php file in your child theme. Add the label element around line 24.

<label for="s">Search</label>
<input type="submit" value="<?php echo $icon; ?>" id="searchsubmit" class="button <?php echo $class; ?>" />
<input type="text" id="s" name="<?php echo $search_params['search_id']; ?>" value="<?php if( ! empty( $_GET['s'] ) ) { echo get_search_query(); } ?>" placeholder='<?php echo $search_params['placeholder']; ?>' />

Best regards,
Ismael

Hey Daniel Patriasz,
Thanks for your patience, try enabling the option at Enfold Theme Options ▸ SEO Support ▸ Search Engine Optimization Support ▸ Preprocessing Shortcodes In Header typically this helps but there are some limitations with the Yoast Pro plugin and the pages created with the Advanced Layout Builder.

Best regards,
Mike

Hey gatehealing,
Thanks for your patience, I see that the lazyload classes are present on the images, perhaps your caching plugin doesn’t recognize them, try disability your caching plugin and then check again, if this doesn’t help try following the Page Speed Insights recommendation of installing a lazy-load WordPress plugin and disable the theme lazyload option.
Another point could be that either your caching plugin or the option in the theme settings has disable jQuery Migrate or has deferred the loading of jQuery, this could prevent the teeme lazyload from working, so a good please to start testing would be to disable the caching plugin, and any other “optimizing” plugins, and then ensure the Enfold Theme Options ▸ Performance ▸ Load jQuery in your footer and Enfold Theme Options ▸ Performance ▸ Disable jQuery Migrate are not enabled.
and then check again to see if that helps.

Best regards,
Mike

Hi,
Thanks for the feedback and the link to your example site, it helped me by seeing what they have done. When I check the site I see the break point for the mobile menu is 992px, and the set the menu item width to 14.25% and the font is a little smaller.
So to show the burger menu until 991px we will use this css:

@media only screen and (min-width: 767px) and (max-width: 991px) {
  #top #header .av-main-nav > li.menu-item  {
      display: none!important;
  }
  #top #header .av-burger-menu-main.menu-item-avia-special  {
      cursor: pointer;
      display: block!important;
  }
  #top #header .av-main-nav > li > a {
  	background-color: transparent !important;
  }
  .html_header_top #top .av_menu_left .main_menu {
    right: 20% !important;
    left: auto !important;
  }
  .html_header_top .av_bottom_nav_header .av-logo-container .main_menu {
    display: block !important;
}
  #top #header_main_alternate {
	 display: none;
}
}

the expected results:

Then to set the main menu similar to the other site we will use this css:

@media only screen and (min-width: 992px) { 
.main_menu {
    display: flex;
    align-items: center;
}
.avia-menu>ul.av-main-nav {
    margin: 0;
    display: flex;
    justify-content: space-around;
    position: relative;
}
.avia-menu>ul.av-main-nav>li.menu-item {
    width: 14.25%;
    padding: 0;
}
.avia-menu>ul.av-main-nav>li.menu-item>a,
.avia-menu>ul.av-main-nav>li.menu-item>a span {
    display: flex;
    align-items: center;
    justify-content: center;
    width: 100%;
    padding: 0;
    font-size: 18px;
}
.avia-menu>ul.av-main-nav>li.menu-item .avia-menu-text,
.avia-menu>ul.av-main-nav>li.menu-item-search-dropdown {
	display: flex;
    justify-content: center;
}
#top #header_main_alternate .container {
    margin: 0 auto;
    padding: 0px 50px;
}
}
@media only screen and (min-width: 1200px) { 
.avia-menu>ul.av-main-nav>li.menu-item {
    margin: 0 13px;
}
}

the expected results 992px:

and at larger screens 1440px:

Please give this a try.
Please ensure to copy the code from the forum and not an email notification so the symbols are not converted.

Best regards,
Mike

Hey Oriano,
I tried searching for Motopress Hotel Booking Plugin but I didn’t find any results for using it with Enfold, I did find that they offer a free version: Hotel Booking Lite so assuming that it is built the same way, perhaps you can test with it and ask the plugin author if it works in the same way.

Best regards,
Mike

Hi,
You can remove the asterisc, that was only an example.
As for the URLs and SEO, I’m not a SEO expert so please research this, but I thought of two options, when you use the Classic Editor you can change the URL to something different than the page title, so I’m thinking that you can for example, change all of the “About” pages to use the URL slug of /about so the language switcher will work, and leave the titles in the appropriate language, like this:

you would need to do this for each language.
Or you can use a redirect plugin and manually add your pages and the corresponding page for each language, here is an example from the plugin page:

you would need to do this for each language, but all of these redirects will be “301” and I’m not sure if this is bad for SEO, it may be.
All in all, either of these will be a lot of work, if it was my site I think that I would just use the original menu and assume that if someone landed on the EN site and they really wanted the FR site, that they would be fine with going to the FR homepage. But I probably have not thought about it as much as you have.
I hope this helps.

Best regards,
Mike