Hi, Guenni007,
Thank you so much for your great help — the language switch now works exactly as I wanted. You’re my hero!
Questions:
1. I assume I have to reinsert the code line after every LayerSlider update.
2. Would it make sense to completely remove the LayerSlider included in Enfold?
3. If so, would I then have to remove the LayerSlider again after every Enfold update? It would be nice if there were an option, for example a toggle switch (LayerSlider on/off), to permanently deactivate and delete the included LayerSlider.

Hi, Ismael,
Thank you for your quick reply. I’m unsure whether I should completely remove the bundled LayerSlider plugin. That might only cause problems and unnecessary effort.
Best Regards
Herb

Clarification: last live-site fatal error occurred Dec. 23, 2025 — staging now reproduces the same Enfold issue

Hello Yigit,
I just wanted to clarify the timeline and current status of the Enfold fatal error that involves avia_font_manager. After reviewing all automated WordPress notifications more carefully, I confirmed that the last fatal error email from the live site (http://www.drisabelbalza.com) was sent on December 23, 2025. Since that date, I have deactivated and completely removed the “Child Theme Configurator plugin” and replaced the Enfold Child theme with the original Enfold Child folder provided by Kriesi (https://kriesi.at/documentation/enfold/install-enfold-theme/#why-child-theme)

Email received from WordPress:
Subject: [Dr. Isabel Balza] Your Site is Experiencing a Technical Issue

Howdy!

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with your theme, Enfold.

First, visit your website (https://www.drisabelbalza.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.drisabelbalza.com/wp-login.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

https://www.drisabelbalza.com/hootlogin/?action=enter_recovery_mode&rm_token=3iCP23yifQpCERmU07tedS&rm_key=AbfuyyFeY7jfVO9htoLbZm

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.8.3
Active theme: Enfold Child (version 1.0)
Current plugin: (version )
PHP version 7.4.33

Error Details
=============
An error of type E_ERROR was caused in line 223 of the file /home/drisabel/public_html/wp-content/themes/enfold/includes/classes/class-social-media-icons.php. Error message: Uncaught Error: Class ‘avia_font_manager’ not found in /home/drisabel/public_html/wp-content/themes/enfold/includes/classes/class-social-media-icons.php:223
Stack trace:
#0 /home/drisabel/public_html/wp-content/themes/enfold/includes/classes/class-social-media-icons.php(259): avia_social_media_icons->build_icon(Array)
#1 /home/drisabel/public_html/wp-content/themes/enfold/includes/classes/class-social-media-icons.php(288): avia_social_media_icons->html()
#2 /home/drisabel/public_html/wp-content/themes/enfold/includes/helper-main-menu.php(22): avia_social_media_icons(Array, false)
#3 /home/drisabel/public_html/wp-includes/template.php(812): require(‘/home/drisabel/…’)
#4 /home/drisabel/public_html/wp-includes/template.php(745): load_template(‘/home/drisabel/…’, false, Array)
#5 /home/drisabel/public_html/wp-includes/general-template.php(206): locate_template(Array, true, false, Array)
#6 /home/drisabel/public_html/wp-content/themes/enfold/header.php(275): get_template_part(‘includes/helper’, ‘main-menu’)

However, the situation has evolved as follows:
1) The same fatal error (Class ‘avia_font_manager’ not found)
2) The same file and line (class-social-media-icons.php, line 223)
3) The same stack trace path (social media icons → helper-main-menu → header.php)
is now being reproduced on the staging site: https://gg.drisabelbalza.com
This confirms the issue is not isolated to the live environment, and it persists even after removing the “Child Theme Configurator” plugin.

Current environment details:
– WordPress 6.8.3
– PHP 7.4.33
– Active theme: Enfold Child (version 1.0) → clean, original folder
– No custom code related to fonts or social icons

At this point, I would appreciate your guidance on:
1) Where exactly avia_font_manager is initialized in Enfold.
2) Under which conditions this class may fail to load before class-social-media-icons.php executes.
3) Whether this behavior is known or expected with WordPress 6.8.3 or PHP 7.4
4) Any recommended temporary workaround to prevent further fatal error emails while the root cause is addressed

