Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • June 15, 2022 at 7:46 pm #1355385
    Adtime

    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
    –>

    June 15, 2022 at 8:31 pm #1355395
    Adtime

    Ok I have now deleted all “_aviaLayoutBuilderCleanData” from the post_meta table for testing and the error (including all content of that page) disappears.

    When I save a page, the “_aviaLayoutBuilderCleanData” is then created again, and the page shows up with content.

    Currently, I have adjusted line 69 of the template-builder.php, so that the content is read directly:
    $content = apply_filters( 'avia_builder_precompile', get_the_content() );

    Is there anything here that speaks against it (with regard to WPML) to leave it as it is?
    Is there any way to regenerate all entries at once?

    June 16, 2022 at 1:50 pm #1355489
    Adtime

    So that we don’t have any changes in the core of Enfold, everything has been restored back to original. We click through each page to restore the deleted entries in the post_meta. For this to work, we had to disable Custom Elements in the Settings (because otherwise some pages wouldn’t open even in the backend). We don’t really need the custom elements.

    Still asking for control/feedback, gladly also in a test environment. We want to make sure that our solution strategy does not lead to further discrepancies in the database.

    June 16, 2022 at 4:20 pm #1355514
    Adtime

    Can be closed. Search & Replace messed up with only a few, well hidden database entries.

    June 18, 2022 at 4:45 am #1355657
    Mike

    Hi,
    Glad to hear that you have this sorted out, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

    Best regards,
    Mike

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error after Url Change’ is closed to new replies.