-
Search Results
-
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
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
I 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]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
Topic: Website soft brick
Hi all – I soft bricked my website by using the reset button in enfold backend. All custom CSS and settings is lost and now I am trying to rebuild all. Lots of things I was able to handle by my self but some I don’t know how to fix.
First problem: I am missing that when the first section of a page has blue background color, the font type is white. See example in PC.
Have installed a plug-in that uses a pop-up box when someone tries to cancel a subscription/membership in Woo commerce. The pop-up doesn’t appear when cancel button is selected. I changed theme and it worked so I believe something in the enfold theme is stopping the pop-up from displaying.








