-
Search Results
-
In reply to: blank screen when editing buttons and other elements
Thanks again, Ismael! Interesting — the temp login isn’t expired, but here’s another one in the PC, also good for a week. I spoke with wp engine support and they troubleshot for about a half hour but couldn’t solve it. They showed me how to look in the inspector > Network > trigger the error > click on the first admin-ajax.php > Response and note how there’s just a “1” (https://snipboard.io/RJ7US6.jpg) as opposed to the html that should show there — they suggested I pass that info on to you in hopes it might provide a clue. I also added another environment in the same account, to test a clean install of Enfold there, and there doesn’t seem to be an issue with that install; no errors on buttons, etc. / functioning normally, if that offers any clue / potential solution. Lmk if you have any other questions.
In reply to: Enfold Version 3.8
Hey Angelika2017,
A few years ago Theme Forest stopped using the API Key for updating, and now uses the Token. So you will need to manually update with the steps below. Also Enfold v3.8 is not PHP v8+ ready, which is the most likely reason you can not make changes. Updating should solve.
We recommend creating a full site backup, including the database, please use your webhost tools for this and not a plugin, unless you are very conflict with the plugin. Another good approach would be to first create a staging site, most webhosts offer this as a single click option, if your webhost has the Softaculous script library that is available in cPanel & Plesk. If it lists your WordPress site you will see a button to create a staging site.
While we don’t expect any issues updating your site, this is a practical approach for such an old site.
If you don’t have a Theme Forest because a “developer” created this site for you using their own Theme Forest account, you may need to create your own account by purchasing your own license. Note that Theme Forest will not transfer licenses & we can not create licenses due to our contract with Theme Forest.To update your version of Enfold you will need to download the latest installable WP version from your Theme Forest account and upload it to your WordPress ▸ Appearance ▸ Themes ▸ Add Themes ▸ Add New
after you choose the zip file and click install, you will see a This theme is already installed message because you are updating, you can continue,
then you will see the Theme updated successfully message.
After which you can go to your Theme Forest account and create a new Token for future automatic updates.Best regards,
MikeHello,
There seems to be something wrong with my Enfold installation. When I try the following command,
$ wp plugin update --allI get the following errors:
PHP Warning: Undefined array key "HTTP_X_FORWARDED_PROTO" in phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1277) : eval()'d code on line 87 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 Warning: Attempt to read property "options" on null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66 PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 74 PHP Fatal error: Uncaught Error: Attempt to modify property "config" on null in /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.php:28 Stack trace: #0 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/shortcode-template.class.php(65): avia_sc_layerslider->shortcode_insert_button() #1 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php(1306): aviaShortcodeTemplate->__construct() #2 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php(428): AviaBuilder->createShortcode() #3 /var/www/html/wp-includes/class-wp-hook.php(341): AviaBuilder->init() #4 /var/www/html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #5 /var/www/html/wp-includes/plugin.php(522): WP_Hook->do_action() #6 /var/www/html/wp-settings.php(742): do_action() #7 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('...') #8 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress() #9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() #10 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process() #11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() #12 phar:///usr/local/bin/wp/php/boot-phar.php(11): include('...') #13 /usr/local/bin/wp(4): include('...') #14 {main} thrown in /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.php on line 28 Fatal error: Uncaught Error: Attempt to modify property "config" on null in /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.php:28 Stack trace: #0 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/shortcode-template.class.php(65): avia_sc_layerslider->shortcode_insert_button() #1 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php(1306): aviaShortcodeTemplate->__construct() #2 /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php(428): AviaBuilder->createShortcode() #3 /var/www/html/wp-includes/class-wp-hook.php(341): AviaBuilder->init() #4 /var/www/html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #5 /var/www/html/wp-includes/plugin.php(522): WP_Hook->do_action() #6 /var/www/html/wp-settings.php(742): do_action() #7 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('...') #8 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress() #9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() #10 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process() #11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() #12 phar:///usr/local/bin/wp/php/boot-phar.php(11): include('...') #13 /usr/local/bin/wp(4): include('...') #14 {main} thrown in /var/www/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.php on line 28 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.Any help is appreciated!
Thanks,
RichardTopic: Preview Changes, Edit Socket
Hi,
When I last used Enfold, there was a “Preview” button that would show you the page after you’d made changes in the editor. Now, I can only find an arrow at the top that will open the page, but unless I save the changes, they don’t appear there. I need a way to preview changes before making them permanent with a Save. Suggestions?
Also, next to the Copyright statement, I’d like to remove the text: powered by Enfold WordPress Theme. How can I do that?
Thanks.
Thanks for your input. And yes, I know the issue was caused by the Enfold theme, I had already tried debugging with fallback themes where the Hivepress listing search worked just fine. Unfortunately, we had to stick with the Enfold theme as the whole website was already fully built with it and its ALB visual editor, making it impossible to switch themes just for Hivepress compatibility.
However, yesterday I took a full day to investigate the Enfold theme files, and I am happy to report that I have found the cause, and thus could fix the problem. Enfold developers might want to read on to understand and fix this potentially problematic code, as it might cause incompatibility issues with not just Hivepress but also other WordPress extensions that use their own search logic.
The file causing the Hivepress search problem is found in the Enfold theme file structure, namely
/themes/enfold/includes/helper-template-logic.php
In this file exists a function called “avia_search_query_filter”, starting around line 37. Its purpose is to “make sure that empty searches are sent to the search page as well”. Empty searches would mean standard text searches without a keyword (search term).
Unfortunately, this function does not check for custom post_types, it just addresses all searches. The URL
https://wiras.dora.group/?post_type=hp_listing&s=should definitely display the search results for the custom “Listing” post type, which is Hivepresses’ own custom post_type (since the parameter is in the URL after clicking Search), and not be treated as a standard text search.The problem is that most Hivepress searches would be considered “empty” searches as they don’t have a keyword parameter, but are searches by checkbox, select menue or radio button values (these are generated by the listings “custom fields”). Thus, the above mentioned function of the Enfold theme hijacks those searches and instead of handing them over to Hivepress, redirects them to the themes’ own “Nothing found” search result page.
All I had to do now is to comment out the whole function in the file “helper-template-logic.php”, starting from line 41 until line 66:
41 if(!function_exists(‘avia_search_query_filter’))
42 {
43 function avia_search_query_filter($query)
[…]
64 add_filter(‘pre_get_posts’, ‘avia_search_query_filter’);
65 }For now this works for us, as we don’t use a standard text search on the site anyway. We just have to be careful when updating the theme.
You might consider finetuning your function to check for “custom post types” and exclude them from the search redirecting, as it seems your current approach is a bit too general and has the potential to hijack other plugins custom search patterns.
Best regards,
SebastianIn reply to: Extra blank space
Hi,
To open a new thread plase login and use this link. It is the large blue button.
To remove the copyright please go to Enfold Theme Options ▸ Footer ▸ Copyright ▸ and add [nolink] See this documentationBest regards,
MikeIn reply to: CSS files are always deleted
Hi again,
I managed to fix it. For those with the same problem, here’s a code snippet to add to the functions.php file that will flush both WP Rocket’s cache and object cache automatically, right after pressing Enfold’s “Save all changes” button.
// Clear WP Rocket cache and Object Cache when Enfold Theme Options are saved add_action( 'avia_ajax_after_save_options_page', function( $new_options ) { // Object Cache Pro: flush object cache if ( function_exists( 'wp_cache_flush' ) ) { wp_cache_flush(); } // WP Rocket: full cache purge if ( function_exists( 'rocket_clean_domain' ) ) { rocket_clean_domain(); } }, 20 );
@Ismael, I suggest you forward this to your team, as there is clearly something wrong here:
– The checkbox “Delete Old CSS And JS Files” is confusing. One expects to not have the CSS deleted if it’s unchecked.
– If there’s object cache in place, even when all caches are flushed after saving Enfold’s settings, the new CSS is not generated. Object cache needs to be cleared too.By the way, the ver=ver-1763353330 parameter is not something of our website. Even Enfold’s demo has it: https://kriesi.at/themes/enfold-2017/
Thank you.
In reply to: CSS files are always deleted
Hi Ismael,
The fact that files are physically deleted is a problem. Honestly, it’s a bit frustrating, because if you guys don’t see any problem, we are stuck with a theme that will cause display issues when you least expect it.
Since you’d like to see style issues, here’s the steps you need to follow. It can also be reproduce on the staging site:
1) Activate WP Rocket (the cache plugin we use)
2) Flush WP Rocket’s cache.
3) Visit the homepage from an Incognito window. Everything looks good. Notice the backgrounds and the file: https://i.imgur.com/Za2PKtu.png
4) Go to Theme Options > Performance and scroll down. You will see the option that says “Delete Old CSS And JS Files” is unchecked: https://i.imgur.com/saPibEH.png
5) Toggle the option on and then off again so the button to save the changes becomes available: https://i.imgur.com/UKA29Ny.png
6) Save the changes.
7) At this point, the physical CSS files are deleted.
8) Close the previous Incognito window and open a new one.
9) Visit the homepage again. Styles are missing: https://i.imgur.com/oqqtgWN.png
The reason is clear. Enfold is deleting the files the cached page still references to. I think you need to solve this in any way:
– Either flush the cache of the most popular cache plugins automatically,
– or make the checkbox “Delete Old CSS And JS Files” do what it’s supposed to do (if anyway they’re deleted, why does this checkbox exist?),
– or provide a solution (a filter or something) so that we can flush the cache programmatically when the “Save the changes” button is pressed.Thank you,
In reply to: CSS files are always deleted
Hi Ismael,
Again, it’s not about losing the styling or not. It’s about the theme’s functionality. Please follow these steps, and feel free to try them yourself. This time I am adding screenshots:
1) Go to the custom CSS folder. You can see that the CSS file exists: https://i.imgur.com/YLUSIKJ.png
2) Go to Theme Options > Performance and scroll down. You will see the option that says “Delete Old CSS And JS Files” is unchecked: https://i.imgur.com/saPibEH.png
3) Toggle the option on and then off again so the button to save the changes becomes available: https://i.imgur.com/UKA29Ny.png
4) Save the changes. The CSS files should not be deleted, correct? Now check the folder again: https://i.imgur.com/NTTBKLb.png
5) The link now redirects to a 404: https://app.site.com/wp-content/uploads/dynamic_avia/avia_posts_css/post-25947.css
6) On a live site, the CSS does not get regenerated because caching systems serve a cached page and prevent the request from reaching Enfold so it can regenerate the CSS. This is problematic because the CSS should not have been deleted in the first place.
@earthchilde: Am I missing something here?In reply to: CSS files are always deleted
Hi Ismael,
I think we are still not on the same page. Let me try to explain it again.
The problem is that Enfold deletes the old CSS files when saving the theme options. That always happens. It doesn’t matter whether you have made changes to pages or not. It doesn’t matter whether the “Delete Old CSS And JS Files” option is disabled. It’s simple: you press the “Save all changes” button and the CSS files are deleted. Here’s a step by step to reproduce the problem:
- Open the homepage from an Incognito.
- See the
/wp-content/uploads/dynamic_avia/avia_posts_css/post-1614.cssfile created. - Open the theme options.
- Go to the Performance section.
- See that “Delete Old CSS And JS Files” is disabled.
- Press the “Save all changes” button.
- The
/wp-content/uploads/dynamic_avia/avia_posts_css/post-1614.cssfile gets deleted. This should not happen. We explicitly chose these files not to be deleted.
This is not a problem if there is no cache in place. But almost everyone has a cache plugin, a CDN, or server cache. This means that when the files get deleted, the pages in question still serve the deleted files, and the only solution is to clear the cache manually so that Enfold can regenerate the CSS.
But the bottom line is that Enfold has a bug where it deletes the CSS files even when we choose not to.
I hope that clarifies it.
Thank you.
In reply to: CSS files are always deleted
Hi Ismael,
Sorry, what I meant is that all the files in the
avia_posts_cssfolder get deleted when pressing the “Save all changes” button on the Enfold settings page. This button: https://i.imgur.com/2frX3XH.pngAnd that happens even when the “Delete Old CSS And JS Files” is disabled and when there is no cache in place. You can see it by yourself in the staging site link I sent you before.
Thanks!
Hi,
We have a very old version (3.0.6) of the Enfold theme and we need to upgrade our PHP version from 5.6.40 to the neweset version PHP 8.4.
However when we tried we also needed to update the theme which we couldn’t find in our themeforest account so now we have bought the newest version.
I am trying to fix the issues with our IT partner and he tried updating it while running a localhost version on his laptop but he got a lot of errors.
Also as soon as we try to update through FTP we get a never ending stream of error messages for example:
Fatal error: Access level to av_email_spam::shortcode_insert_button() must be public (as in class aviaShortcodeTemplate) in ******\htdocs\*******\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\email_spam.php on line 16
To be smart i thought to just exclude it from the php file just to have it move on to the next 50 similar error messages.
Please let me know how to update the theme. As I found on your forums it was suggested you first needed to update to a version 4.5. or something and that would allow auto updates. However we now only have version 3.0.6. and the newest 7.1.3.
Kind regards
In reply to: Enfold Theme get compatibel with Heroic KB Plugin
Hey allespalettibystefan,
It’s unfortunately unlikely that we will find the time to make the Enfold layout builder compatible with the plugin you are using. If the plugin is compatible with the default WordPress editor, then I would suggest that you use those. Note that you can still add Enfold elements using Magic Wand button in the classic editor.
Best regards,
RikardIn reply to: HELP IN total Panic I broke my website
Perhaps the developers should set this setting to this value (“Block and Hide reset all options button”) by default after Enfold Activation. Too many people have accidentally pressed this button despite a warning pop-up.
Hi,
Hope you’re doing fine. I’ve recently bought Enfold and I’m using the Travel Demo. There is a blue bar above the main header/main menu that I can’t remove. I even found went to Enfold –> Advanced Styling and I deleted something called “small bar above the main menu”. Now the blue bar is kind of gone but that area is still there with the buttons (call, Registeration, Customer Login). So I thought it’s best to ask you before playing around with it anymore. I found a solution you have provided with adding a CSS code to Enfold but I was wondering if it’s possible to get rid of it without adding any CSS code.
Thanks
My website terrystavern.com is running Enfold 4.2.4. Can the old 4.2.4 version be updated to the latest version 7.1.3 using the theme update button on my cPanel, or will programming be required to preserve the design? I want to know before purchasing because a web designer used your theme to develop this site and I may choose to just replace the theme with all new if I can’t just by your $59 regular license and simply hit the update button in the Enfold Theme admin area. I don’t have the time to devote to programming and would opt to start with a fresh website if it’s not possible to just hit the update button after purchasing your license. Please let me know. Thanks.
Over the last few days when attempting to edit pages using Advanced Layout Builder page edit, it just throws up a blank page with a button for the Default Editor that just provides a small non-resizable box showing the HTML source.
After consulting the hosting provider DreamHost they revealed a console message:
“wp.editPost.PluginBlockSettingsMenuItem is deprecated since version 6.6.
Please use wp.editor.PluginBlockSettingsMenuItem instead.”The suggestion was that there is some incompatibility between our version of Enfold 7.1.3 and WordPress 6.8.3
It looks like this issue is recurring in Enfold 7.1.2 when ‘Use first slides caption as permanent caption’ is selected.
I have a custom shortcode:
<?php if ( ! defined( 'ABSPATH' ) ) { exit; } // Exit if accessed directly if ( ! class_exists( 'avia_sc_portfolio_kacheln' ) ) { class avia_sc_portfolio_kacheln extends aviaShortcodeTemplate { /** * Create the config array for the shortcode button */ function shortcode_insert_button() { $this->config['version'] = '1.0'; $this->config['self_closing'] = 'no'; $this->config['base_element'] = 'yes'; $this->config['name'] = 'Portfolio Kachel'; $this->config['tab'] = 'wuk Elements'; $this->config['icon'] = AviaBuilder::$path['imagesURL'] . 'sc-image.png'; $this->config['order'] = 1; $this->config['target'] = 'avia-target-insert'; $this->config['shortcode'] = 'av_portfoliokachel'; // $this->config['modal_data'] = array( 'modal_class' => 'mediumscreen' ); $this->config['tooltip'] = __( 'Inserts an image of your choice', 'avia_framework' ); $this->config['preview'] = 1; $this->config['disabling_allowed'] = true; $this->config['id_name'] = 'id'; $this->config['id_show'] = 'yes'; } function popup_elements() { $template_url = get_stylesheet_directory_uri(); $this->elements = array( array( 'type' => 'tab_container', 'nodescription' => true ), array( 'type' => 'tab', 'name' => __( 'Kachel', 'avia_framework' ), 'nodescription' => true ), array( 'type' => 'toggle_container', 'nodescription' => true ), array( "name" => __("Choose Image",'avia_framework' ), "desc" => __("Either upload a new, or choose an existing image from your media library",'avia_framework' ), "id" => "bild", "type" => "image", "title" => __("Insert Image",'avia_framework' ), "button" => __("Insert",'avia_framework' ), "std" => "", ), array( "name" => __("Title", 'avia_framework' ), "id" => "title", "std" => "", "type" => "input" ), array( "name" => __("Text", 'avia_framework' ), "id" => "text", "std" => "", "type" => "textarea" ), array( "name" => __("Button Text", 'avia_framework' ), "id" => "button_text", "std" => "", "type" => "input" ), array( 'name' => __( 'Image Link?', 'avia_framework' ), 'desc' => __( 'Where should your image link to?', 'avia_framework' ), 'id' => 'link', 'type' => 'linkpicker', 'fetchTMPL' => true, 'std' => '', 'lockable' => true, 'subtype' => array( __( 'No Link', 'avia_framework' ) => '', __( 'Lightbox', 'avia_framework' ) => 'lightbox', __( 'Set Manually', 'avia_framework' ) => 'manually', __( 'Single Entry', 'avia_framework' ) => 'single', __( 'Taxonomy Overview Page', 'avia_framework' ) => 'taxonomy', ) ), array( 'name' => __( 'Open new tab/window', 'avia_framework' ), 'desc' => __( 'Do you want to open the link url in a new tab/window?', 'avia_framework' ), 'id' => 'target', 'type' => 'select', 'std' => '', 'lockable' => true, 'required' => array( 'link', 'not_empty_and', 'lightbox' ), 'subtype' => AviaHtmlHelper::linking_options() ), array( 'type' => 'toggle_container_close', 'nodescription' => true ), array( 'type' => 'tab_close', 'nodescription' => true ), array( 'type' => 'tab', 'name' => __( 'Advanced', 'avia_framework' ), 'nodescription' => true ), array( 'type' => 'toggle_container', 'nodescription' => true ), array( 'type' => 'template', 'template_id' => 'screen_options_toggle', 'lockable' => true ), array( 'type' => 'template', 'template_id' => 'developer_options_toggle', 'args' => array( 'sc' => $this ) ), array( 'type' => 'toggle_container_close', 'nodescription' => true ), array( 'type' => 'tab_close', 'nodescription' => true ), array( 'type' => 'template', 'template_id' => 'element_template_selection_tab', 'args' => array( 'sc' => $this ) ), array( 'type' => 'tab_container_close', 'nodescription' => true ), array( 'id' => 'av_element_hidden_in_editor', 'type' => 'hidden', 'std' => '0' ) ); } /** * Editor Element - this function defines the visual appearance of an element on the AviaBuilder Canvas * Most common usage is to define some markup in the $params['innerHtml'] which is then inserted into the drag and drop container * Less often used: $params['data'] to add data attributes, $params['class'] to modify the className * * * @param array $params this array holds the default values for $content and $args. * @return $params the return array usually holds an innerHtml key that holds item specific markup. */ function editor_element( $params ) { extract( $params['args'] ); global $KACHELINDEX; $KACHELINDEX++; if (strstr($link,"manually,")) { $url = str_replace("manually,","",$link); } elseif (strstr($link,",")) { $tmp = explode(",",$link); $url = get_the_permalink($tmp[1]); } $out = '<div class="portfolio_kacheln sameheight"'.((empty($button_text) && !empty($link)) ? ' onclick="location.href='.$url.'"' : '').'> <div class="bg2">'.str_pad($KACHELINDEX, 2, "0", STR_PAD_LEFT).'</div> <div class="pic" style="">'. '<img src="'.$bild.'" />'. '<h3>'.$title.'</h3>'. '</div>'. (!empty($text) ? '<p>'.$text.'</p>' : ''). ((!empty($link) && !empty($button_text)) ? '<p class="action"><a href="'.$url.'" class="button">'.$button_text.'</a></p>' : ''). '</div>'; $params['innerHtml'] = $out; return $params; } /** * Frontend Shortcode Handler * * @param array $atts array of attributes * @param string $content text within enclosing form of shortcode element * @param string $shortcodename the shortcode found, when == callback name * @return string $output returns the modified html string */ function shortcode_handler( $atts, $content = '', $shortcodename = '', $meta = '' ) { extract( $atts ); global $KACHELINDEX; $KACHELINDEX++; if (strstr($link,"manually,")) { $url = str_replace("manually,","",$link); } elseif (strstr($link,",")) { $tmp = explode(",",$link); $url = get_the_permalink($tmp[1]); } $out = '<div class="portfolio_kacheln sameheight"'.((empty($button_text) && !empty($link)) ? ' onclick="'.($target == '' ? 'location.href='.$url.'"' : 'window.open(\''.$url.'\', \'_blank\');') : '').'> <div class="bg2">'.str_pad($KACHELINDEX, 2, "0", STR_PAD_LEFT).'</div> <div class="pic" style="">'. '<img src="'.$bild.'" />'. '<h3>'.$title.'</h3>'. '</div>'. (!empty($text) ? '<p>'.$text.'</p>' : ''). ((!empty($link) && !empty($button_text)) ? '<p class="action"><a'.($target != '' ? ' target="'.$target.'"' : '').' href="'.$url.'" class="button">'.$button_text.'</a></p>' : ''). '</div>'; return $out; } } }taht generates a shortcode like:
[av_portfoliokachel bild='https://xexadeti.cyon.site/wp-content/uploads/2025/08/sta-schweisstechnische-ausbildung-mag-schweissen.jpg' attachment='277' attachment_size='full' title='MAG' text='(135 - Metall-Aktivgas-Schweissen) Unverändert: [av_portfoliokachel bild='https://xexadeti.cyon.site/wp-content/uploads/2025/08/sta-schweisstechnische-ausbildung-mag-schweissen.jpg' attachment='277' attachment_size='full' title='MAG' text='(135 - Metall-Aktivgas-Schweissen) Gelöscht: MAG – das Arbeitstier unter den Schweissverfahren! Wir zeigen dir, wie’s richtig geht!' button_text='Infos zu MAG' link='portfolio_entries,5' target='' id='' custom_class='' template_class='' av_element_hidden_in_editor='0' av_uid='av-mebf8h83' sc_version='1.0' admin_preview_bg=''][/av_portfoliokachel]everything working fine, except oine thing, the ‘ Character.
array( "name" => __("Text", 'avia_framework' ), "id" => "text", "std" => "", "type" => "textarea" ),If I enter a ‘ char in this “Text” field, it doesnt get escaped as it should
as example: text=’test’s’ will be the endresult and not text=’test\’s’. Is there a hook or filter where I can “correctly apply escaping to a field?Strangly, I did setup the page and that did work. I did update to latest enfold version and now, that is not working anymore. Is that a new bug that the encoding is not correctly working?
It dows work, when changing the field name from “text” to “content”. But what, if I want more than 1 “content” field?
Normal textarea should equallless its name escaped correctly in enfold…Thanks for aour advice or fix.
My website design is missing the add new plugins
In reply to: License Key
Hi,
Please note that your page is in maintenance mode so we can not see it without logging in, but based on the photography demo, the two buttons “view portfolio and get in touch” are in the slider:
To edit the button text, first click the slider in the backend to edit, and then click the slide to edit:
then go to the Advanced tab Link Settings and edit the Button Label:
Please note that while you have a valid license for the theme, which is for life, support on the forum is different, when you purchase the theme, you also get six months of support with your purchase code, but your support expired 2016-03-02 so for further support please try going to your Theme Forest account and renew your support and then register your new support purchase code and log in to the support forum and open a new thread. Please note that using the contact form is not appropriate for support questions.Best regards,
MikeI just received this and the only API I use is for my Enfold sites. I assume you guys are on top of this:
Hello Google Maps Customer,
We are changing the Google Maps JavaScript API controls to reduce the space they occupy by default and to improve the accessibility of panning the map.
We’re reaching out to you because we have observed one or more of the following criteria:
Your end-users use the Zoom buttons significantly more than the average.
One or more of your maps explicitly disables the Zoom control.
One or more of your maps have customized controls.
We have provided additional information below to guide you through this change.What you need to know
Map controls are visual elements that allow user interaction with the map, including zooming the map, enabling Street View, and changing the Map Type.Version 3.58 of the Google Maps JavaScript API added a new Camera control to make panning the map accessible with a single gesture. This new Camera control features buttons for panning the map and for zooming the map in and out, effectively being a single control to guide the map’s viewport.
The changes are listed in the table below:
Date Available in Channel Changes Implemented
In September 2024 In the weekly channel Version 3.58 and version 3.59 offer the Camera control, without changing the default map controls.
In November 2024 In the quarterly channel
In February 2025 In the weekly channel Version 3.60 and newer contain the updated changes to the default map controls.
In May 2025 In the quarterly channel
November 2025 Version 3.58 is no longer available.
February 2026 Version 3.59 is no longer available.
What you need to do
Before the default controls are updatedTest the new Camera control on your maps in version 3.60 or newer.
If you use default controls in your map options, specify version 3.60 or newer to see how the default controls change.
If you do not use the default controls, or prefer not to test a newer version for now, enable the Camera control, and optionally disable the Zoom control, in google.maps.MapOptions.
After the default controls are updated
Consider taking one of the following actions when using version 3.60 or newer:If your code explicitly enables the Zoom control (zoomControl: true), both the Zoom control and the Camera control will be displayed. Consider choosing one to save on map space.
If your code explicitly disables the Zoom control (zoomControl: false), you may also want to disable the Camera control.
If your code explicitly enables the Zoom control (zoomControl: true) while keeping the default controls disabled (disableDefaultUI: true), only the Zoom control will be displayed. For better accessibility, consider enabling the Camera control instead.
You can specify version 3.59 which will be available until February 2026.Impacted customers/accounts:
Your affected projects, client ids and most affected websites are listed below:
400662023768
http://www.thomashenthorne.com
We’re here to help
Refer to our Maps Javascript API documentation for information about how to edit google.maps.MapOptions to enable cameraControl.If you have any other questions or need additional support, please contact us at Google Maps Platform Support.
Thanks for choosing Google Maps Platform.
—The Google Maps Platform Team
We are displaying weekly Youtube sermons in our website as videos.
We would like to also insert “cleaned up” transcripts, using the magic of ChatGPT.
We get a lovely html with print buttons, pdf buttons, style sheet — but cannot figure out how to insert this html document on our Enfold page.I have tried to use content in Accordion. Have learned that won’t work.
(Obviously, each week transcript will be different, so hoped I could use Advanced Custom Fields to store document info and then display via my custom post template.)
Right now, I am trying Textblock — in Code, not Visual.
I see the document nicely displayed on BACKEND, but on FRONTEND, I do NOT see the document displayed.
Since STYLE was included in the HTML — I moved style out to a Codeblock.
SCRIPT is also in there and I can move it out to another Codeblock.
What is your suggestion to “see” the document on the FRONTEND?
Thanks in Advance…
Below is the attempted code…
`[av_codeblock wrapper_element='' wrapper_element_attributes='' codeblock_type='' alb_description='' id='' custom_class='' template_class='' av_uid='av-mfpdws8b' sc_version='1.0']
<style>
/* ——– Base Styles ——– */<br />
:root {<br />
–bg: #0b0c0f;<br />
–card: #11131a;<br />
–ink: #e8ecf1;<br />
–muted: #aeb7c2;<br />
–accent: #6aa2ff;<br />
–accent-ink: #0b1b3a;<br />
–rule: #1e2330;<br />
}<br />
html, body { height: 100%; }<br />
body {<br />
margin: 0;<br />
background: radial-gradient(1200px 1200px at 10% -10%, #1b2030 0%, var(–bg) 60%);<br />
color: var(–ink);<br />
font: 16px/1.7 system-ui, -apple-system, Segoe UI, Roboto, Helvetica, Arial, “Apple Color Emoji”, “Segoe UI Emoji”;<br />
-webkit-font-smoothing: antialiased;<br />
-moz-osx-font-smoothing: grayscale;<br />
}</p>
<p> .wrapper {<br />
max-width: 860px;<br />
margin: 48px auto 96px;<br />
padding: 0 20px;<br />
}</p>
<p> .toolbar {<br />
position: sticky;<br />
top: 0;<br />
z-index: 10;<br />
backdrop-filter: blur(10px);<br />
-webkit-backdrop-filter: blur(10px);<br />
background: color-mix(in srgb, var(–bg) 80%, transparent);<br />
border-bottom: 1px solid var(–rule);<br />
}<br />
.toolbar-inner {<br />
max-width: 860px;<br />
margin: 0 auto;<br />
padding: 10px 20px;<br />
display: flex;<br />
gap: 10px;<br />
align-items: center;<br />
justify-content: flex-end;<br />
}<br />
.btn {<br />
appearance: none;<br />
border: 1px solid var(–rule);<br />
background: linear-gradient(180deg, #1a2233, var(–card));<br />
color: var(–ink);<br />
padding: 10px 14px;<br />
border-radius: 14px;<br />
cursor: pointer;<br />
font-weight: 600;<br />
transition: transform 0.05s ease, box-shadow 0.2s ease, background 0.2s ease;<br />
box-shadow: 0 6px 14px rgba(0,0,0,0.25);<br />
}<br />
.btn:hover { transform: translateY(-1px); }<br />
.btn:active { transform: translateY(0); }<br />
.btn.accent {<br />
border-color: color-mix(in srgb, var(–accent), #000 50%);<br />
background: linear-gradient(180deg, color-mix(in srgb, var(–accent) 50%, #fff 0%), var(–accent-ink));<br />
color: white;<br />
text-shadow: 0 1px 0 rgba(0,0,0,0.35);<br />
}</p>
<p> .card {<br />
background: linear-gradient(180deg, #131827, var(–card));<br />
border: 1px solid var(–rule);<br />
border-radius: 22px;<br />
padding: 28px 28px 36px;<br />
box-shadow: 0 20px 60px rgba(0,0,0,0.35);<br />
}</p>
<p> h1, h2, h3 { line-height: 1.2; margin: 0 0 8px; }<br />
h1 {<br />
font-size: clamp(28px, 4.2vw, 44px);<br />
letter-spacing: -0.02em;<br />
margin-bottom: 12px;<br />
}<br />
.meta { color: var(–muted); margin-bottom: 28px; }</p>
<p> h2 {<br />
font-size: clamp(20px, 2.5vw, 26px);<br />
margin-top: 34px;<br />
}</p>
<p> p { margin: 12px 0; }<br />
ul { margin: 8px 0 16px 24px; }<br />
li { margin: 6px 0; }</p>
<p> blockquote {<br />
margin: 18px 0;<br />
padding: 16px 18px;<br />
border-left: 4px solid var(–accent);<br />
background: color-mix(in srgb, var(–card), #000 8%);<br />
border-radius: 10px;<br />
}<br />
blockquote p { margin: 0; }</p>
<p> hr { border: none; border-top: 1px solid var(–rule); margin: 28px 0; }</p>
<p> .note { color: var(–muted); font-size: 14px; }</p>
<p> /* Drop cap for the opening paragraph */<br />
.lead:first-letter {<br />
float: left;<br />
font-size: 3.2em;<br />
line-height: 0.9;<br />
padding-right: 10px;<br />
margin-top: 6px;<br />
font-weight: 800;<br />
color: var(–accent);<br />
text-shadow: 0 6px 16px rgba(106,162,255,0.35);<br />
}</p>
<p> /* Print styles */<br />
@media print {<br />
body { background: white; color: #111; }<br />
.toolbar { display: none !important; }<br />
.wrapper { margin: 0; max-width: 100%; }<br />
.card { box-shadow: none; border: none; border-radius: 0; padding: 0; }<br />
a { color: black; text-decoration: none; }<br />
.note { color: #444; }<br />
@page { size: A4; margin: 20mm; }<br />
h1 { font-size: 28pt; }<br />
h2 { font-size: 16pt; margin-top: 18pt; }<br />
p, li, blockquote { font-size: 11.5pt; }<br />
blockquote { background: #f6f6f6; border-left-color: #888; }<br />
}<br />
</style>
[/av_codeblock][av_textblock fold_type='' fold_height='' fold_more='Read more' fold_less='Read less' fold_text_style='' fold_btn_align='' textblock_styling_align='' textblock_styling='' textblock_styling_gap='' textblock_styling_mobile='' size='' av-desktop-font-size='' av-medium-font-size='' av-small-font-size='' av-mini-font-size='' font_color='' color='' background='bg_color' background_color='' background_gradient_direction='vertical' background_gradient_color1='#000000' background_gradient_color2='#ffffff' background_gradient_color3='' padding='' padding_sync='true' av-desktop-padding='' av-desktop-padding_sync='true' av-medium-padding='' av-medium-padding_sync='true' av-small-padding='' av-small-padding_sync='true' av-mini-padding='' av-mini-padding_sync='true' fold_overlay_color='' fold_text_color='' fold_btn_color='theme-color' fold_btn_bg_color='' fold_btn_font_color='' size-btn-text='' av-desktop-font-size-btn-text='' av-medium-font-size-btn-text='' av-small-font-size-btn-text='' av-mini-font-size-btn-text='' fold_timer='' z_index_fold='' id='' custom_class='' template_class='' av_uid='av-mfpdtbrg' sc_version='1.0' admin_preview_bg='']
<div class=”toolbar” aria-label=”Document tools”>
<div class=”toolbar-inner”><button class=”btn” title=”Send to a printer”>
️ Print
</button>
<button class=”btn accent” title=”Use your browser’s Save as PDF option in the dialog”>
Download PDF
</button></div>
</div>
<div class=”wrapper”><article id=”content” class=”card”><header>
<h1>Sermon: “You Are the Light of the World”</h1>
<div class=”meta”>Text: Matthew 5:14–16</div>
</header>
<p class=”lead”>So, you might have noticed the theme. Send the Light. Thy Word is a lamp. There’s definitely a theme going here.</p>
We are continuing through the best sermon ever preached by the greatest preacher ever. We have seen Jesus giving assurances to His followers in the Beatitudes—letting them know that His followers are blessed.Last week, we began looking at the section where Jesus tells His followers that they are salt and light.
<h2>Salt</h2>
We learned a few things about salt in Jesus’ day. Salt was precious. When Jesus said, “Ye are the salt of the earth,” His disciples understood the value. Salt was so valuable it was sometimes used as payment for soldiers.Its value came from its purpose:
- Preservative – As salt, we preserve the holiness of God and His Word in the world.
- Purifier – Salt was used as a cleansing agent; so are we in the world.
- Penetrating – Salt works its way in. We are called to go into all the world with the gospel.
- Creates thirst – Salt makes people thirsty. Do we, by our lives, make people thirst for the living water that is Christ?
Jesus also warned of useless salt: “If the salt has lost its savour… it is good for nothing, but to be cast out and trodden under foot of men.” Notice, Jesus never challenged us to be salt or light. He simply said, you are.
<hr />
<h2>Light</h2>
Matthew 5:14–16 — “Ye are the light of the world. A city that is set on a hill cannot be hid. Neither do men light a candle and put it under a bushel, but on a candlestick, and it giveth light unto all that are in the house. Let your light so shine before men that they may see your good works and glorify your Father which is in heaven.”
What a title. What a privilege—that Jesus would say we are the light of the world. But what does He mean?
<h3>Jesus, the True Light</h3>
John wrote of the Light in John 1:4–9: “In Him was life, and the life was the light of men. And the light shineth in darkness, and the darkness comprehended it not… That was the true Light, which lighteth every man that cometh into the world.” Of course, John was speaking of Jesus.Jesus confirmed it Himself in John 8:12—“I am the light of the world.” Again, in John 9:5—“As long as I am in the world, I am the light of the world.” But then Jesus turned to His disciples and said, “Ye are the light of the world.”
<h3>The Nature of Our Light</h3>- It is personal – Jesus has given every believer this light. He didn’t say we might be light someday; He said we are light.
- It is His light in us – We are not the source. Jesus is. We are the lamp, the candle, the bulb through which His light shines.
- It is powerful – Even the smallest light conquers darkness. A single match in a dark cave changes everything.
Paul reminds us in 2 Corinthians 4:6 that God “commanded the light to shine out of darkness” into our hearts. Philippians 2:15 calls us to shine as lights “in the midst of a crooked and perverse nation.”
The tragedy is that much of the darkness in our world exists because Christians have hidden their light.
<h3>The Purpose of Our Light</h3>- To shine – Light is not made to be hidden under a bushel but set on a candlestick.
- To expose – Light reveals what is hidden in darkness, including sin.
- To reflect – Like the moon reflects the sun, we reflect the Son.
- To guide – Like runway lights, a lighthouse, or a warning sign, our light points others to safety and to the Father through Christ.
<h3>The Result of Our Light</h3>
Jesus says, “Let your light so shine before men that they may see your good works and glorify your Father which is in heaven.” Our light draws others to God. Our good works should point people to Him, not to ourselves. Salvation is mankind’s greatest need—and our shining light directs people to Christ.
<h2>Closing Challenge</h2>
Light always overcomes darkness, but it must shine to make a difference. Is your light shining for Jesus? Can you truly sing, “This little light of mine, I’m going to let it shine”? Or are you hiding your light under a bushel?If you are trusting in Christ, you have His light. Let it shine.
Prayer — “Lord, we thank You for Your Word this morning and the encouragement that we are the light of the world. Help us not to cover or hide the light, but to let it shine, that others may see our good works and glorify our Father in heaven. Amen.”
<p class=”note”>Tip: Use Print to send directly to a printer, or choose Save as PDF in the print dialog to download a PDF copy.</p>
</article></div>
<script>
// Optionally hide buttons when printing (extra safety for non-supporting browsers)
window.addEventListener(‘beforeprint’, () => {
document.querySelector(‘.toolbar’)?.setAttribute(‘data-hidden’, ‘true’);
});
window.addEventListener(‘afterprint’, () => {
document.querySelector(‘.toolbar’)?.removeAttribute(‘data-hidden’);
});
</script>
[/av_textblock]In reply to: javascript error – Syntax Error, unexpected $eof
In reply to: javascript error – Syntax Error, unexpected $eof
`<a href=”http://[18-Sep-2025 01:04:06 UTC] EXCEPTION: Unclosed ‘{‘ on line 1367 in /home/calvarybaptistdu/public_html/wp-content/themes/enfold-child/functions.php on line 1393″>Toggle a section when a button is clicked</a>
I am very evidently not good with javascript, but was hoping to follow “recipe” on
to Show/Hide a section.
I was trying to create what’s entitled
- Toggle a Section when a button is clicked.
At end of functioning functions.php, I inserted the following code and got the error indicated in the subject line above.
The debug indicates an [18-Sep-2025 01:04:06 UTC] EXCEPTION: Unclosed ‘{‘ on line 1367 in functions.php on line 1393 — that appears to be right on the line prior to the add_action. If I put in } (to close it?), I still get the error.
Please, could somebody steer me right on this thing? I’m befuddled!
Thanks for any help from an expert!
======================================================================================//——————————-
// Toggle section
//——————————-function toggle_on_click(){
?>
<script>
jQuery(window).on(‘load’, function(){// Button onClick event
jQuery(“.toggle-button a”).on(“click”, function(e) {
// Add your button events here
console.log(” toggle section”);
jQuery(“#toggle-section”).toggleClass(“hide-me”);
console.log(” Prevent default “);
e.preventDefault();
});
});
</script>
<!–?php<br /–> }add_action(‘wp_footer’, ‘toggle_on_click’);
Topic: Widget page inactive
Hello,
The widget page is completely inactive; none of the buttons are working. In debug mode, I get the following error message:
Une erreur de type E_ERROR a été causée dans la ligne 153 du fichier /homepages/21/d858425693/htdocs/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-mailchimp.php. Message d’erreur : Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in /homepages/21/d858425693/htdocs/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-mailchimp.php:153
Stack trace:
#0 /homepages/21/d858425693/htdocs/wp-content/themes/enfold/framework/php/widgets/widget-classes/class-avia-mailchimp.php(153): strip_tags()
#1 /homepages/21/d858425693/htdocs/wp-includes/class-wp-widget.php(535): aviaFramework\widgets\avia_mailchimp_widget->form()
#2 /homepages/21/d858425693/htdocs/wp-admin/includes/widgets.php(276): WP_Widget->form_callback()
#3 /homepages/21/d858425693/htdocs/wp-includes/widgets.php(845): wp_widget_control()
#4 /homepages/21/d858425693/htdocs/wp-admin/includes/widgets.php(119): dynamic_sidebar()
#5 /homepages/21/d858425693/htdocs/wp-admin/widgets-form.php(552): wp_list_widget_controls()
#6 /homepages/21/d858425693/htdocs/wp-admin/widgets.php(34): require(‘/homepages/21/d…’)
#7 {main}
thrown
Thank you for your helpTopic: Enfold memory error
Hi – my system reports kind of enfold memory error? This is with regard to the main page.
By clicking on the edit-button of the main page, an error screen appears.
Error code, see Private Content. How can I solve this problem?
Topic: Checkout problem
Hi Enfold Support,
I’m using Flux Checkout with the Enfold theme, and I’ve confirmed with the plugin developers that Flux works fine with WooCommerce’s default Storefront theme. The issues only occur when Enfold is active.
Specifically, Enfold is:
Injecting custom checkout styling that breaks the field layout and button styles in Flux Checkout.
Loading checkout-related scripts which cause conflicts and make some buttons unclickable.Could you please provide a way to disable Enfold’s checkout styling and scripts so that Flux Checkout can render properly? Ideally, Enfold should allow me to opt out of its custom checkout modifications so that third-party checkout plugins like Flux Checkout can function as intended.
Thank you for your help!
Hi Team Enfold, Kriesi,
I have been using Enfold for 10 years(?). I have no idea when it came out, but it feels like forever. Having used it on three websites, two of which are still online (links below). I wanted to give some serious user feedback to you and your team since I hope it will help you to make it even better! I totally understand if there is no room for such a thing in your team. So I’m simply sending it as a “here you go, some seriously golden nuggets, do with it what you want” type of email :)
Websites:
MeshMasters.com (up2date)
RobertBerrier.com (old, and needs an update)Before I slap all the feedback points. Know that I am a (3D) artist, with limited web coding knowledge. So I don’t know what is possible or not.
—
1) Often I want to have media like an image or video, but also text fields, to the left or right, or center of a section or part of the website, but in a smaller size than the container it’s in. For example, if I have a full width color section. Within that color section, I can use a 1/4 container with the media/text in it, another 3/4 container next to it to “force” it to be at a smaller size to the left or right of that color section. Or, I want to have a 1/3 sized media/text in the center of the website, so I put two 1/5 containers to the left and right. This “works”, but it’s finicky. I often rather want the media to be at a fixed (smaller) size, no matter what is next to it. Even better would be a percentage. Eg, this media should always be 20% size compared to the browser window, or 20% of the container it’s in. The container it is in would still be its max possible size. But it will try to get close to the smaller percentage or pixel size. This can somewhat be done with using a smaller resolution image. But this is also finicky because of all the different screen resolutions, especially in our age with HD vs 4k. So, a better way to “size” down images without having to container it. Perhaps a percentage setting in the media element itself.
—
2) The ability to have (all) elements be in the center of of the page. Eg, media, containers, buttons. If they are smaller than the color section or container they are in. I often want them in the center of that color section or container. No matter what responsive size we are in. Currently I need to do this with “buffer” containers to try and align it to the setting.
I have created some CSS code with a Class ID that I can add to a color section. Then everything in that color section will be centered. But I believe this should be a default setting within a color section and containers. Eg, “align all content within this container/color section to the Left/Center/Right.
—
3) I use CSS code to not have the header be transparent. I would say this should be an option in the Enfold settings. Rather than needing to code.
#header {
background-color: #1d1d40; /* This is needed for the opacity change */
opacity: 1 !important;
}4) When text is in BOLD or STRONG. It gets an assigned color from the theme options. Not a bad idea, but it is a shared color with I believe “Primary Color – Font color for links, dropcaps and other elements” This means we users have less control over how text and it’s colors looks like. I suggest that BOLD and STRONG has a separate color option within the Theme color settings. In my opinion, links and BOLD should be seen as two different things to customize. I currently use CSS code to adjust this.
—
5) For all my websites I have a max website width setting, as set in the Enfold settings. But sometimes, I want a color section to use its own unique size. For example, you will see on MeshMasters.com that the portfolio section is a full-width color section. While the contact section at the button is a bit smaller than the website’s width settings. Having this as a setting in color sections would give people more options to make cool layouts. Currently I have this CSS code for this:
/* ========================================== */
/* === Color sections width additions === */
/* ========================================== *//* === Full width, no padding === */
#fullwidth-container-nopadding .container {
width: 100% !important;
min-width: 100%;
padding: 0;
margin: 0;
}/* === Full width, small padding === */
#fullwidth-container-smallpadding .container {
width: 100% !important;
min-width: 100%;
padding: 10px;
margin: 10px;
}/* === Full width, default padding === */
#fullwidth-container .container {
width: 100% !important;
min-width: 100%;
}—
5) Similar to the point above. I want my blog posts to be a smaller width. Since it makes reading large pieces of text easier. So having a separate width setting for blog posts could be interesting to add. For example, the main website is at say 85% width. But perhaps all blog posts are at 70%.
—
6) Font sizes on the main page (or landing pages) are often large. To grab attention with cool copy writing that sells. These are often smaller pieces of text. But on blog posts you have large pieces of text. And so a smaller font size makes it more readable. Since there is only one BODY or P font size for the entire website. You are stuck in choosing one for all pages. I currently made CSS code so on blog posts all font sizes are 95% or 90% smaller than the rest of the website. Perhaps this could also be a setting in the Enfold theme settings. Eg “blog posts font sizes”.
—
7) There are currently three responsive break points in pixels. I believe it’s 990px and 768px and 480px. Perhaps this is the standard in web development. But the ability to change these website wide would be great. Eg, If I change the 990px to say 800px in the enfold settings. Then on all other instances where this is used, like in color sections, containers, etc. That value is also reflected there in the UI.
—
8) When columns break down for responsiveness. They break down into a single column. Eg, a column of 3 containers, becomes a column of 1 with 3 containers below each other. Having options to control to how many columns it breaks would be great. Eg, 4 columns of containers next to each other (4×1). Could be 2 columns of 2 containers next to each other. Eg, 2×2. Instead of 1×4. More controls options for this would be AMAZING!
—
9) fyi, I used CSS code to adjust the masonry gap size (to 4 px). It’s a small thing, but perhaps a quick win to add to the Masonry settings and so to make the theme better.
—
10) another small thing. I use CSS code to remove the Gallery border.
—
11) I use CSS code to remove the Blog button hover effect. Perhaps also a quick win to add to Enfold.
/* === Hover icon disable === */
.slide-entry-wrap .image-overlay-inside:before { display: none; }/* === Hover overlay color === */
.image-overlay { background: #0f0f26; }—
12) Very similar where I remove the Featured Image effect:
.big-preview.single-big a{
pointer-events:none!important;
}—
13) And also the blog page excerpts and dates:
/* === Remove blog page excerpts === */
.blog .slide-entry-excerpt { display: none; }/* === Remove blog page dates === */
.slide-meta { display: none !important; }—
14) Tables are very difficult to adjust. There is no control over it’s color and borders. I use quite a lot of CSS code to adjust them. Perhaps this should be an entire section in the Enfold themes to control them?
I currently use code to:
– Adjust colors for: General cells, uneven cells, even cells, header cells, the borders
– Thickness of borders and its colors
– Give transparency to cells.
– And then to apply these settings to each different theme area (Logo area, main area, alternative area, footer area, socket area)—
15) the button element is missing padding and margin settings (and maybe also alignment settings?)
—
16) There are default padding settings for Color Sections. 0%, 20%, Default(?), 70% and 130%. It would be great if we can adjust these globally in the Enfold Settings. And ofcourse these changes are reflected in the Color Section padding settings. For example, Perhaps I want the default to be 60%, the large 100% and the extra large 150%
Yes, I am aware you can put in custom values in the element itself. But it’s better to align values website wide.
—
That’s it. I hope it helps and you can improve Enfold to an even better edition!
Robert Berrier
