-
Search Results
-
Hi
We made a new website with Enfold and WPML and now we have some problems or things that we do not understand.The first thing is that sometimes we have “av_button: label” and av_button: link” and sometimes we have only “av_button: label” in the translation editor.
The second thing is that for example the job description of a team member can have new lines in the original language but not in the translation.
See screenshots in the private content section.
Thanks very much.
Best regards
MikeIn reply to: Updating theme
Hi,
From what I see the “button” that is added in your portfolio grid is a link that has been added in the footer with a custom class of “x”:
this is not typical, usually the footer is empty:
so this is probably some custom code to add this link and create the button, and since you are losing this customization when you update the site it would point to a possible core file that has been customized instead of this code in your child theme, or perhaps the code needs to be adjusted to work correctly.
Please post the custom function that creates this button so we can test it on our test sites. I looked in your child theme but couldn’t find anything that would do this.Best regards,
MikeIn reply to: Burger Menu JS click action is deferred by WP-Rocket
Yes, I do and thank you. Unfortunately the touch event seems to get caught behind delayed actions no matter what I exclude.
#top .dropdown_widget .buttons .button.checkout #top .dropdown_widget .buttons .button .woocommerce-mini-cart__buttons a.button.wc-forward a.button.wc-forward:hover .woocommerce-page .button #sv-rbadge-box #searchform #searchsubmit .avia-search-tooltip .inner-toolip .minus .plus .rating_container .woocommerce-product-gallery .header_color .avia-tt #top #searchform(.*) .avia-search-tooltip #searchform(.*) #top .avia-font-entypo-fontello .header_color .av_ajax_search_image .header_color .av_ajax_search_title .header_color .ajax_search_excerpt (.*).av_ajax_search_entry(.*) .ajax_search_response (.*) (.*).av_ajax_search_title (.*).ajax_search_excerpt (.*).av_ajax_search_image .header_color h4 (.*).av_ajax_search_content .main_menu .menu-item-avia-special .av-hamburger .av-hamburger-box .av-hamburger-inner .av-burger-overlay .av-burger-overlay-scroll .av-burger-overlay-inner .av-active-burger-items .av-burger-overlay-active .av-burger-overlay-active-delayed .av-hamburger--spin .av-js-hamburger .avia_hidden_link_text .av-burger-menu-main #av-burger-menu-ul #avia-menu .av-width-submenu .current_page_item .current-menu-item .avia-menu .av-main-nav-wrap .menu .av-main-nav .sub-menu .av-burger-overlay-bg .inner-container #header_main\/jquery(-migrate)?-?([0-9.]+)?(.min|.slim|.slim.min)?.js(\?(.*))?( |'|"|>) /dynamic_avia/avia-footer-scripts-(.*).js /enfold/js/avia-snippet-hamburger-menu.min.js /enfold/js/avia.js /enfold/js/shortcodes.js /enfold/js/avia-compat.js /enfold/js/(.*).js /enfold/js/aviapopup/(.*).js /enfold/config-templatebuilder/avia-shortcodes/ /wp-content/plugins/woocommerce-germanized/(.*) var avia_is_mobileIt is a very common problem and I don´t know what the issue is but it seems that the burger-menu calls to some other function that still does get delayed.
In reply to: CSS Colors
Hey Chrisxx1982,
Thank you for your patience and the screenshots.
1: please link to this page as I couldn’t find the purple color on my Android device, you are using Android correct?
2: Try this CSS in your Enfold Theme Options ▸ General Styling ▸ Quick CSS field:#top #menu-item-shop .av-cart-counter { background-color: red; color: #ffffff; }3: try this css:
#top #main div.woocommerce-error a.button, #top #main div.woocommerce-message a.button { background: red; }4: for the links on this one page only in the text element, try this css:
#top.home .avia_textblock strong a { color: red; }5: try this css:
#top ul.products li .price, #top p.price { color: #000 !important; }Please adjust the colors to suit, after applying the css, please clear your browser cache and check.
Best regards,
MikeIn reply to: Google search results show ‘Untitled’
Hi,
Sure if you wish, if it helps try these steps, if you see this Verify domain ownership via DNS record
and you added custom nameserver DNS URLs where you bought your domain from, like NameCheap.com
which points to your webhost with a cPanel, you can go to Zone Editor
then click “add record” ▸ “add TXT record”
then add the domain name like the other TXT records (without https) and paste the google code:
and wait a few minutes and the click “verify” on the google Verify domain ownership popup:
I had to wait about ten minutes and check three times on my test site, but this I got the success message:
then you can go to URL Inspection see the Request Indexing button which you can use to get Google to re-crawl and re-index your URL.
But you might have to wait a day before doing this, as I found that with a new account and domain google shows the message Processing data, please check again in a day or so
But at least you got the ball rolling, in the future you will find the Google Search Console to be very helpful.Best regards,
MikeIn reply to: Masonry no entries fallback
Hi,
When I test the filter that Ismael posted above on my test site child theme functions.php and test a masonry element for a specific category, and set all of the items to “draft” the masonry element is not included in the page source code and it shows no items until I publish one of the posts for the specific category.add_filter('avf_masonry_query_no_entries_fallback', function($fallback) { return false; }, 10, 1);So this filter seems to be working correctly, when I examine your site you seemed to also be tring to show posts in a masonry element, but you didn’t have a category selected:
thus on the frontend the masonry element showed some “pages” instead of “posts”
so I selected the category in the masonry element:
and now on the frontend the masonry doesn’t show any items:
the title and button show because they are separate elements:
Please check.Best regards,
MikeIn reply to: slider above the password entry?
Hey schweg33,
Thank you for the inquiry.
Are you trying to edit the password protected page? If so, try to add this filter in the functions.php file and add your own modifications.
function avf_custom_password_form() { global $post; $label = 'pwbox-' . ( empty( $post->ID ) ? rand() : $post->ID ); $output = ' <div class="boldgrid-section"> <div class="container"> <div class="av-more-info">More info here</div> <form action="' . esc_url( site_url( 'wp-login.php?action=postpass', 'login_post' ) ) . '" class="form-inline post-password-form" method="post"> <p>' . __( 'This content is password protected. This is a custom message. To view it please enter your password below:' ) . '</p> <label for="' . $label . '">' . __( 'Password:' ) . ' <input name="post_password" id="' . $label . '" type="password" size="20" class="form-control" /></label><button type="submit" name="Submit" class="button-primary">' . esc_attr_x( 'Enter', 'post password form' ) . '</button> </form> </div> </div>'; return $output; } add_filter('the_password_form', 'avf_custom_password_form', 99);If you want to add a slider, try setting the builder to debug mode so that you can extract the shortcode of a builder element from one of your pages.
// https://kriesi.at/documentation/enfold/intro-to-layout-builder/#debug-mode
Best regards,
IsmaelIn reply to: Customised Toggle element doesn’t show
Thanks for your quick answer Ismael,
I did add this part of code in the functions.php located i the Enfold-Child shortcodes folder.
I wanted to change the name of the toggle shortcode because I need to keep the toggle component for other uses.
This new my-toggle element, displayed in the avia-builder is very specific, hence the changes I made.This works fine with Testimonial.php or buttons_fullwidth.php, so I wonder why this doesn’t work as expected with toggle.php
best regards
XavierHello,
In Enfold-child, I copied-pasted toggles.php, then changed the class name as well as the shortcode:
avia_sc_toggle by my_toogle$this->config[‘shortcode’] = ‘av_toggle_container’;
av_toggle_container by my_toggle_container$this->config[‘shortcode_nested’] = array( ‘av_toggle’ );
av_toggle by my_toggleI did that by replacing the texts in all the file.
When I edit the page from the dashboard, update then click on view, all seems to work well, the component is correctly displayed.
BUT when I go directly to the url, the component is not showed.Is there something I missed ?
I did the same with testimonials.php and buttons_fullwidth.php, and for this two component all’s working fine.Thanks in advance for your help.
Best regardsIn reply to: Easy slider buttons show loading element on click
Hi marius146,
Thanks for giving us admin access.
I have added this CSS code in Enfold > General Styling > Quick CSS:#top .avia-slideshow-button .avia_loading_icon { display: none !important; }Please review your site.
Best regards,
NikkoIn reply to: submitting a support topic
Hey David Wiener,
Please see the big blue button at the top of the forum, when you are logged in:
or you can use this link to create a new thread and we will gladly try to help you. Thank you for using Enfold.Best regards,
MikeTopic: submitting a support topic
I just bought Enfold and I’m having a few problems but I can’t find where to submit a topic. I’ve been to the support page and seen the topics but I don’t see a button/link where I can submit a topic.
Dave.Hey whdsolutions,
Try this CSS in your Enfold Theme Options ▸ General Styling ▸ Quick CSS field:#top a { text-decoration: underline; } #top #header a, #top #footer a, #top #socket a, #top a.avia-button, #top a.more-link { text-decoration: none; }After applying the css, please clear your browser cache and check.
Best regards,
MikeHallo,
1) ich habe eine website (www.ebook-schreiben-und-verkaufen.de) gekauft, die derzeit mit dem Theme “Thrive” läuft. Ich würde gern Thrive durch Enfold ersetzen (weil es in meiner Gegend einige Webdesigner gibt, die Enfold bevorzugen)… Allerdings… Die website benutzt u.a. das Feature “Thrive Leads”, das, wenn ein bestimmter Button geclickt wird, den Bildschirm abdunkelt und eine Eingabemaske für Vorname und eMail-Adresse bringt… Diese Daten werden dann via API an Klick-Tipp weitergeleitet, um dort eine eMail-Serie zu starten. Das sollte doch auch mit Enfold möglich sein? Ich habe ein paar Informationen dazu gefunden, diese sind aber teilweise schon sehr alt.Das Ganze sollte möglichst ohe zusätzliche Produkte möglich sein, da das Projekt derzeit ohnehin wenig rentabel ist (ich weiß, dass man z.B. NUR die Thrive Leads als Plugin auch für andere Themes nutzen kann…). Aber: Was geht mit “Bordmitteln” von Enfold? Bzw., falls es weitere Produkte braucht, was würden Sie empfehlen?
2) Gibt es irgendwo (YouTube etc.) ein Tutorial zu Enfold? (Bei Udemy hab ich mal einen Kurs gesehen…) Habe noch sehr wenig Ahnung von WordPress und gar keine von Enfold…
Danke schon mal.
When activating Enfold v5.6.5 in a cPanel with PHP 8, the website crashes and “There has been a critical error on this website.” displays.
Error Log:
[20-Nov-2023 06:08:54 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 662
[20-Nov-2023 06:12:14 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 618
[20-Nov-2023 06:12:15 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 601
[20-Nov-2023 06:58:08 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 662
[20-Nov-2023 07:11:01 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 643
[20-Nov-2023 07:17:46 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 590
[20-Nov-2023 07:21:22 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 590
[20-Nov-2023 07:21:55 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 590
[20-Nov-2023 07:25:13 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 662
[20-Nov-2023 07:31:50 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 643
[20-Nov-2023 07:45:07 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 226
[20-Nov-2023 07:45:15 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 226
[20-Nov-2023 07:48:19 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 77
[20-Nov-2023 07:48:27 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 235
[20-Nov-2023 07:48:28 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 226
[20-Nov-2023 07:48:31 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 234
[20-Nov-2023 07:48:32 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 226
[20-Nov-2023 07:50:50 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 233
[20-Nov-2023 07:50:51 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 77
[20-Nov-2023 07:54:30 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 5242880 bytes) in /home/betagchtravis/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.php on line 64Suggestions?
In reply to: Button – Link on Pictures
Hey Chrisxx1982,
Thanks for the screenshots and the link to your site, but it looks like you have added a strong tag around your caption text and then used some custom css to create the button:.av-image-caption-overlay-center p strong { color: #FFF; padding: 10px; background-color: rgba(0,0,0,.5); font-weight: 400; border-radius: 5px }So if you want the button in the image to be green then please adjust the background color in the above css, the image element doesn’t have a “button” option.
If you did use a strong tag I hope you are using the Special Character Translation plugin so you will not have this error:
If I have misunderstood please include an admin login in the Private Content area so we can be of more assistance.Best regards,
MikeTopic: Colors
Hi,
unfortunately, I can’t set the appropriate colors in the general styling in the Enfold Theme settings.I have created a new color scheme for our shop, which I would now like to add.
For example, if I want to customize the buttons differently, I only find the global setting. For example, I want to change the color of the “Add to Cart” button, but then other areas with the button for offer prices also change…
I also looked at the theme options with “extended styling”, but unfortunately I can’t find exactly what I’m looking for there. I can adjust some things, but not everything.
How can I assign different colors to each area on my website?
I would like to take this opportunity to thank you again for your help. I booked support specifically and am very satisfied so far. I currently have more to renovate and so far I have been able to help with every request, thank you very much for that.
Best regards
ChristianIn reply to: Menu issue
Hi keifygeorge,
Please try to add this in Enfold > General Styling > Quick CSS:
#top #header_main .dropdown_widget_cart .woocommerce-mini-cart__buttons { background-color: black; border-top: 1px solid white; }Hope it helps.
Best regards,
NikkoUpdating 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[]=undefined&args[]= 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:2The 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 682I’m using the enfold construction demo on my website and i am unable to update the prtfolio button images on my home and projects pages. Also once i allocate my media with an image sectio in the portfolio dedicated page, i get it blury and low quality
Hi guys,
I now have the full superspeedy pack from WP Intense which includes a lot of database modifications.They also encourage you to set as many non-essential WP_Options with Autoload YES to Autoload NO to speed up all uncached actions on a site.
https://www.wpintense.com/knowledgebase/managing-your-wp_options-table/I have had to do an extensive review of transients generated by plugins and also items that auto load. The speed difference from optimising wp_options in the backend and front end on large sites is massive.
I want to apply this same method to Enfold theme itself.
If you run the following SQL command you can see Enfold typically has over 100 – 150 autoloaded functions.
select left(option_name,15) option_name, count( * ) total from wp_options where autoload = 'yes' group by left(option_name,15) order by total desc limit 100;(Note you need to change wp_ to your database prefix if it isnt wp_)
You can also then run:
SELECT * FROM wp_options where option_name like 'av_alb_usage_av%'; SELECT * FROM wp_options where option_name like 'av_alb_usage_av%' and autoload = 'yes';and
DELETE FROM
or
UPDATEav_alb_usage_av has over 100 options:
av_alb_usage_av_blog
av_alb_usage_av_button
av_alb_usage_av_button_big
av_alb_usage_av_buttonrow
av_alb_usage_av_buttonrow_item
av_alb_usage_av_catalogue
av_alb_usage_av_catalogue_item
av_alb_usage_av_cell
av_alb_usage_av_cell_four_fifth
av_alb_usage_av_cell_one_fifth
av_alb_usage_av_cell_one_fourth
av_alb_usage_av_cell_one_full
av_alb_usage_av_cell_one_half
av_alb_usage_av_cell_one_third
av_alb_usage_av_cell_three_fifth
av_alb_usage_av_cell_three_fourth
av_alb_usage_av_cell_two_fifth
av_alb_usage_av_cell_two_third
av_alb_usage_av_codeblock
av_alb_usage_av_comments_list
av_alb_usage_av_contact
av_alb_usage_av_contact_field
av_alb_usage_av_content_slide
av_alb_usage_av_content_slider
av_alb_usage_av_countdown
av_alb_usage_av_feature_image_slider
av_alb_usage_av_font_icon
av_alb_usage_av_four_fifth
av_alb_usage_av_fullscreen
av_alb_usage_av_fullscreen_slide
av_alb_usage_av_gallery
av_alb_usage_av_gmap_location
av_alb_usage_av_google_map
av_alb_usage_av_heading
av_alb_usage_av_headline_rotator
av_alb_usage_av_horizontal_gallery
av_alb_usage_av_hr
av_alb_usage_av_icon_box
av_alb_usage_av_icongrid
av_alb_usage_av_icongrid_item
av_alb_usage_av_iconlist
av_alb_usage_av_iconlist_item
av_alb_usage_av_image
av_alb_usage_av_image_hotspot
av_alb_usage_av_image_spot
av_alb_usage_av_layerslider
av_alb_usage_av_layout_row
av_alb_usage_av_magazine
av_alb_usage_av_mailchimp
av_alb_usage_av_mailchimp_field
av_alb_usage_av_masonry_entries
av_alb_usage_av_masonry_gallery
av_alb_usage_av_metadata_item
av_alb_usage_av_notification
av_alb_usage_av_one_fifth
av_alb_usage_av_one_fourth
av_alb_usage_av_one_full
av_alb_usage_av_one_half
av_alb_usage_av_one_third
av_alb_usage_av_partner
av_alb_usage_av_partner_logo
av_alb_usage_av_player
av_alb_usage_av_playlist_element
av_alb_usage_av_portfolio
av_alb_usage_av_post_metadata
av_alb_usage_av_postcontent
av_alb_usage_av_postslider
av_alb_usage_av_product_button
av_alb_usage_av_product_info
av_alb_usage_av_product_meta
av_alb_usage_av_product_price
av_alb_usage_av_progress
av_alb_usage_av_progress_bar
av_alb_usage_av_promobox
av_alb_usage_av_rotator_item
av_alb_usage_av_row
av_alb_usage_av_section
av_alb_usage_av_sidebar
av_alb_usage_av_slide
av_alb_usage_av_slide_accordion
av_alb_usage_av_slide_full
av_alb_usage_av_slideshow
av_alb_usage_av_slideshow_accordion
av_alb_usage_av_slideshow_full
av_alb_usage_av_social_share
av_alb_usage_av_submenu
av_alb_usage_av_submenu_item
av_alb_usage_av_tab
av_alb_usage_av_tab_container
av_alb_usage_av_tab_section
av_alb_usage_av_tab_sub_section
av_alb_usage_av_table
av_alb_usage_av_team_icon
av_alb_usage_av_team_member
av_alb_usage_av_testimonial_single
av_alb_usage_av_testimonials
av_alb_usage_av_textblock
av_alb_usage_av_three_fifth
av_alb_usage_av_three_fourth
av_alb_usage_av_timeline
av_alb_usage_av_timeline_item
av_alb_usage_av_toggle
av_alb_usage_av_toggle_container
av_alb_usage_av_two_fifth
av_alb_usage_av_two_third
av_alb_usage_av_video
av_alb_usage_avia_sc_searchand there are also other autoloaded options from the theme including:
avia_stylesheet
avia_gutenberg_
avia_options_th
widget_avia-ins
avia_woocommercPlus others possibly in your installation vs mine.
Would it be possible to review these options and make it so those that only run in the back end of wordpress are set to Autoload = NO
Would it also be possible to provide a list of those that can safely be set to NO? I can then run an SQL command to set them to NO:Like this:
update wp_options set autoload = 'no' where option_name like 'av_alb_usage_av_animated_numbers%' and autoload = 'yes';Transients Review
SELECT
option_nameASname,option_valueASvalue
FROM LkxroSS_options
WHEREoption_nameLIKE ‘%transient_%’
ORDER BYoption_nameAnything Enfold auto generates that shouldnt be autoloaded?
In reply to: Update 4.07 to latest version
Hi informatie1,
You cannot update the theme anymore using API key, you’ll need to use a personal token for that, in order to generate it, please follow the instructions in our documentation: https://kriesi.at/documentation/enfold/theme-registration/#how-to-generate-a-envato-personal-token
For updating the theme on your site, please do the following process:
First make a backup:
– Site Backup: https://kriesi.at/documentation/enfold/backup-wordpress-site/
– Theme Settings Backup: https://kriesi.at/documentation/enfold/backup-theme-settings/Option 1: Use Envato Market to update your site
– link: https://envato.com/market-plugin/Option 2: Update manually
1. Login to ThemeForest and download the Enfold theme, right-click over the downloaded zip file and extract/unzip it.
2. It should generate a new folder, open it and look for the enfold folder
3. Right-click the enfold folder then zip it, here’s a tutorial on how to create a zip file in windows: https://www.howtogeek.com/668409/how-to-zip-and-unzip-files-on-windows-10/ (this should create enfold.zip
4. Log in to WordPress as and Admin.
5. Install and activate a maintenance plugin and put your site in Maintenance mode.
6. Go to Appearance > Themes, switch to a default WordPress theme like TwentyTwenty then delete Enfold.
7. Click on the ADD NEW button.
8. Click on the UPLOAD THEME button.
9. Click BROWSE and choose enfold.zip file
10. Click the INSTALL NOW button and switch to Enfold or your child theme.
11. Remove the maintenance mode then deactivate and remove the maintenance plugin.Then register the theme by following the instructions in https://kriesi.at/documentation/enfold/theme-registration/
Once this is done, the next time you update, you’ll only need to go to Enfold > Theme Updates and click on the Update button.Hope it helps.
Best regards,
NikkoIn reply to: Prevent SPAM on Email Buttons
Hi Mike
Thanks for the update.
So, now i can use also subject and body in the button without using mailto?
I will wait for the official Enfold version with this change. Do you already know when this will be released?
What’s about the social links of a team member?There we have to use mailto: when we want to add an email address so the anti spam does not work.
Best regards
MikeIn reply to: Prevent SPAM on Email Buttons
Hi,
The Dev Team has updated the email spam function to include the subject and body in the email address in the button and in the shortcode in the shortcode wand, like this:(Email address hidden if logged out) ?subject=your_subject&body=your_body
I linked to the files below, you will need to replace:
/enfold/config-templatebuilder/avia-shortcodes/email_spam.php
/enfold/config-templatebuilder/avia-template-builder/php/class-generic-helper.php
In the button you will not manually add the “mailto:” and the shortcode would look like this:
[av_email_spam url=" (Email address hidden if logged out) ?subject=your_subject&body=your_body" hex_encoding="1"]readable info[/av_email_spam]Best regards,
MikeTopic: Buttons Shop Page
Hi, I have a problem with the layout of the shop page button as you can see from the image https://www.impsolari.com/wp-content/uploads/2023/11/shop-ko.png it can’t be read at all while it is in hover, just barely in hover but I would simply like it to work like the same green button on the product page https://www.impsolari.com/wp-content/uploads/2023/11/product-ok.png with the writing white but I can’t find the settings in the enfold settings can you help me please?
Thanks Gianluca from ItalyIn reply to: Show a default search field instead of search icon
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.
Does anyone know what the CSS is to style the woocommerce search bar (that searches for products only) to look the same as the default enfold search box which I have disabled as it is returning posts not products?
I would like the woocommerce search to look identical with a little magnifying glass search icon rather than a button below saying “search”
Thank you
In reply to: Social like news
Hey,
If you’d like to enable social share buttons on your bog posts, you can do so in the Enfold theme options > Blog Layout > Share Links At The Bottom Of Your Blog Pos ( https://i.imgur.com/gNMQqry.png ).
Best regards,
YigitHi,
Please click this button on the Enfold sub forum: https://imgur.com/a/AnoSPNb, or use this link to open a new thread.
Best regards,
Rikard