Thank you for your continued assistance — my goal is to resolve this definitively before applying any further changes to the live site.

Best regards,
Claudia

• This reply was modified 1 month ago by carrclaudia.
• This reply was modified 1 month ago by carrclaudia.

Hi Rikard, when I extract the download (installation files only), I get an enfold folder. Inside, I find PHP files and several subfolders, but no ZIP file. I’m probably just being dense. Can you help me?

Subject: Clarification about WordPress error alerts and admin email

Hi Kriesi Support Team,

I’d like to clarify one important detail regarding the technical error alerts.

I personally do not receive any WordPress error notification emails. The WordPress administrator email address is configured to use the site owner’s GreenGeeks account, which was set up by the previous web developer before I became involved. My email was never added to receive system alerts.

Because of this, I can only know whether the error is still occurring when the site owner receives a WordPress alert email and forwards it to me. If no alert is forwarded, I have no direct confirmation from WordPress itself.

After my last changes yesterday (removing the previously generated Child Theme and uploading the original Enfold Child from Kriesi), both the staging site and the live site are still working correctly, and I have not been informed of any new alerts by the client so far. However, I cannot independently confirm whether WordPress has completely stopped sending them. I wanted to explain this limitation clearly so you have the full context.

Question about PHP version upgrade compatibility with Enfold:

Additionally, I’d like your advice regarding the PHP version. The site is currently running on PHP 7.4.33, and WordPress has been recommending an upgrade for several months now. I understand that PHP 7.4 is no longer receiving security updates, so I agree that an upgrade is necessary.

My concern is compatibility. Several active plugins list compatibility ranges such as “PHP 5.2.4 or higher” or “PHP 7.4 or higher,” but they do not clearly state support for PHP 8.1, 8.2, or 8.3. Because this site relies heavily on Enfold and its integrations, I want to avoid introducing new issues by upgrading PHP without proper validation.

Could you please advise:
1) – Which PHP versions are currently fully supported and tested with the latest Enfold version?
2) – Whether PHP 8.1 is the safest recommended upgrade path at this time, rather than 8.2 or 8.3?
3) – If there are any known Enfold-related issues or settings to be aware of before switching PHP versions.

Hosting limitation regarding PHP version on live and staging sites:

One additional clarification regarding the hosting environment:
1) Both the live site and the staging site are hosted under the same GreenGeeks account, and unfortunately, GreenGeeks does not allow PHP versions to be set independently per site in this setup. Any PHP version change applied at the hosting level affects both the live site and the staging site at the same time.

2) Because of this limitation, I cannot safely test different PHP versions on staging without impacting the live site as well. That’s why it’s especially important for me to confirm in advance which PHP version is recommended and fully compatible with the current Enfold version before making any change.

If you have a specific PHP version you consider the safest choice for Enfold in this situation, your guidance would be greatly appreciated.
Thank you for your understanding and support.

Best regards,
Claudia

Thanks

a/ If we reverts to the standard woo product page, are there ways of adding the extra enfold layout builder elements after eg. The table, the showrooms slider, the accordions. Or would all of these be lost?

b/ If we used the existing as you say and add javascript – could test this if I set you a test page and gave access? Id f the javascript worked, would it be added separately at page level, or could it be added once for all products pages?

Thanks

Subject: Issue resolved after replacing Child Theme – monitoring alerts

Hello Kriesi Support Team,

I wanted to update you on the latest status.

I completely deleted the Enfold Child theme that was previously created using the “Child Theme Configurator plugin” and deactivated the plugin as well. After that, I uploaded and activated the original Enfold Child theme folder provided by Kriesi.

Since making this change, everything is working correctly on both the staging site (https://gg.drisabelbalza.com) and the live website: https://www.drisbalebalza.com

There are no visible issues, and the site is behaving normally. At this point, I’m monitoring to confirm that the alert/error emails stop, which I expect now that the child theme structure is clean and original.

Thank you for your guidance. I hope this helped identify the real root cause.

Best regards,
Claudia

• This reply was modified 1 month, 1 week ago by carrclaudia.
• This reply was modified 1 month, 1 week ago by carrclaudia.