Forum Replies Created

Viewing 30 posts - 1 through 30 (of 60 total)
  • Author
    Posts
  • in reply to: Missing Media Library images when inserting images #1464567

    I went to settings in Polylang and deactivated the Media module. All images now seem to be available.

    This might mean for different language plugins that one will need to turn OFF the media module if they have something like it is available. To be able to show all the images for multiple languages.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1427203

    Hi Nikko

    I adjusted the php option memory_limit to 512M. The same as is in the wp-config file.

    An important aspect of this is that the web host has not known how to handle the various fatal errors and other errors that have shown up when working in the backend. I do not believe the frontend has been impacted but it disturbs the flow when working on the site. The errors have become less over time but they do on occasion still show up. I have also noticed a general sluggish/slowness when working in the backend. This too has somewhat become better.

    in reply to: Not able to see stock overlay badge in WooCommerce #1427199

    Thank you very much!
    I did not even think about the z-index. That worked well!

    in reply to: E_ERROR in Enfold functions file as well as in other files #1427079

    I have made some updates.

    I added this to wp-config file.

    define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

    In the PHP options I changed many of the below values.

    allow_url_fopen (is on)
    error_reporting (E_ALL)
    max_execution_time changed from 30 to 90
    max_input_time changed from -1 to 2000
    memory_limit 128M (no change)
    open_basedir (is blank)
    post_max_size changed from 8M to 32M
    register_long_arrays (is off)
    short_open_tag (is on)
    upload_max_filesize changed from 4M to 64M

    The site seems better. I do on occasion notice new fatal errors. For instance I noticed a new fatal error which mentioned WP Rocket. I am in contact with support at WP Rocket and have brought it onward to them.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1425876

    (Adding a new post to the thread to reply to your question.)

    Hey Nikko
    “How much memory is allowed to you by your hosting provider based on the package you purchased/subscribed?”
    –> memory_limit is set to the max of 896M.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1425858

    Updating this reply.

    Hey Nikko
    “How much memory is allowed to you by your hosting provider based on the package you purchased/subscribed?”
    memory_limit is set to the max of 896M.

    —————————
    Original response below.
    ————-

    When editing a WooCommerce product using Enfold Avia Layout Editor I am seeing these dev console errors.
    My example is going to edit this product. https://labhuset.no/wp-admin/post.php?post=1722&action=edit&classic-editor

    Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args%5B%5D=undefined&args%5B%5D= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Dl (react-dom.min.js?ver=18.2.0:10:96134)
    at e (react-dom.min.js?ver=18.2.0:10:45699)
    at fr (react-dom.min.js?ver=18.2.0:10:54784)
    at js (react-dom.min.js?ver=18.2.0:10:120956)
    at wl (react-dom.min.js?ver=18.2.0:10:88659)
    at bl (react-dom.min.js?ver=18.2.0:10:88587)
    at yl (react-dom.min.js?ver=18.2.0:10:88450)
    at fl (react-dom.min.js?ver=18.2.0:10:85607)
    at Nn (react-dom.min.js?ver=18.2.0:10:32474)
    at al (react-dom.min.js?ver=18.2.0:10:82721)
    ar @ react-dom.min.js?ver=18.2.0:10

    Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘call’)
    at i (index.js?ver=8.3.0:2:431624)
    at 65792 (5792.js:1:2426)
    at Function.i (index.js?ver=8.3.0:2:431624)
    maps.googleapis.com/maps/api/mapsjs/gen_204?csp_test=true:1

    Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
    editor.min.js?ver=6.4.1:2

    Uncaught TypeError: Cannot read properties of undefined (reading ‘getSelection’)
    at editor.min.js?ver=6.4.1:2:2280
    at n (editor.min.js?ver=6.4.1:2:3384)
    at HTMLDocument.<anonymous> (editor.min.js?ver=6.4.1:2:248)
    at C (tinymce.min.js?ver=49110-20201110:2:10800)
    at HTMLDocument.d (tinymce.min.js?ver=49110-20201110:2:10946)
    at Object.trigger (jquery.min.js?ver=3.7.1:2:70435)
    at HTMLButtonElement.<anonymous> (jquery.min.js?ver=3.7.1:2:70726)
    at Function.each (jquery.min.js?ver=3.7.1:2:3129)
    at e.<computed>.each (jquery.min.js?ver=3.7.1:2:1594)
    at e.<computed>.trigger (jquery.min.js?ver=3.7.1:2:70701)
    plugin.min.js?ver=49110-20201110:1 Deprecated TinyMCE API call: <target>.onChange.add(..)
    editor.min.js?ver=6.4.1:2

    Uncaught TypeError: Cannot read properties of undefined (reading ‘getSelection’)
    at editor.min.js?ver=6.4.1:2:2280
    at n (editor.min.js?ver=6.4.1:2:3384)
    at HTMLDocument.<anonymous> (editor.min.js?ver=6.4.1:2:248)
    at C (tinymce.min.js?ver=49110-20201110:2:10800)
    at HTMLDocument.d (tinymce.min.js?ver=49110-20201110:2:10946)
    at Object.trigger (jquery.min.js?ver=3.7.1:2:70435)
    at HTMLButtonElement.<anonymous> (jquery.min.js?ver=3.7.1:2:70726)
    at Function.each (jquery.min.js?ver=3.7.1:2:3129)
    at e.<computed>.each (jquery.min.js?ver=3.7.1:2:1594)
    at e.<computed>.trigger (jquery.min.js?ver=3.7.1:2:70701)

    Failed to load resource: the server responded with a status of 503 (Service Unavailable) admin-ajax.php:1

    POST https://labhuset.no/wp-admin/admin-ajax.php 500 (Internal Server Error)
    send @ jquery.min.js?ver=3.7.1:2
    ajax @ jquery.min.js?ver=3.7.1:2
    (anonymous) @ jquery-migrate.min.js?ver=3.4.1:2
    e.<computed> @ jquery-migrate.min.js?ver=3.4.1:2
    l @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    setTimeout (async)
    m @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    c @ jquery.min.js?ver=3.7.1:2
    fireWith @ jquery.min.js?ver=3.7.1:2
    l @ jquery.min.js?ver=3.7.1:2
    (anonymous) @ jquery.min.js?ver=3.7.1:2
    load (async)
    send @ jquery.min.js?ver=3.7.1:2
    ajax @ jquery.min.js?ver=3.7.1:2
    (anonymous) @ jquery-migrate.min.js?ver=3.4.1:2
    e.<computed> @ jquery-migrate.min.js?ver=3.4.1:2
    l @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    setTimeout (async)
    m @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    c @ jquery.min.js?ver=3.7.1:2
    fireWith @ jquery.min.js?ver=3.7.1:2
    l @ jquery.min.js?ver=3.7.1:2
    (anonymous) @ jquery.min.js?ver=3.7.1:2
    load (async)
    send @ jquery.min.js?ver=3.7.1:2
    ajax @ jquery.min.js?ver=3.7.1:2
    (anonymous) @ jquery-migrate.min.js?ver=3.4.1:2
    e.<computed> @ jquery-migrate.min.js?ver=3.4.1:2
    l @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    setTimeout (async)
    m @ heartbeat.min.js?ver=6.4.1:2
    d @ heartbeat.min.js?ver=6.4.1:2
    p @ heartbeat.min.js?ver=6.4.1:2
    (anonymous) @ heartbeat.min.js?ver=6.4.1:2
    dispatch @ jquery.min.js?ver=3.7.1:2
    v.handle @ jquery.min.js?ver=3.7.1:2

    • This reply was modified 11 months ago by SHR Design. Reason: Updating reply to answer question
    in reply to: E_ERROR in Enfold functions file as well as in other files #1425829

    Hi Nikko
    What should I tell the web host?
    I have asked them for help earlier but they did not see any problems on their end, so I need to figure out how to formulate how I share information with them. Thank you!

    in reply to: E_ERROR in Enfold functions file as well as in other files #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 11 months ago by SHR Design. Reason: Adding more information
    in reply to: E_ERROR in Enfold functions file as well as in other files #1425784

    Hi Nikko
    I received this WordPress recovery email earlier today. I was still able to access the site without having to use the site recovery link.

    WordPress version 6.4.1
    Active theme: Enfold (version 5.6.8)
    Current plugin: (version )
    PHP version 8.1.13

    Error Details
    =============

    An error of type E_ERROR was caused in line 742 of the file /home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php. Error message: Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/hr/hr.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-admin/admin-ajax.php(22): require_once(‘/home/L/labhuse…’)
    #8 {main}
    thrown

    ———

    Enfold is showing up on occasion with errors. It would be helpful to get this fixed as well. I am working with other plugin developers to get other things fixed.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1425611

    I made a new video today. Link also shared in the wp org WooCommerce issue seen in the above link.
    It shows the impact of switching from PHP 8.1 to PHP 8.0. WooCommerce and Solid Security plugins are impacted.
    I have emailed Solid Security plugin support and I have added on to the above issue for WooCommerce.

    I do not know if Enfold has an impact on these things.

    • This reply was modified 11 months, 1 week ago by SHR Design. Reason: Adding info
    in reply to: E_ERROR in Enfold functions file as well as in other files #1425601

    A few days ago adjusted the allocated memory.
    I am still receiving fatal errors, but even though they are seen as fatal errors they since looks down for a moment and then I refresh and the site comes back.

    There is a wp org WooCommerce thread I made.
    https://wordpress.org/support/topic/recovery-mode-mentions-these-errors/#post-17201893

    • This reply was modified 11 months, 1 week ago by SHR Design. Reason: Adjusting text
    in reply to: Show a default search field instead of search icon #1425245

    Hey Mike

    I added a gear icon to show the user that something is going on. As it seems one needs to wait a little before results show up.
    I mentioned the slowness of the search area for FidoSearch support so I will see what they say. It might be something I can share here. So let’s wait a few days with closing the thread.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1425239

    Hi Nikko

    I have noticed there is a mix of errors with the labhuset.no web site. The site ran WP 6.3.2 at the time I took the below video. Right afterward I upgraded it to WP 6.4 but all the same errors remained.

    The video became much longer (24 minutes) than I hoped as multiple issues showed up along the way.

    1- I have contacted ManageWP about the errors related to the Worker plugin.
    There are various errors there, so it is hard to pinpoint what is really going on.
    This is a work in progress. I thought I would share the video just in case you have any thoughts regarding what is going on.

    Here is one Enfold error that came up.
    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home/L/Labhusetno//www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/base-classes/class-popup-templates-base.php on line 104

    • This reply was modified 11 months, 1 week ago by SHR Design. Reason: Added an error related to Enfold
    in reply to: Show a default search field instead of search icon #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.

    in reply to: E_ERROR in Enfold functions file as well as in other files #1424902

    Thank you for your help!

    I am including FTP access in the private area.

    Btw
    There is also a problem moving around and/or performing various actions in the Labhuset WordPress backend as often it jumps to an error screen (looks like fatal errors). Example a product or moving to all products and then a product. I have to refresh the browser window to return to the regular backend WordPress. It happens seemingly on random. There is a mix of WooCommerce errors happening. I made this issue at the WooCommerce Github repo: https://github.com/woocommerce/woocommerce/issues/41255
    I do not know how this is related to Enfold though.

    • This reply was modified 11 months, 2 weeks ago by SHR Design. Reason: Additional information
    in reply to: Show a default search field instead of search icon #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.

    in reply to: Best way to inject variable content into post body #1424439

    Hei
    I hope you can help me.
    We have a problem with Enfold and WooCommerce on the website labhsuet.no.

    1. The problem is WooCommerce’s problem using Enfold.
    The site works extremely slow when we work backend. It have been a problem in a few weeks now.
    We have switched plugins on and off and received feedback that there is something wrong with Enfold.
    This topic comes up and our webhotell tells us this problem:

    In this case, WordPress found an error with your theme, Enfold.
    WordPress has a built-in feature that detects when an extension or theme causes a fatal error with your site and notifies you with this email automatically.
    In this case, WordPress found an error in one of your extensions, WooCommerce.
    First visit your website https://labhuset.no/
    If you seek help with this problem, you may be asked for any of the following information:
    WordPress version 6.3.2
    Active theme: Enfold (version 5.6.6)
    Current Extension: WooCommerce (version 8.2.1)
    PHP version 8.1.13

    2. It´s also a problem that the media don´t images in the media do not appear when they are to be loaded on the pages.

    May I be allowed to send you the login codes so that you can look into the problem and find out whats wrong?

    Best regards Silje from SHR Design.

    in reply to: MaiChimp API problem #1346354

    Thanks!

    in reply to: MaiChimp API problem #1346319

    Thanks. I will try Ismael.

    Best regards,
    Silje

    in reply to: MaiChimp API problem #1346277

    Hi Rikard

    Can you please give me a link to the best tutorial for using another plugin for the contact form? Du you recommend the plugin Contactform7?
    Do I have to also use a safety plugin?

    Best regards from Silje

    in reply to: MaiChimp API problem #1345940

    Hello Rikard

    It does not seem to be good enough.
    Have you got any better plan.😊

    Best regards Silje

    in reply to: MaiChimp API problem #1345870

    Thanks. I will try.
    What would you recommend me to do to avoid spam from Enfold’s contact form?

    Best regards

    @Siljerang

    in reply to: WooCommerce and Enfold Layout editor #1239155

    Hei @rikard and @Victoria

    I just want to tell you that It was the host of my customers mail, that have not opened the e-mail to send from the Contact form, after the spam.
    I´m glad we found out what was wrong. And it´s nothing wrong with the Contact Form in Enfold. 😊

    I´m so glad.


    @siljerang

    in reply to: WooCommerce and Enfold Layout editor #1238812

    Hei @rikard

    In the file manger i found an error_log:

    [Tue Aug 18 15:11:01.203892 2020] [ssl:error] [pid 3496841] AH02032: Hostname http://www.bjornafjordenopplevelser.no:443 provided via SNI and hostname http://www.bjornafjordenopplevelser.no provided via HTTP are different
    [Tue Aug 18 15:11:02.642252 2020] [ssl:error] [pid 3497211] AH02032: Hostname bjornafjordenopplevelser.no:443 provided via SNI and hostname bjornafjordenopplevelser.no provided via HTTP are different

    Can you tell me what to do with this to get the contact form ok again?

    Hope to here from you soon. My customer can´t wait anymore?
    Thanks for helping me out of this problem.😊

    Best regards from @siljerang

    in reply to: WooCommerce and Enfold Layout editor #1238774

    Hei @rikard

    We have a problem to use the Contact Form on our website https://bjornafjordenopplevelser.no/contact-us/
    We use the contact form from Avia Layout Builder.
    When you click on “send”, the customer do not receives an e-mail, and it will not send the information to the e-mail I have written in the form that goes to the owner of the page, like it did before. I think it’s because of the spam their mail has been through, which came from the website.
    Now I have taken away the Contact Form from the site waiting for help from you to find out what`s wrong.
    Can you help me?


    @siljerang

    in reply to: WooCommerce and Enfold Layout editor #1238432

    Hei @Rikard

    Thanks. Yes, I did find a place where I had written Bold text closed properly. Tok it away, and than I could save the elements in content aganin. Thank you. I´m so glad.😊

    ___

    We have also a problem to use the Contact Form on our website https://bjornafjordenopplevelser.no/contact-us/
    We use the contact form from Avia Layout Builder.
    When you click on “send”, the customer do not receives an e-mail, and it will not send the information to the e-mail I have written in the form that goes to the owner of the page, like it did before. I think it’s because of the spam their mail has been through, which came from the website.
    Now I have taken away the Contact Form from the site waiting for help from you to find out what`s wrong.
    Can you help me?


    @Siljerang

    in reply to: Contactform Error – Not sending #1238316

    Hei @Victoria

    I´m so glad to here from you.😊
    No I´m sorry. It did not work. I think you have tasted the Contact Form on another site.
    Here´s the website I have problems with https://bjornafjordenopplevelser.no/contact-us/.
    I had to take away the Contact Form until my costumer had set in his SMTP Host kode in the plugin WP mail SMTP.
    I hope it will be better after he have done that. Or schoud I download a Contact Form plugin instead og use the Avia Layer builder elements that I usally do?

    ___

    I have also a problem with a new page I have made today. It will not accept me to update elements from Avia Layer builder like it normally do.
    Can you tell me how to find API in Envato Market, ( where I have bought the Enfold Theme) and how to update the Enfold Theme in Enfold?
    Or is it a bug in Enfold, that did come within the new version of WordPress. Is it some plugins I have to download? I have dowloaded Disable Gutenberg already.

    Thanks for helping me out of this. I hope you can solve this two problems I have.

    Best regards

    @Siljerang

    in reply to: WooCommerce and Enfold Layout editor #1238121

    Hello @Rikard

    When I use the Advanced Layout Editor on my costumers new website gallerinostegaten.no the content element just
    disappear after I have saved it, instead of being saved. Is it something I have installed to fix this? I have installed Disable Gutenberg at the site. Is this a bug within the new version of WordPress, or is it some more plugins I have to upload? I´m glad if you can help me.

    Best regards from @Siljerang

    in reply to: Contactform Error – Not sending #1238005

    Hi @Rikard

    Royaltask say It is a bug within Enfold occuring since the last update. Is that correct?
    Con you send me the answer where you can show me how to solve this problem?😊
    My customer can´t wait anymore. They need the Contact Form to get order.

    Best regards from @Siljerang

    in reply to: Contactform Error – Not sending #1237717

    Hi Victoria

    @royaltask
    say It is a bug within Enfold occuring since the last update. Is that correct?
    Con you send me the answer where you can show me (and others) how to solve this?

    Best regards from Silje.

Viewing 30 posts - 1 through 30 (of 60 total)