Forum Replies Created
-
AuthorPosts
-
November 15, 2024 at 2:49 am in reply to: Show a default search field instead of search icon #1471352
Hey Mike
I need to circle back to not using any code here. To figure out the bottom line issue happening. Fibo Search should be seen but it is not.
In a not logged in browser window. Upon loading the screen the Fibo Search box is seen for a moment before I noticed a kind of white area cover the everything to the left of the menu. (Seen in the Brave and Firefox browser not logged inn.)From this it looks like the Fibo Search is not a part of the menu. Even though it is added through the menu.
Why is Enfold covering up Fibo Search and how can we handle this in a simple way?
November 15, 2024 at 12:35 am in reply to: Built in privacy feature in theme options not working correctly. #1471347Hi
I had to login in Firefox to be able to Enable/Disable cookie consent messages. As this is not working in Brave on my own computer here. Which I find strange. I am not sure what else to do at this stage.November 12, 2024 at 1:46 am in reply to: Built in privacy feature in theme options not working correctly. #1471121Hi Ismael
Good to hear that it looks alright on your end in Brave.
How do I enable/disable the privacy feature in Enfold? I did not see anything that gave clarity in relation to this.Thank you.
November 10, 2024 at 10:35 pm in reply to: Built in privacy feature in theme options not working correctly. #1471033Interesting. I turned off some of the extensions thinking those might impact. I believe the ad blocker by default is on.
It seems a bit weird if that impacts these two fields though.I added a screenshot to my dropbox. Hopefully the link works fine.
https://www.dropbox.com/scl/fi/rg9yj4eneiwrb1jx9gql8/Enfold-Privacy-setting-seen-in-Brave-browser.jpg?rlkey=sw11lkf83a5giyputm3uafdca&st=mpg6clos&dl=0″ alt=”Privacy and Cookies settings in Enfold seen in Brave browser”Redoing the link:
https://icedrive.net/s/2kNfTC1vGyA7XajAD9FfAD2iYvP1Thanks for being there Mike.
- This reply was modified 6 days, 21 hours ago by SHR Design. Reason: Original image link does not work. I added another
- This reply was modified 6 days, 21 hours ago by SHR Design. Reason: Trying the image link again
- This reply was modified 6 days, 21 hours ago by SHR Design.
November 10, 2024 at 6:31 pm in reply to: Built in privacy feature in theme options not working correctly. #1471021Thanks Mike!
I noticed the plugin conflict between Autoptimize and WP Rocket and have left Autoptimize off. No need as you mentioned to have both.
I turned WP Rocket on again and then off but in the Brave (Chrome version) browser I am still seeing the same issue that the Enable cookie consent messages AND the Message fields contain errors. Both fields are hidden so that I can not modify these.Logging in with Firefox both these fields show up as they should,
So the issue here is that Brave is not showing the two fields correctly.
November 3, 2024 at 11:01 am in reply to: Show a default search field instead of search icon #1470491Hi
Thank you for leaving the thread open.
The whole process stopped up with FiboSearch. As I forgot to reply to their message when trying to figure out why the search was slow.
I have added FiboSearch to another site: https://industrihuset.no/
I transferred the same settings from the first site to the second site, but either I forgot something to transfer over or I have to add additional CSS to Enfold as the search bar is there for a second before it disappears perhaps behind the menu. I also will need to move the search bar down to align it with the rest of the menu.Do you have some advice on this? Thank you.
It would help to update the Enfold theme code so that contact form fields are not grey but white on default.
As I do not believe it was changed by myself or anyone else working on the site.Thanks for the help.
I think it is fine to close it.
Hi Ismael
That worked! Adding white to the background color of the fields made it clear where to click to enter information.
I reactivated Autoptimize again and it is working nicely.Hi
To figure out the correct CSS I did the following:
I made the desktop browser small so the Hamburger/mobile menu showed up. I right clicked the background color and selected Inspect (various browsers do something similar but might call it a little different from each other). In Inspect one can see the HTML and the CSS. I looked at the CSS and clicked into the code and added a color to see if that impacted the mobile menu. I end up using this code:@media only screen and (max-width: 989px) { #top #av-burger-menu-ul { vertical-align: top; background: orange !important; } }
I made this issue because it would be good to have an easy way when using Enfold to select not to show image title on hover.
It seems that Blocksy and Gutenberg will not display the image title. If I want to include the Image title in an Image block in Gutenberg I would need to open Advanced and add in the title as mentioned by Ismael.Now instead of a customer needing to include code to not show the image title on hover it would be helpful that Enfold itself found a way to handle it without needing the customer to tackle it.
Thank you for the discussion!
Hey
I am using the Brave browser which is a variation of Chrome.
Duckduckgo logo here.https://duckduckgo.com/
Using the Brave browser I do not see any image title on hover when hovering over the logo.I mentioned testing the default theme Twenty Twenty Four on another site here: https://bluewinddesign.com/
I was wrong I am testing the new upcoming theme Twenty Twenty Five and RC1 of WP 6.7
Using Gutenberg. A cover block with an image. It does not show image title on hover. I also added other kinds of blocks below it.
Do you see any image title on hover on any of these?Another site running the theme Blocksy.
Hover over the image used there: https://okosamfunn.no/
Do you see any image title show up?Now for Enfold I have to add JavaScript to remove the image title so it is not seen on hover. Adding JS is not a good approach. As you say the image title should not be removed.
Go to https://wordpress.org/ do any of the images show an image title when you hover the images?
From the exploration above Using the new Twenty Twenty Five upcoming default theme or a Blocksy theme I was not able to see any image title show up on hover. I do with the Enfold theme. Again I am testing using the Brave browser.
Suggestions?
August 13, 2024 at 11:01 pm in reply to: Missing Media Library images when inserting images #1464567I 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.
December 5, 2023 at 9:03 am in reply to: E_ERROR in Enfold functions file as well as in other files #1427203Hi 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.
December 5, 2023 at 8:30 am in reply to: Not able to see stock overlay badge in WooCommerce #1427199Thank you very much!
I did not even think about the z-index. That worked well!December 3, 2023 at 10:27 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1427079I 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 64MThe 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.
November 17, 2023 at 10:15 pm 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.November 17, 2023 at 5:02 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1425858Updating 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-editorError: 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:10Uncaught (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:1Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
editor.min.js?ver=6.4.1:2Uncaught 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:2Uncaught 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 1 year ago by SHR Design. Reason: Updating reply to answer question
November 17, 2023 at 12:40 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1425829Hi 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!November 17, 2023 at 12:05 am in reply to: E_ERROR in Enfold functions file as well as in other files #1425789The 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 7422023-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 7422023-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 7422023-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 1952023-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 7422023-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 7422023-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 7422023-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 1952023-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 7422023-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 1902023-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 7422023-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 6822023-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 6822023-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 7422023-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 7422023-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 6822023-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 7422023-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 2272023-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 8292023-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 1 year ago by SHR Design. Reason: Adding more information
November 16, 2023 at 10:27 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1425784Hi 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.13Error 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.
November 15, 2023 at 12:52 am in reply to: E_ERROR in Enfold functions file as well as in other files #1425611I 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 1 year ago by SHR Design. Reason: Adding info
November 14, 2023 at 9:40 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1425601A 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 1 year ago by SHR Design. Reason: Adjusting text
November 10, 2023 at 4:35 pm in reply to: Show a default search field instead of search icon #1425245Hey 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.November 10, 2023 at 2:59 pm in reply to: E_ERROR in Enfold functions file as well as in other files #1425239Hi 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 1 year ago by SHR Design. Reason: Added an error related to Enfold
November 10, 2023 at 12:41 am in reply to: Show a default search field instead of search icon #1425179Thank 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.
November 7, 2023 at 10:27 am in reply to: E_ERROR in Enfold functions file as well as in other files #1424902Thank 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 1 year ago by SHR Design. Reason: Additional information
November 6, 2023 at 1:01 pm in reply to: Show a default search field instead of search icon #1424780Hi 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.
November 2, 2023 at 8:40 pm in reply to: Best way to inject variable content into post body #1424439Hei
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.
Thanks!
Thanks. I will try Ismael.
Best regards,
Silje -
AuthorPosts