Viewing 30 results - 31 through 60 (of 229 total)
1 2 3 … 6 7 8
  • Author
    Search Results
  • July 11, 2022 at 4:02 pm #1357965

    In reply to: php 7.4 or php 8.0

    Mounia83
    This reply has been marked as private.
    June 15, 2022 at 7:46 pm #1355385

    Topic: Fatal Error after Url Change

    in forum Enfold
    Adtime
    Participant

    Hi guys,

    we wanted to put a website online today, but after changing the url in the database (Better Search & Replace), the following error occurs:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 268435464 bytes) in /html/wordpress/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-element-templates.php on line 3531

    Increasing the memory doesn’t make sense, Enfold goes into an infinite loop (while(true)) in said line because it can’t find the correct content templates anymore.

    The changes of the Url’s in the database look so far correctly / as with other sites also.

    An update to Enfold 5 was also tried. Downgrades also.

    Deactivating the plugins does not help. All other 1st level stuff do not work either.

    I can provide a test environment.

    The page is very large (+wpml) and putting it online is urgent.

    Please help.

    <!–
    Debugging Info for Theme support:

    Theme: Enfold
    Version: 4.9.2.2
    Installed: enfold
    AviaFramework Version: 5.0
    AviaBuilder Version: 4.8
    aviaElementManager Version: 1.0.1
    – – – – – – – – – – –
    ChildTheme: Enfold Child
    ChildTheme Version: 1.0
    ChildTheme Installed: enfold

    ML:256-PU:120-PLA:17
    WP:6.0
    Compress: CSS:all theme files – JS:all theme files
    Updates: enabled – token has changed and not verified
    PLAu:16
    –>

    April 28, 2022 at 5:02 pm #1349850

    In reply to: Enfold Page Builder will Not Load or Enfold Theme settings fail to Save etc

    Rikard

    Hi,

    Thanks for the update. I’m seeing this on your site now:

    Fatal error: Allowed memory size of 2097152 bytes exhausted (tried to allocate 20480 bytes) in /var/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/grid_row/cell.php on line 969

    Please try to increase the memory allocated to PHP on your installation: https://wordpress.org/support/article/editing-wp-config-php/. If you need help with that, then please try reaching out to your hosting provider.

    Best regards,
    Rikard

    January 27, 2022 at 12:48 am #1337379

    In reply to: Couple Issues with Enfold Install

    acscreativenew

    Hi,

    Sorry, login should be good now.

    I have turned off all the plugins and im still getting the same error. Also, debugging is turned on now.

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 16384 bytes) in /home/devcganet/public_html/wp-includes/formatting.php on line 486

    January 25, 2022 at 7:55 pm #1337155

    Topic: Couple Issues with Enfold Install

    in forum Enfold
    acscreativenew
    Participant

    Hi, so im running enfold and have run into a couple of issues on my website.

    First when I try to save a page with the “social buttons” element the page will not save.
    Second the search is a little messed up. When i use the search it will drop down the ajax search but when i view all results it throws an error.

    Can you help me take a look at these issues on my website?

    I keep getting these errors within my logs

    [25-Jan-2022 18:02:59 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 16384 bytes) in /home/devcganet/public_html/wp-includes/formatting.php on line 486

    Here are my PHP settings

    display_errors = Off
    max_execution_time = 90
    max_input_time = 90
    max_input_vars = 4000
    memory_limit = 512M
    post_max_size = 256M
    session.gc_maxlifetime = 1440
    session.save_path = “/var/cpanel/php/sessions/ea-php74”
    upload_max_filesize = 60M
    zlib.output_compression = Off

    Thanks
    -Dan

    October 20, 2021 at 4:10 pm #1325755

    Topic: Enfold – debug error showing whne upgrade to php 7.4

    in forum Enfold
    johnoros
    Participant

    Hello,

    I am currently running WordPress 5.8.1 and Enfold 4.8.6.5

    When I enable PHP 7.4 on my VPS my site throws the following errors. How can I resolve the error related to Enfold.

    Errors I am receiving with debug mode turned on
    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 32768 bytes) in /home/mysite/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-html-helper.php on line 1701

    Any help much appreciated,
    Thanks,
    John O Connor

    September 16, 2021 at 5:18 am #1321130

    In reply to: custom page template not using full width

    S-edwards

    It seems that we are having much larger issues now. Im not sure if its related, but whenever i try to update a page i get errors. At the moment is says

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32768 bytes) in /public_html/wp-includes/wp-db.php on line 2022
    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    on the front end im getting:

    Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /public_html/wp-includes/functions.php on line 5107

    even though its only a few dozen lines long.

    Also, i had Disable Gutenberg plugin installed, which i have deactivated along with all the other plugins. However the page backend is still using defalt wordpress editor andnot Guttenberg. I have no idea whats going on or how to fix it

    August 20, 2021 at 8:50 am #1317584

    Topic: PHP Fatal error: Allowed memory issue on editor

    in forum Enfold
    Rustum
    Participant

    Hi Support

    We have an error on our site. This happens when we edit a page and then click on Mailchimp Signin or Page Content to edit it’s settings.

    [20-Aug-2021 06:42:33 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 57344 bytes) in /home/michanicco/public_html/wp-includes/wp-db.php on line 2022

    The PHP Memory Limit: 4000M
    The PHP Version: 7.4.19
    Enfold Version: 4.8.6.2
    Total Pages: 2888
    Total Posts: 56
    .htaccess: php_value memory_limit 4000M
    .user.ini: memory_limit = 4000M
    php.ini: memory_limit = 4000M
    wp-config.php: define( ‘WP_MEMORY_LIMIT’, ‘4000M’ );

    Please advise what more we need to do here to get this to work ?

    Thank you.

    • This topic was modified 4 years, 5 months ago by Rustum.
    August 6, 2021 at 8:17 am #1314767

    In reply to: After updating to 4.8.4 a whole section of my website is not working

    computereze

    for the Lifesupport website:

    I have done some digging through debug and get the following error:
    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32768 bytes) in /home/lifesupportuk/public_html/wp-admin/includes/theme.php on line 739

    Line 739 of code shows:
    ‘hasPackage’ => isset( $updates[ $slug ] ) && ! empty( $updates[ $slug ][‘package’] ),

    Not sure what’s happening here as this has only happened since 4.8.6. nothing else on the site has changed other than the enfold update

    Hope you can help

    • This reply was modified 4 years, 5 months ago by computereze.
    May 6, 2021 at 5:42 pm #1298846

    Topic: Fatal error: Allowed memory size of 15728640 bytes exhausted

    in forum Enfold
    mattvisa
    Participant

    Hello,

    My site went down Tuesday, and I was able to delete child theme and restore an old DB I had and now site is back up (even though I lost all my theme settings – when I restore them, site goes blank.

    However, I am still getting this fatal error in the bottom of the pages, see here:

    Home

    Fatal error: Allowed memory size of 15728640 bytes exhausted (tried to allocate 1052672 bytes) in /home/customer/www/cityflourish.com/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/external/JSqueeze.php on line 484

    May 4, 2021 at 4:01 pm #1298328

    Topic: Fatal memory error

    in forum Enfold
    mattvisa
    Participant

    Hi
    I am having issue with
    cityflourish.com

    Fatal error: Allowed memory size of 15728640 bytes exhausted (tried to allocate 765952 bytes) in /home/customer/www/cityflourish.com/public_html/wp-includes/functions.php on line 599

    I tried disabling plugins and issue persists

    February 10, 2021 at 3:51 pm #1279521

    In reply to: There has been a critical error on this website

    alanlodge

    hello again.

    The backend of all this is a little foreign to me. But i have found the error log and think this is what is meant: Have no idea how to interpres it though. I this helpful to know what’s to do?

    [08-Feb-2021 16:06:46 UTC] PHP Warning: Declaration of WP_CLI\LanguagePackUpgrader::download_package($package) should be compatible with WP_Upgrader::download_package($package, $check_signatures = false, $hook_extra = Array) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/wp-cli/vendor/wp-cli/language-command/src/WP_CLI/LanguagePackUpgrader.php on line 23
    [09-Feb-2021 06:23:55 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32768 bytes) in /home/alanlodge/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/magazine/magazine.php on line 1173
    [09-Feb-2021 06:24:03 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32768 bytes) in /home/alanlodge/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/magazine/magazine.php on line 1173
    [10-Feb-2021 06:19:34 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32768 bytes) in /home/alanlodge/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/heading/heading.php on line 270
    [10-Feb-2021 06:19:38 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes) in /home/alanlodge/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/headline_rotator/headline_rotator.php on line 306

    November 11, 2020 at 12:21 am #1259724

    In reply to: HTTP ERROR 500 — on all product edit pages

    Victoria

    Hi JenniferHillberg,

    Well, the fatal errors come from some plugins:
    [10-Nov-2020 14:26:11 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home3/ountain1/public_html/wp-content/plugins/facebook-for-woocommerce/includes/Products/FBCategories.php on line 47
    [10-Nov-2020 14:26:11 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32768 bytes) in /home3/ountain1/public_html/wp-admin/includes/class-wp-upgrader.php on line 870

    Please disable them and see if it works.
    Best regards,
    Victoria

    November 10, 2020 at 4:29 pm #1259605

    In reply to: HTTP ERROR 500 — on all product edit pages

    JenniferHillberg

    [10-Nov-2020 14:25:36 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:36 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:36 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:36 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:43 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:44 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:46 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:47 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:47 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:47 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:47 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:48 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:25:48 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:25:48 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:25:48 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:25:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home3/ountain1/public_html/wp-content/plugins/facebook-for-woocommerce/includes/Products/FBCategories.php on line 47
    [10-Nov-2020 14:25:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home3/ountain1/public_html/wp-includes/class-wp-recovery-mode.php on line 366
    [10-Nov-2020 14:25:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 434176 bytes) in Unknown on line 0
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:08 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:09 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:09 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:09 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:09 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:10 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:10 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:10 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:10 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:11 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home3/ountain1/public_html/wp-content/plugins/facebook-for-woocommerce/includes/Products/FBCategories.php on line 47
    [10-Nov-2020 14:26:11 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32768 bytes) in /home3/ountain1/public_html/wp-admin/includes/class-wp-upgrader.php on line 870
    [10-Nov-2020 14:26:20 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:20 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:20 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:20 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:25 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:25 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:25 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:25 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:26:59 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:06 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:07 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:08 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:08 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:08 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:08 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in /home3/ountain1/public_html/wp-config.php on line 92
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant AUTOSAVE_INTERVAL already defined in /home3/ountain1/public_html/wp-config.php on line 93
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant WP_POST_REVISIONS already defined in /home3/ountain1/public_html/wp-config.php on line 94
    [10-Nov-2020 14:27:13 UTC] PHP Notice: Constant EMPTY_TRASH_DAYS already defined in /home3/ountain1/public_html/wp-config.php on line 95
    [10-Nov-2020 14:27:14 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home3/ountain1/public_html/wp-content/plugins/facebook-for-woocommerce/includes/Products/FBCategories.php on line 47
    [10-Nov-2020 14:27:14 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home3/ountain1/public_html/wp-includes/class-wp-fatal-error-handler.php on line 72
    [10-Nov-2020 14:27:14 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 434176 bytes) in Unknown on line 0

    October 28, 2020 at 11:30 pm #1256538

    Topic: Enfold causing Fatal error: Allowed memory size of x bytes exhausted

    in forum Enfold
    Cohete.Net
    Participant

    I have a WordPress site with enfold that has been kinda slow from the beginning, thinking that the long load times were caused by the server i moved to another one (Digitalocean Ubuntu droplet) where, after moving there the site, doesn’t load, and shows the error “Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 53944936 bytes) in /var/www/dropletlatina.coheteam.com/wp-includes/wp-db.php on line 1485”, deactivating plugins doesn’t affect the problem in any way, changing to the default WordPress theme resolves the problem immediately and the site works perfectly on the new server, activating Enfold again restores the problem.

    I really like using Enfold, it’s the best theme i’ve found and i would really like to solve this problem, is there something i can check in order to solve it?

    EDIT:Forgot to mention that i’ve tried the tipycal solution of increasing the php memory limit, in this moment it’s in 256M which is already too big for a site like this one.

    EDIT2: Turns out the problem didn’t had to do with Enfold itself, the reason i thought that was that, after changing the Enfold theme the site seemed to work normal, but after some time the problem reappeared, so it’s likely a weird instance of a wordpress bug, i’m sorry for all the fuzz!

    • This topic was modified 5 years, 2 months ago by Cohete.Net.
    October 4, 2020 at 3:25 pm #1250415

    In reply to: admin-ajax.php error 500 – too many pages?

    ottwebtech

    Hi Victoria
    Thank you for the response.
    server logs shows:

    [04-Oct-2020 12:34:23 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 69632 bytes) in /home/mylocksuk/public_html/wp-includes/wp-db.php on line 1999
    [04-Oct-2020 12:34:23 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 65536 bytes) in /home/mylocksuk/public_html/wp-includes/functions.php on line 4669
    [04-Oct-2020 12:34:23 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

    the things is – everything setup to memory limit of 512M
    both php.ini (cpanel) & wp-config.php
    i can confirm wordpress using the 512M because if i comment out those from wp-config
    define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’); define(‘WP_MEMORY_LIMIT’, ‘512M’);
    im start to getting the “PHP Fatal error” on ALB pages.

    also created a phpinfo(); test file that shows that 512M is indeed in use.

    I have 3500 pages with lots of images (9G) if that related – But got a pretty decent VPS. lots of free memory and disk space.
    everything running smooth beside that issue.
    Hosting at Fastcomet, the’re support already try to figure it out without any luck. saying not a vps related issue.

    Really need your help :)
    Thank you.

    September 17, 2020 at 10:07 pm #1246603

    Topic: Fatal error: Allowed memory size

    in forum Enfold
    JEFFIRE
    Participant

    Hi there,
    im getting this error:
    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 40960 bytes) in /www/wp-includes/wp-db.php on line 1989

    It prevents me to edit pages and acces to Enfold section.
    If i revert i revert to basic wp theme all is good.

    Ive upped wp-config, php.ini, .htaccess –>1024mb.

    August 4, 2020 at 2:03 am #1235010

    Topic: Fatal Error: Allowed Memory Size Exhausted

    in forum Enfold
    djugut
    Participant

    I am working on a site and when i try to activate the Enfold theme or Enfold Child theme, I am encountering this fatal error.

    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 8192 bytes) in /home/jsimp/public_html/new_pg/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/html-helper.class.php on line 2402

    you can visit https://imp.cv/new_pg/wp-admin/themes.php?action=activate&stylesheet=enfold-child&_wpnonce=505e2a5af1 to see the issue.

    Any ideas?

    Thanks,

    José Figueiredo

    July 23, 2020 at 12:21 am #1232457

    Topic: Allowed memory size exhausted

    in forum Enfold
    GaianHelmers
    Participant

    I’ve been trying to figure out how to reduce the memory demand of Enfold.
    -I’ve added the WP Super Cache as was recommended.
    -Got my host to increase the PHP memory limit to 512.
    -Set the Enfold editor to Classic
    -Enabled debugging, but also looked through the server log.

    This is one of the most frequent alerts I receive when trying to navigate the back-end dashboard. However, they are not the only errors. I see many come from the Avia Layout Editor as well.

    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 20480 bytes) in xxxxxxx/wp-includes/plugin.php on line 182

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 20480 bytes) in xxxxxxx/wp-includes/class-wp-fatal-error-handler.php on line 67

    What is the actual memory demand from Enfold systems? My host says that I should try and reduce the memory demand as it causes huge overhead for my users, however, I am also nearly unable to edit and post to my site.

    Furthermore, though I’m not sure how to test if this is also a memory issue, when I edit blocks often times the window loads blank. It’s incredibly tedious to have to open and close a block edit over and over until the window actually opens.

    I have no plugins enabled, only the Enfold theme. I did have a previous custom theme and website before I updated to this theme, however, I understand that once you enable a different theme, there should be little overlap in code and systems…

    June 17, 2020 at 6:08 pm #1223468

    Topic: Upgrading PHP Version Above 7.1 Breaks the site

    in forum Enfold
    ebsportsart
    Participant

    Hey guys,

    Whenever I go to update my site over PHP version 7.1 my site breaks. Any idea what is going on?

    I get this error message..

    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 32768 bytes) in /home/aecyberpub/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/html-helper.class.php on line 1299

    Thanks

    Jim

    May 27, 2020 at 4:12 pm #1217007

    Topic: Trouble after update

    in forum Enfold
    Jak73
    Participant

    Hi,
    I updated enfold and I’m getting errors from time to time like this:
    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 28672 bytes) in /www/htdocs/——–/wp-admin/menu.php on line 68
    Die Website hat technische Schwierigkeiten. Bitte prüfen Sie das E-Mail-Postfach des Website-Administrators, um dort weitere Anweisungen zu finden.

    —

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in /www/htdocs/——-/wp-admin/includes/deprecated.php on line 757

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in /www/htdocs/——-/wp-includes/class-wp-fatal-error-handler.php on line 44

    When I reload error goes away. But this is still an issue to me.

    What can I do?

    kind regards

    Jak

    • This topic was modified 5 years, 8 months ago by Jak73.
    May 25, 2020 at 8:45 am #1216020

    In reply to: Fatal error: /config-templatebuilder/avia-shortcodes

    Nikko

    Hi peterolle,

    It’s this fatal error that shows it, specifically 41943040:

    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 12288 bytes) in /public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.php on line 532

    Although adding something like this in the wp-config.php file most of the times work (try using lower values like 64M or 128M:

    define( 'WP_MEMORY_LIMIT', '512M' );

    But if it doesn’t please contact your host as they might not permit high memory usage.

    Best regards,
    Nikko

    May 24, 2020 at 2:38 pm #1215772

    In reply to: Fatal error: /config-templatebuilder/avia-shortcodes

    Rikard

    Hi,

    Yes, and those results range back to 2011, it’s really strange that you didn’t notice that. I’m of course referring to other users having this problem with the current version of the theme and not running any plugins. A lack of memory is a very common in WordPress, so 181 results in 9 years is surprisingly small number.

    I can’t login to your site because of the problem you are having, how can we access your site and check your settings?

    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 12288 bytes) in /public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.php on line 532
    There has been a critical error on your website. Please check your site admin email inbox for instructions.

    Best regards,
    Rikard

    May 21, 2020 at 9:09 pm #1215083

    Topic: Fatal error: /config-templatebuilder/avia-shortcodes

    in forum Enfold
    peterolle
    Participant

    I keep getting this in any thing I try to do in the site. See a plugin description, activate a plugin, delete a widget, save a setting, etc…

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2621440 bytes) in /home/site/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_fullscreen/slideshow_fullscreen.php on line 624

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2621440 bytes) in /home/site/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/product_snippets/product_snippet_meta.php on line 89

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2621440 bytes) in /home/site/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/progressbar/progressbar.php on line 218

    And so on, errors and more errors.

    It is a clean install, there is nothing, just WordPress and Enfold, nothing else.

    I have assigned 512 in config.

    Is that a bug?
    How to fix it?

    Thanks.

    • This topic was modified 5 years, 8 months ago by Yigit.
    May 18, 2020 at 11:05 pm #1214130

    In reply to: Woocommerce

    BarbaraResl

    Fatal error: Allowed memory size of 58720256 bytes exhausted (tried to allocate 20480 bytes) in /home/.sites/29/site1673/web/NEU/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/popup-templates.class.php on line 156 Fatal error: Allowed memory size of 58720256 bytes exhausted (tried to allocate 20480 bytes) in /home/.sites/29/site1673/web/NEU/wp-includes/class-wp-fatal-error-handler.php on line 67

    May 9, 2020 at 11:12 pm #1211530

    In reply to: critical error on your website(s)

    Nikko

    Hi Paul,

    Thanks for that, the error listed is this one:

    PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 15728672 bytes) in /public_html/wp-includes/wp-db.php on line 1390

    It seems that the memory your site is using is more than what’s it allocated that’s why it fails.
    To fix it, please do the following recommendation: https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/

    Best regards,
    Nikko

    May 8, 2020 at 7:51 am #1210946

    Topic: Fatal error Allowed memory size of 268435456 bytes exhausted

    in forum Enfold
    VBV-Hofheim
    Participant

    Leider macht nun unsere Webseite Probleme, und zwar bekomme ich, wenn ich an einer Stelle wenn etwas bearbeiten möchte, folgende Fehlermeldung:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 106496 bytes) in /homepages/34/d104425903/htdocs/clickandbuilds/VolksBildungsVereinHofheim/wp-includes/wp-db.php on line 1995

    Danke für eine schnelle Hilfe

    Svenja

    March 11, 2020 at 11:03 am #1192191

    In reply to: API key

    Eric Helander
    Guest
    This reply has been marked as private.
    December 8, 2019 at 9:50 pm #1163905

    In reply to: Bild einfügen funktionier nicht mehr

    Photoart-Huebner
    This reply has been marked as private.
    November 25, 2019 at 12:53 pm #1159836

    In reply to: Avia Layout Builder Blank Edit Boxes

    Ismael

    Hi,

    UPDATE: The server is still running out of memory during the database query because the maximum memory limit is still set to 268435456 bytes or 268MB instead of the 512MB that we set in the .htaccess file. The memory adjustment is reflected in the PHP info variables, but it doesn’t really get applied in the environment. You should ask your hosting provider if it’s possible to increase the PHP memory limit and if so, ask them how because all the attempts that we made to increase it is not working.

    [25-Nov-2019 10:46:07 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home/wua4p6lmxmxf/public_html/wp-includes/wp-db.php on line 1972

    Best regards,
    Ismael

  • Author
    Search Results
Viewing 30 results - 31 through 60 (of 229 total)
1 2 3 … 6 7 8