-
Search Results
-
I use the WP SMTP Mail plugin.
Enfold is generating regular errors from the plugin. Here’s the error report:
Debug Event Details
Type
Error
Date
July 7, 2025 at 2:06 pm
Content
Mailer: Other SMTP
SMTP Error: data not accepted.SMTP server error: DATA END command failed Detail: Spam message rejected
SMTP code: 554 Additional SMTP info: 5.7.1
Source
Enfold
/home/storage/322/4077322/user/htdocs/wp-content/themes/enfold/framework/php/class-form-generator.php (line: 1485)I just found out the errors actually started in April 2024 but as I use the free version of the plugin I don’t get notified via email when an error occurs so I’d only notice it if I logged in to the WP admin panel and there had been a recent error (as I did today). Unfortunately when there is a successful send of an email the plugin clears the error flag from the admin bar which is why I only discovered this today.
The errors are generated at random intervals. There have been one a day for the past 3 days, prior to that it was June 30, two on June 28, two on June 26, June 25, June 24, June 22, June 3, May 31 etc.
Any ideas?
WordPress 6.8.1, Enfold 7.1.1
Nach dem Update von Enfold erscheint folgender PHP-Fehler im Frontend und/oder Backend und nach Aktivierung von WP Rocket kam es zu einem Error 500.
Nach einer Analyse mit Hilfe v. ChatGPT (sorry, hab nur eingeschränkte php-Kenntnisse) kam die KI zu diesem Schluss:Warning: Trying to access array offset on value of type null in /wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/helper-templates/function-set-avia-frontend.php on line [XY]Ursache:
In der Funktion avia_get_option() wird folgender Code ausgeführt:$pages[] = 'avia'; $pages = array_unique( array_merge( $pages, array_keys( $avia->options ) ) );Wenn $avia->options nicht gesetzt oder null ist, erzeugt array_keys( $avia->options ) eine PHP-Warning.
Lösungsvorschlag:
Absicherung der Zeile, z.B. so:$pages[] = 'avia'; if ( isset( $avia->options ) && is_array( $avia->options ) ) { $pages = array_unique( array_merge( $pages, array_keys( $avia->options ) ) ); }So wird der Fehler zuverlässig vermieden, auch wenn $avia->options noch nicht initialisiert wurde.
System:
Enfold Version: 7.1.1
WP Rocket:
PHP Version: 8.2.28
Hosting: HetznerUm den Error 500 und die auftretenden PHP-Warnungen in Verbindung mit Enfold zu identifizieren, haben wir folgende Schritte unternommen:
1. WP_DEBUG aktiviert: Fehlerausgabe und Logging wurden aktiviert, um detaillierte Fehlermeldungen zu erhalten.
2. PHP-Log geprüft: Im Error-Log wurde die Warnung „Trying to access array offset on value of type null“ in der Datei function-set-avia-frontend.php gefunden.
3. Object Cache geprüft: Im Hetzner-Webhosting wurde überprüft, ob Redis oder Memcached aktiv sind. Redis war aktiviert, wurde aber testweise deaktiviert. Das Problem bestand weiterhin.
4. Theme-Tests: Das Enfold-Theme und das Enfold-Child-Theme wurden einzeln getestet. Der Error 500 blieb bestehen, unabhängig vom Theme.
5. Kritische Theme-Datei überprüft: Die Datei function-set-avia-frontend.php wurde gezielt untersucht und der problematische Quellcode identifiziert.
6. Optionen im Backend geprüft: Es wurde geprüft, ob veraltete oder ungültige Optionen (z. B. durch Caching) eine Rolle spielen könnten.Diese gezielten Analysen führten letztlich zur Identifikation des fehlerhaften Codes in der Theme-Funktion.
Hallo folgendes Problem.
Ich will auf meiner Reservierungsseite einfach das Datum einschränken in der Form tt.mm.jjjj
Z.B. nur von 08.08.2025 – 18.05.2025Was hab ich alles getan.
1. Supportseiten durchforstet
2. Child Theme angelegt
3. In functions.php folgendes eingetragen:/* Datum Platzhalter auf tt.mm.jjjj Format gesetzt */
add_filter(‘avf_datepicker_date_placeholder’, ‘new_date_placeholder’);
function new_date_placeholder() {
$placeholder = “TT.MM.JJJJ”;
return $placeholder;
}/* Datum Platzhalter auf tt.mm.jjjj Format gesetzt */
add_filter(‘avf_datepicker_dateformat’, ‘avf_change_datepicker_format’);
function avf_change_datepicker_format($date_format) {
$date_format = ‘dd.mm.yy’;
return $date_format;
}=> Format auf tt.mm.jjjj gesetzt, sowohl Platzhalter als auch bei der Übernahme.
4. Verschiedene Versuche das Datum via jQuery.datepicker zu ändern.
(DANK an Guenni007)
z.B. durchfunction my_datepicker_defaults() {
?>
<script type=”text/javascript”>
jQuery(document).ready(function(){
jQuery.datepicker.setDefaults({
minDate: 0,
maxDate: ‘1m’ )
});
});
</script>
<?php
}
add_action(‘wp_footer’, ‘my_datepicker_defaults’, 20);Hier sollte von heute auf 1 Monat eingeschränkt werden.
Leider keine Reaktion. Nicht durch private Mode, anderen Browser und Browserdaten löschen.Liebe Leute, alle Versuche via den Supportseiten eine funktionierende Lösung zu finden sind gescheitert.
Jetzt bitte erneut:
Wie schränke ich im Reservierungsformular am Datumsfeld den auszuwählenden Zeitraum ein?
Also nur Bereich zwischen 08.08.2025 – 18.08.20205 wählbar.Vielen Dank.
Hello Enfold Support Team,
I am trying to change the default cropped size of my featured images on single blog posts to a proper 16:9 aspect ratio, so that my 1280x720px images are displayed in full without any cropping.
I have tried two different PHP-based methods based on my research, but neither has worked on my local server environment (so caching should not be the issue).
Method 1: Modifying Existing Sizes
First, I tried to modify the existing theme sizes using the avf_modify_thumb_size filter. This was the code I used in my child theme’s functions.php (respectively in a Code Snippet Plugin):
function enfold_definitive_image_ratio_fix( $size_array ) { $size_array['entry_without_sidebar'] = array('width' => 1210, 'height' => 681); $size_array['entry_with_sidebar'] = array('width' => 845, 'height' => 475); return $size_array; } add_filter( 'avf_modify_thumb_size', 'enfold_definitive_image_ratio_fix', 10, 1 );When this code is active, the “Regenerate Thumbnails” page still shows the old default dimensions (e.g., 1210×423), so the filter does not seem to be applying correctly.
Method 2: Registering a New Size and Forcing its Use
As an alternative, I also tried registering a brand new 16:9 image size (custom-16-9-hero) and then used the avf_post_featured_image_size filter to force the theme to use it. Here is the code for that attempt:
function enfold_add_custom_image_sizes() { add_image_size( 'custom-16-9-hero', 1280, 720, true ); } add_action( 'after_setup_theme', 'enfold_add_custom_image_sizes' ); function enfold_use_custom_featured_image_size( $size ) { if ( is_singular('post') ) { return 'custom-16-9-hero'; } return $size; } add_filter( 'avf_post_featured_image_size', 'enfold_use_custom_featured_image_size', 10, 1 );With this method, the “Regenerate Thumbnails” plugin does show my new custom-16-9-hero – 1280 x 720 size and creates the files correctly after regenerating. However, the theme’s single post template still ignores the filter and continues to display the old default cropped image.
My question is:
In the latest version of Enfold, what is the definitive and correct method to ensure the featured image on a single post page is displayed at a custom 16:9 ratio?
Thank you very much for your help.
Kind regards,
DavidHi there,
I’m in the process of taking over a customer’s website that was previously managed by another provider. The site is using the Enfold theme, currently running on PHP 7.3. I’m having trouble backing up and restoring it on my server, which is running a newer PHP version.
I also downloaded the theme files from the existing site, but they’re not working correctly on my setup—likely due to outdated compatibility.
Would it be possible to purchase the latest version of the Enfold theme directly from you? If so, would the child theme from the original site still work once installed with the updated parent theme on my server?
Many thanks in advance for your help!
Hello,
I have created a webshop in Enfold and it’s online for some weeks now. Suddenly, when I now want to change a page, the Enfold builder keeps loading and loading. I do have an error:
[Wed Jun 25 17:15:24.316261 2025] [error] [pid 2241641] mod_proxy_fcgi.c(911): [client 80.69.66.83:0] AH01071: Got error ‘PHP message: PHP Warning: session_start(): open(/data/sites/web/plantenbloemenshopnl/tmp/sess_19d3d7d790334ec4a47fef4459fab6f9, O_RDWR) failed: File too large (27) in /data/sites/web/plantenbloemenshopnl/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.php on line 112; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /data/sites/web/plantenbloemenshopnl/tmp) in /data/sites/web/plantenbloemenshopnl/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.php on line 112’What could be wrong and what is the solution? Kindly need your support. I did have contact with the web hosting and I cannot change settings like WP_Memory_Limit.
Looking forward for your reply,
With kind regards,
ArjanSo I have Enfold 6.x / LS 7.12.4 on our live site, and Enfold 7.1.1 / LS 7.14.4 on a staging clone.
On both sites, I can open the wp-admin/admin.php?page=layerslider main admin page. But I can not edit a single LayerSlider slide any more. We rarely do this, so I don’t know when it stopped working.
When loading a slider for editing, the blue loading layer of LayerSlider just stays on top forever. No JS Console messages, and even with WP DEBUG enabled, no serverside errors or messages.
On the LayerSlider Admin page, an update of LS is announced, this is of course not yet included in Enfold. Would that solve the problem? What else could resolve this problem?
Regards
UlrichTopic: Error Saving Settings…
Hi, thanks for your help many years ago (see my email support from (Email address hidden if logged out) )!
We’ve updated this old client to v4.0 of Enfold, which has helped with PHP errors. But we’re still getting this error on every Save or Save Settings button:[Back Popup] : Saving didnt work!
Please reload the page and try againIt would also be good if we could register a support account, and possibly have this purchase tranferred to (Email address hidden if logged out) since the person who bought this plugin is no longer associated with this site.
And one more: is this v4.0 Enfold compatible with the latest WP 6.8.1 and PHP7.4? We’d like to move this to a more modern hosting platform. Thanks!












