Viewing 30 results - 361 through 390 (of 7,502 total)
  • Author
    Search Results
  • #1425789

    The following is located in the WooCommerce -> Status Logs. Adding what is related to Enfold. The error log is very long through the day. There are a bunch of error logs for each day.
    I believe these are related to PHP 8.1. (PHP 8.0?

    I appologize but this entry is very very long showing most of the errors seen in the error long related to Enfold.

    2023-11-16T10:36:19+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/logoslider/logoslider.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php on line 742

    2023-11-16T10:50:11+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/gallery_horizontal/gallery_horizontal.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T10:50:14+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-combo.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/widgets/class-widget-loader.php:180
    Stack trace:
    #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): aviaFramework\widgets\avia_widget_loader->handler_widgets_init()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 /home/L/labhusetno/www/wp-includes/widgets.php(1858): do_action()
    #4 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): wp_widgets_init()
    #5 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #6 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #7 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #8 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #9 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #10 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #11 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #12 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/widgets/class-widget-loader.php på linje 180)

    2023-11-16T10:58:19+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/search/search.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T11:04:24+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/framework/php/class-megamenu.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php:195
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/framework/avia_framework.php(38): require()
    #1 /home/L/labhusetno/www/wp-content/themes/enfold/functions.php(247): require_once(‘/home/L/labhuse…’)
    #2 /home/L/labhusetno/www/wp-settings.php(611): include(‘/home/L/labhuse…’)
    #3 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #4 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #7 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 195

    2023-11-16T12:45:51+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/logoslider/logoslider.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-cron.php(46): require_once(‘/home/L/labhuse…’)
    #8 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php on line 742

    2023-11-16T12:46:58+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T12:47:06+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/gallery_horizontal/gallery_horizontal.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T12:47:12+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/framework/php/class-megamenu.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php:195
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/framework/avia_framework.php(38): require()
    #1 /home/L/labhusetno/www/wp-content/themes/enfold/functions.php(247): require_once(‘/home/L/labhuse…’)
    #2 /home/L/labhusetno/www/wp-settings.php(611): include(‘/home/L/labhuse…’)
    #3 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #4 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #7 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 195

    2023-11-16T12:47:58+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttonrow/buttonrow.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T12:48:03+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php:190
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/framework/avia_framework.php(38): require()
    #1 /home/L/labhusetno/www/wp-content/themes/enfold/functions.php(247): require_once(‘/home/L/labhuse…’)
    #2 /home/L/labhusetno/www/wp-settings.php(611): include(‘/home/L/labhuse…’)
    #3 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #4 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #7 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 190

    2023-11-16T16:53:19+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/leaflet_maps/leaflet_maps.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php on line 742

    2023-11-16T16:53:19+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:682
    Stack trace:
    #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #4 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #8 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php on line 682

    2023-11-16T17:40:48+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-element-manager.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:682
    Stack trace:
    #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #4 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #8 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 682

    2023-11-16T18:47:12+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/team/team.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T21:42:52+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttonrow/buttonrow.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-cron.php(46): require_once(‘/home/L/labhuse…’)
    #8 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php on line 742

    2023-11-16T21:59:02+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/base-classes/class-modal-base.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:682
    Stack trace:
    #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #4 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #8 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 682

    2023-11-16T21:59:10+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/icon_circles/icon_circles.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:742
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(698): AviaBuilder->autoloadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #9 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 742

    2023-11-16T22:00:39+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/framework/php/class-breadcrumb-trail.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php:227
    Stack trace:
    #0 /home/L/labhusetno/www/wp-content/themes/enfold/framework/avia_framework.php(38): require()
    #1 /home/L/labhusetno/www/wp-content/themes/enfold/functions.php(247): require_once(‘/home/L/labhuse…’)
    #2 /home/L/labhusetno/www/wp-settings.php(611): include(‘/home/L/labhuse…’)
    #3 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #4 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #7 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 227

    2023-11-16T22:08:32+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/includes/helper-post-format.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/functions.php:829
    Stack trace:
    #0 /home/L/labhusetno/www/wp-settings.php(611): include()
    #1 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #2 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #3 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #4 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #5 {main}
    thrown in /home/L/labhusetno/www/wp-content/themes/enfold/functions.php on line 829

    2023-11-16T22:37:11+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-svg-shapes.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php:682
    Stack trace:
    #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): AviaBuilder->loadLibraries()
    #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 /home/L/labhusetno/www/wp-settings.php(643): do_action()
    #4 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’)
    #5 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’)
    #6 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’)
    #7 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’)
    #8 {main}
    thrown i /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php på linje 682

    • This reply was modified 2 years, 5 months ago by SHR Design. Reason: Adding more information
    thinkjarvis
    Participant

    Hi guys,
    I now have the full superspeedy pack from WP Intense which includes a lot of database modifications.

    They also encourage you to set as many non-essential WP_Options with Autoload YES to Autoload NO to speed up all uncached actions on a site.
    https://www.wpintense.com/knowledgebase/managing-your-wp_options-table/

    I have had to do an extensive review of transients generated by plugins and also items that auto load. The speed difference from optimising wp_options in the backend and front end on large sites is massive.

    I want to apply this same method to Enfold theme itself.

    If you run the following SQL command you can see Enfold typically has over 100 – 150 autoloaded functions.

    select left(option_name,15) option_name, count( * ) total
    from wp_options where autoload = 'yes'
    group by left(option_name,15)
    order by total desc
    limit 100;

    (Note you need to change wp_ to your database prefix if it isnt wp_)

    You can also then run:

    SELECT * FROM wp_options where option_name like 'av_alb_usage_av%';
    SELECT * FROM wp_options where option_name like 'av_alb_usage_av%' and autoload = 'yes';

    and
    DELETE FROM
    or
    UPDATE

    av_alb_usage_av has over 100 options:

    av_alb_usage_av_blog
    av_alb_usage_av_button
    av_alb_usage_av_button_big
    av_alb_usage_av_buttonrow
    av_alb_usage_av_buttonrow_item
    av_alb_usage_av_catalogue
    av_alb_usage_av_catalogue_item
    av_alb_usage_av_cell
    av_alb_usage_av_cell_four_fifth
    av_alb_usage_av_cell_one_fifth
    av_alb_usage_av_cell_one_fourth
    av_alb_usage_av_cell_one_full
    av_alb_usage_av_cell_one_half
    av_alb_usage_av_cell_one_third
    av_alb_usage_av_cell_three_fifth
    av_alb_usage_av_cell_three_fourth
    av_alb_usage_av_cell_two_fifth
    av_alb_usage_av_cell_two_third
    av_alb_usage_av_codeblock
    av_alb_usage_av_comments_list
    av_alb_usage_av_contact
    av_alb_usage_av_contact_field
    av_alb_usage_av_content_slide
    av_alb_usage_av_content_slider
    av_alb_usage_av_countdown
    av_alb_usage_av_feature_image_slider
    av_alb_usage_av_font_icon
    av_alb_usage_av_four_fifth
    av_alb_usage_av_fullscreen
    av_alb_usage_av_fullscreen_slide
    av_alb_usage_av_gallery
    av_alb_usage_av_gmap_location
    av_alb_usage_av_google_map
    av_alb_usage_av_heading
    av_alb_usage_av_headline_rotator
    av_alb_usage_av_horizontal_gallery
    av_alb_usage_av_hr
    av_alb_usage_av_icon_box
    av_alb_usage_av_icongrid
    av_alb_usage_av_icongrid_item
    av_alb_usage_av_iconlist
    av_alb_usage_av_iconlist_item
    av_alb_usage_av_image
    av_alb_usage_av_image_hotspot
    av_alb_usage_av_image_spot
    av_alb_usage_av_layerslider
    av_alb_usage_av_layout_row
    av_alb_usage_av_magazine
    av_alb_usage_av_mailchimp
    av_alb_usage_av_mailchimp_field
    av_alb_usage_av_masonry_entries
    av_alb_usage_av_masonry_gallery
    av_alb_usage_av_metadata_item
    av_alb_usage_av_notification
    av_alb_usage_av_one_fifth
    av_alb_usage_av_one_fourth
    av_alb_usage_av_one_full
    av_alb_usage_av_one_half
    av_alb_usage_av_one_third
    av_alb_usage_av_partner
    av_alb_usage_av_partner_logo
    av_alb_usage_av_player
    av_alb_usage_av_playlist_element
    av_alb_usage_av_portfolio
    av_alb_usage_av_post_metadata
    av_alb_usage_av_postcontent
    av_alb_usage_av_postslider
    av_alb_usage_av_product_button
    av_alb_usage_av_product_info
    av_alb_usage_av_product_meta
    av_alb_usage_av_product_price
    av_alb_usage_av_progress
    av_alb_usage_av_progress_bar
    av_alb_usage_av_promobox
    av_alb_usage_av_rotator_item
    av_alb_usage_av_row
    av_alb_usage_av_section
    av_alb_usage_av_sidebar
    av_alb_usage_av_slide
    av_alb_usage_av_slide_accordion
    av_alb_usage_av_slide_full
    av_alb_usage_av_slideshow
    av_alb_usage_av_slideshow_accordion
    av_alb_usage_av_slideshow_full
    av_alb_usage_av_social_share
    av_alb_usage_av_submenu
    av_alb_usage_av_submenu_item
    av_alb_usage_av_tab
    av_alb_usage_av_tab_container
    av_alb_usage_av_tab_section
    av_alb_usage_av_tab_sub_section
    av_alb_usage_av_table
    av_alb_usage_av_team_icon
    av_alb_usage_av_team_member
    av_alb_usage_av_testimonial_single
    av_alb_usage_av_testimonials
    av_alb_usage_av_textblock
    av_alb_usage_av_three_fifth
    av_alb_usage_av_three_fourth
    av_alb_usage_av_timeline
    av_alb_usage_av_timeline_item
    av_alb_usage_av_toggle
    av_alb_usage_av_toggle_container
    av_alb_usage_av_two_fifth
    av_alb_usage_av_two_third
    av_alb_usage_av_video
    av_alb_usage_avia_sc_search

    and there are also other autoloaded options from the theme including:
    avia_stylesheet
    avia_gutenberg_
    avia_options_th
    widget_avia-ins
    avia_woocommerc

    Plus others possibly in your installation vs mine.

    Would it be possible to review these options and make it so those that only run in the back end of wordpress are set to Autoload = NO
    Would it also be possible to provide a list of those that can safely be set to NO? I can then run an SQL command to set them to NO:

    Like this:
    update wp_options set autoload = 'no' where option_name like 'av_alb_usage_av_animated_numbers%' and autoload = 'yes';

    Transients Review

    SELECT option_name AS name, option_value AS value
    FROM LkxroSS_options
    WHERE option_name LIKE ‘%transient_%’
    ORDER BY option_name

    Anything Enfold auto generates that shouldnt be autoloaded?

    • This topic was modified 2 years, 5 months ago by thinkjarvis.
    • This topic was modified 2 years, 5 months ago by thinkjarvis.
    #1425641

    Hi,

    The search bar displays consistently on our end across different sizes. Did you subscribe to a CDN provider? Please try to temporarily disable it or try to check the site on a different device.

    I’m not sure as to the exact process?

    You can disable the file compression settings temporarily (Enfold > Performance > File Compression), just to make sure that the updated resources are loaded. Please refer to the documentation below for more details.

    // https://kriesi.at/documentation/enfold/optimization/#css-and-js-merging

    Best regards,
    Ismael

    #1425579

    thanks for the link :

    First: you had the wrong language defintiton on your page – for a good hyphenation you should have your lang set for the main language on your page.
    guess it is:lang="da-DK"
    (alway click to enlarge the images)

    Next: this is justified text layout ! – you can see the rule for it here:

    i told you in the other topic that it is alway difficult to have a nice word distance without breaking the words on justified text.
    if you do not like to justify the text get rid of that part inside:

    #top .fullsize .template-blog .post .entry-content-wrapper {
      text-align: left;   /****** this part is set to justify in your css *****/
      font-size: 1.15em;
      line-height: 1.7em;
      max-width: 800px;  /****** see comment under this codeblock *****/
      margin: 0 auto;
    }

    the 800px ( or 40em ) max-width is a default setting from enfold – if this is what you mean in your e-mail talking about:

    it’s stuck in the center regardless of the CSS I apply

    then you can avoid that by:

    #top #wrap_all .fullsize .template-blog .post .entry-content-wrapper,
    #top #wrap_all .fullsize .template-blog .post .entry-content-wrapper > * ,
    #top #wrap_all .fullsize .template-blog .post-title {
      max-width: unset !important;
      margin: 0;
    }

    if you like to preserve the justification of your paragraph texts – then a hyphens: auto will mainly solve that issue:
    (those ugly underlined spaces inside block : “for______Search_____Engine”)

    #top #wrap_all .fullsize .template-blog .post .entry-content-wrapper p {
      text-align: justify;
      -webkit-hyphens: auto;
      hyphens: auto !important;
      text-justify:  distribute;
      word-spacing: -0.05em !important;
      text-align-last: left;
    }

    but: as mentioned above the hyphenation only works well if the lang attribute on html is set to the language of your texts.
    F.e. the word “Søgemaskineoptimering” does not hyphen on small screens.

    #1425578
    Thomas
    Participant

    Hi Kriesi-Team,

    The Appearance > Widgets panel on our page is not loading/working correct. The complete right side of the panel, where the widgets content should appear, remains empty.
    This error is already a year old, but it hasn’t bothered me so far since the frontend is not affected. I searched your support page but was not lucky this time.
    Please find the Error message below:

    WordPress version 6.4.1
    Active theme: Enfold 5.6.8 child
    PHP version 8.0.30
    ————–
    An error of type E_ERROR was caused in line 368 of the file /XXX/wordpress/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-newsbox.php. Error message: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in /XXX/wordpress/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-newsbox.php:368
    Stack trace:
    #0 /XXX/wordpress/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-newsbox.php(368): strip_tags()
    #1 /XXX/wordpress/wp-includes/class-wp-widget.php(535): aviaFramework\widgets\avia_newsbox->form()
    #2 /XXX/wordpress/wp-admin/includes/widgets.php(276): WP_Widget->form_callback()
    #3 /XXX/wordpress/wp-includes/widgets.php(837): wp_widget_control()
    #4 /XXX/wordpress/wp-admin/includes/widgets.php(119): dynamic_sidebar()
    #5 /XXX/wordpress/wp-admin/widgets-form.php(477): wp_list_widget_controls()
    #6 /XXX/wordpress/wp-admin/widgets.php(34): require(‘…’)
    #7 {main}
    thrown
    ——————–

    I’ve added link and login in private
    Thanks for your help.
    Thomas

    #1425282

    Hey ballindigital,

    Please try the following in Quick CSS under Enfold->General Styling:

    @media only screen and (max-width: 767px) {
    #searchform {
      background: #fff;
    }
    }

    Best regards,
    Rikard

    #1425179

    Thank you for your help Mike! I sent a message to FiboSearch and was told the following.

    – Make sure that Enfold Theme Options -> Main Menu -> Append Search Icon To Main Menu (is toggled off).

    – FidoSearch bar is added through Appearance -> Menus. To the location it is to be in.
    (Menu item options be sure to have Layout: Search bar selected.)

    WooCommerce -> FiboSearch -> Starting tab. Make sure that Search bars Replace them is not checked. As this is not meant to replace the Enfold search, but to replace it.

    WooCommerce -> FiboSearch -> Search bar. I clicked to use the Show submit button. I also used the style Solaris. Use layout Search bar.

    FiboSearch support gave me the following CSS. I added some additional code.

    /* Fra Fibiosearch  support 9 nov 2023. */
    /* Overriding default Enfold code. */
    .menu-item .dgwt-wcas-search-wrapp {
      opacity: 1 !important;
      display: block !important;
    }
    
    .dgwt-wcas-search-input {
      margin-bottom: 0 !important;
    }
    
    .menu-item .dgwt-wcas-search-form {
      margin-bottom: 0 !important;
    }
    
    /* Search field. */
    #menu-item-3327 {
      height: 90px;
      display: flex;
      align-items: center;
    }
    
    /* Search field. 6 nov Joachim. */
    #top .header_color .input-text, #top .header_color input[type='text'], #top .header_color input[type='input'], #top .header_color input[type='password'], #top .header_color input[type='email'], #top .header_color input[type='number'], #top .header_color input[type='url'], #top .header_color input[type='tel'], #top .header_color input[type='search'], #top .header_color textarea, #top .header_color select {
        border: 1px solid lightgrey;
        background: white;
    }
    
    /* Search button. 6 Nov Joachim. */
    .dgwt-wcas-search-wrapp .dgwt-wcas-sf-wrapp .dgwt-wcas-search-submit, .dgwt-wcas-om-bar .dgwt-wcas-om-return {
        background-color: #f7f7f7;
        color: #0f0f0f;
        border-top: 1px solid lightgrey;
        border-right: 1px solid lightgrey;
        border-bottom: 1px solid lightgrey;
    }

    I added so much detail so that others whom might come across this thread might also want to try out FiboSearch.
    The result is seen here: https://labhuset.no/

    The site is slow to show results so that is something I will need to look into.

    #1425169
    Yuli
    Participant

    Does anyone know what the CSS is to style the woocommerce search bar (that searches for products only) to look the same as the default enfold search box which I have disabled as it is returning posts not products?

    I would like the woocommerce search to look identical with a little magnifying glass search icon rather than a button below saying “search”

    Thank you

    #1425136
    Marc
    Participant

    Hello together,

    We are utilizing the tab section element on our website but the height option “auto adjust to content” does not seem to work properly.
    All tab sections still have the same height as the tab section with the most content (see private content section).
    We have also tried to completely redesign the section from scratch but with no luck at all.
    After some research we have found quite a few topics on this issue but mostly from older Enfold versions (between 2017-2019), so it seems that the issue had been fixed in some former release.
    We are running Enfold 5.6.8 on PHP 8.2.12.

    How can this be fixed?

    Best regards,
    Marc

    #1425134

    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:
    Enfold_Support_3879.jpeg
    I disabled this setting and tested when logged out and the pagination is now working correctly.

    Best regards,
    Mike

    #1425021

    Hi FW,

    Please try to check Relevanssi Search
    In their Advanced Features, it lists: “Log queries, show most popular queries and recent queries with no hits.” maybe it would help.
    To integrate Relevanssi with our theme, please check our documentation: https://kriesi.at/documentation/enfold/search/#use-relevanssi-in-search-instead-of-the-default-search
    Hope it helps.

    Best regards,
    Nikko

    #1424985
    FW
    Participant

    Hi,

    is there a way to save the search requests on the website? I think it could be very interessting to take a look at searches on our website.

    “did you make sure to select it as both the heading and body font”
    Yes, I did, as I wrote in my initial posting.

    I think I set all elements in (Enfold > General Styling and) Enfold > Advanced Styling to the uploaded font.
    But as every element needs to be picked individually for editing it is not straight forward to stay on top of things. Therefore could you please let me know where to find the respective css files which are modified by these two UI configurations? It would be easier to search for the font names in an editor.

    Best Regards,
    ABIX

    #1424810

    Hi,
    Thanks for the link to your site, I have not seen a custom menu item with a “search icon” option before:
    Enfold_Support_3855.jpeg
    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

    #1424780

    Hi Mike

    The following seems like the easiest method.

    1-
    I turned off Append Search Icon To Main Menu in the Enfold Theme Options.

    2-
    WooCommerce -> FiboSearch -> Starting.
    Turned off the Search bars to replace Enfold with the FidoSearch.

    3-
    Added the Custom Link FiboSearch bar to the menu her.
    Used Layout: Default. Menu Style: Default.

    Results. Search field or Search icon can for a very short moment be seen to the left of the top menu here. Just to the left of the Hjem / Home menu item.
    https://labhuset.no/

    I do not know what is going on there.

    #1424736

    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

    #1424719

    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

    #1424712
    SHR Design
    Participant

    Hi

    I have been looking through various threads in the matter of changing the default search magnifying class icon with a search field/bar but the various solutions I have found have not worked.

    Including an Enfold setting to instead use the search field would be helpful.

    This is the site: https://labhuset.no/
    It uses: Enfold Version: 5.6.8
    WordPress: 6.3.2
    WooCommerce version 8.2.1

    I have installed and activated: “FiboSearch – AJAX Search for WooCommerce” to make search show up with more details as well as be able to get WooCommerce categories, tags, content etc into the search.

    I now need to be able to show the Search field instead of the Search icon in the header where the icon can be seen today. https://labhuset.no/

    Thank you!

    #1423684
    Thina
    Participant

    Hi

    I have a compatibility problem with BestWebSoft Plugin pdf&print plugin.

    To check out I deactivated Enfold and all plugins except BestWebSoft Plugin pdf&print and activated twenty-twenty.
    Than I activated the plugins one by one – BestWebSoft Plugin pdf&print still worked
    only after activating Enfold the problem occurred again.

    With the shortcode [bws_pdfprint display=’pdf,print’] on a page I get a “Not found” search result when I click on the pdf icon on the page
    and when I click the print icon just the headline is printed instead of the content.

    Best regards
    Bettina

    • This topic was modified 2 years, 5 months ago by Thina.
    #1423585

    Well with your Alias name and a little search i found your page ;)
    and on FAQ everything works fine here in OSX Chrome

    Edit :
    . You are right. I see – if you open the 5th or 6th toggle there are again this behavior.
    Can you please remove the interims solution with toggle_wrap set to display: none
    and refresh all cachings and merging please after that.

    I had to inspect where we can correct this. – on the enfold page https://kriesi.at/themes/enfold-2017/elements/accordion/ it works as i said as expected.

    #1423363

    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

    molinesupport
    Participant

    I’m building a bookshop
    Which will present 1000’s of books

    I have connected WooCommerce with the Book Importer as we use BatchLine for stocking supply:
    BCS BatchLine Book Importer (Its working well)

    The import creates 2 custom fields (relevant to my question) main_image and thumbnail_image both populated with url values.
    The Main image appears correctly within a product page.

    However I am trying to work out how I can update the relevant file for the grid, slider, and list Enfold features. I believe from research Enfold is using the shop thumbnail image? I can’t quite work out the structure and if I could develop the files to pull in the url from a Custom Field – thumbnail_image. I assume this is not a function.php solution but developing some code. Can anyone give me any points on how the code is even structured. It looks like it takes information for the html rendering from the WooCommerce files. Batchline inform me it works fine with the shopfront WooCommerce theme, so if anyone who’s the difference, I would be very grateful.

    Best Regards C

    #1422550

    In reply to: Enfold & SEO

    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

    #1422522

    hm – I have never attached any particular importance to it. But you are indeed right. It seems that the base.css (line 470ff) setting of the font is used there. It’s listed as HelveticaNeue, Helvetica etc. Since Enfold stores the fonts you set in options as a variable, you can set here:

    #top .input-text, 
    #top input[type="text"], 
    #top input[type="input"], 
    #top input[type="password"], 
    #top input[type="email"], 
    #top input[type="number"], 
    #top input[type="url"], 
    #top input[type="tel"], 
    #top input[type="search"], 
    #top textarea, 
    #top select {
    	font-family: var(--enfold-font-family-body) !important
    }

    or if you like to change it only for that input field:

    #top #s {
      font-family: var(--enfold-font-family-body) !important
    }

    maybe this should be changed on default to inherit the font like all the other settings ( line 20ff)
    (html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, etc. )

    #1422507
    kaneljeff
    Participant

    Two questions:

    1. I am starting from the Enfold Gym demo and noticed that the Main Menu search box does not following my font settings. Is there a way to force the search box to use the Body Text Font?

    2. I noticed in the demo that hovering on the Main Menu items turns the button background a different color (red)? That does not work for my site no matter how I configure the Logo Area colors. How can I make this work on my site?

    Thank you.

    • This topic was modified 2 years, 6 months ago by kaneljeff.
    • This topic was modified 2 years, 6 months ago by kaneljeff.
    • This topic was modified 2 years, 6 months ago by kaneljeff.
    santanin
    Participant

    Good day, I am using the most recent version of Enfold and the most recent version of WordPress and all my plugins are up to date.

    I just received an email from Google Search Console saying there’s a new reason preventing my videos from being indexed. When I log into my Google Search Console and investigate further, it says there’s a problem on my website with the “Video outside the viewport.

    The description Google gives on its website is:
    “The video must appear in the viewport when loading the page to be considered for indexing. Move the video so that the entire video is inside the renderable area of the page and seen when the page loads. The videos on these pages aren’t indexed or served on Google as video results.”

    I’m using your Avia Layout Builder and just basic layout options for 1 column or 2 columns, and your basic video media element for a video I have on my YouTube channel. On some pages I have videos in one column, and on some pages, I have videos in a 1/2 column. Both pages where I have a video in either 1 column or in a 1/2 column are getting flagged by Google saying that the video is outside the viewport, and as a result, Google is not indexing the video, which is very important to my client.

    What should I do to ensure the videos are not outside the viewport to ensure Google indexes them properly? Like I said, I’m using very basic elements of your Avia Layout Builder. I’m not doing anything complex or using any custom code, I’m using 1 or 2 column layouts and just dragging the video media element inside them.

    I included a few pages that Google said have the “video outside the viewport” in the private section of this message.

    Any help would be greatly appreciated.

    #1422066

    Topic: Tags problem and other

    in forum Enfold
    Yaphoon
    Participant

    Hi there,
    I want a help in below

    1.The home page head
    The right 中文 in square. When in hover, the words color change to same color of square.
    Can I change the square color or words color in hover

    I want to add a search in head, I forget where to add. Could you advise.

    2.

    FAQ

    pls sea the sidebar. I want to remove the words below picture and no line outside picture and no change when hover. Where can I set?

    The products categories
    I set categories, I think it is a post categories, so it doesn’t show anything. May I set as portfolio instead of categories.

    3. the tag cloud does not work
    Both in sidebar and footer, could you help

    4.in foot, how can I delete “Enfold Theme by Kriesi”

    Thanks and best regards,

    Wang

    #1421847

    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:
    Enfold_Support_3634.jpeg
    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:
    Enfold_Support_3636.jpeg
    and at larger screens 1440px:
    Enfold_Support_3638.jpeg
    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

    i think that the additional classes inside text-block element will come from a plugin. If you search for those extemely specific class like : min-h-[20px] i only found that tailwind css from https://tailpress.io/
    Did you build the site on an existing installation – and possibly change the theme to Enfold afterwards?
    The loading of jQuery in the footer could be set on Enfold on the settings page: performance
    This is of course possible, but then you have to take into account that the scripts that need jQuery are loaded afterwards. This can be achieved, for example, by first not loading the scripts in the head area and then setting a correspondingly higher priority number for the function.

    Next: do you really need jQuery Migrate ? – same on performance tab

Viewing 30 results - 361 through 390 (of 7,502 total)