Fatal error since update

  • Resolved temerity001

    (@temerity001)


    2 days, 17 hours ago

    Hello,

    I have had to disable Better Docs. I have the following data when in debug mode. I believe we had the problem before and the site was rolled back. I don’t know if the fault was ever fixed.

    Current WP 7.0. All plugins are up-to-date.

    Thanks.

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/ContainerBuilder.php on line 275

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Source/ReflectionBasedAutowiring.php on line 18

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Source/Autowiring.php on line 23

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Source/DefinitionArray.php on line 43

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Proxy/ProxyFactory.php on line 43

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Container.php on line 97

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Container.php on line 98

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Container.php on line 99

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/ObjectDefinition.php on line 71

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/ObjectDefinition.php on line 87

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/ObjectDefinition.php on line 185

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Resolver/ObjectCreator.php on line 215

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Resolver/ParameterResolver.php on line 39

    Deprecated: WPDeveloper\BetterDocs\Dependencies\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/includes/Dependencies/DI/Definition/Resolver/ParameterResolver.php on line 40

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-jetpack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sites/3a/2/23414174f6/public_html/wp-includes/functions.php on line 6170

    Deprecated: WCJ_Products_Crowdfunding_Shortcodes::get_product_orders_data(): Implicitly marking parameter $return_value as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/booster-plus-for-woocommerce/includes/shortcodes/class-wcj-products-crowdfunding-shortcodes.php on line 103

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sites/3a/2/23414174f6/public_html/wp-includes/functions.php on line 6170

    Deprecated: WCJ_Checkout_Custom_Fields::add_custom_fields_to_order_display(): Implicitly marking parameter $section as nullable is deprecated, the explicit nullable type must be used instead in /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/booster-plus-for-woocommerce/includes/class-wcj-checkout-custom-fields.php on line 415

    Warning: Cannot modify header information - headers already sent by (output started at /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/vendor/composer/ClassLoader.php:576) in /usr/share/php/wp-stack-cache.php on line 1636

    Warning: Cannot modify header information - headers already sent by (output started at /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/vendor/composer/ClassLoader.php:576) in /usr/share/php/wp-stack-cache.php on line 1637

    Warning: Cannot modify header information - headers already sent by (output started at /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/vendor/composer/ClassLoader.php:576) in /usr/share/php/wp-stack-cache.php on line 1636

    Warning: Cannot modify header information - headers already sent by (output started at /home/sites/3a/2/23414174f6/public_html/wp-content/plugins/betterdocs/vendor/composer/ClassLoader.php:576) in /usr/share/php/wp-stack-cache.php on line 1637

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 524288 bytes) in /home/sites/3a/2/23414174f6/public_html/wp-content/themes/oceanwp/inc/customizer/options/header.php on line 3835

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Pial

    (@iapial)

    2 days, 15 hours ago

    Hey @temerity001

    Really sorry for the inconvenience.

    We’ve identified the issue, it’s triggered specifically on PHP 8.4+, and we’ve already applied a fix. We’ll be releasing an update very soon.

    In the meantime, please use this development version: https://d.pr/f/5wyTti

    Two things worth addressing on your end based on your debug log:

    1. PHP memory limit — your site is might be on lower memory for a stack with WooCommerce + multiple plugins. We’d recommend raising it to at least 512 MB. Easiest path is asking your host to update memory_limit in php.ini, or add this to your wp-config.php:

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

    2. OceanWP memory error — the fatal in your log comes from OceanWP, likely a side effect of the issue we’re fixing. If it persists after installing the dev version and bumping memory, try switching to a default WordPress theme briefly to rule out a theme-specific interaction.

    Let us know how it goes.

    Thread Starter temerity001

    (@temerity001)

    2 days ago

    Good Morning. I appreciate your timely response and the fix. I did update the plugin and then increased the memory to 512M. It now works as expected. Thanks again.

    Plugin Support Pial

    (@iapial)

    1 day, 23 hours ago

    Hi @temerity001 ,

    I’m really glad to hear that everything is working properly now.

    I also sincerely appreciate your patience, understanding, and cooperation while we worked through the issue. And thank you so much for taking the time to leave a review and share your feedback. It truly means a lot to me personally and to our entire team. Supportive feedback like yours genuinely motivates us to keep improving and helping our users in the best way possible.

    Please feel free to reach out to us anytime if you ever face any issues or need any assistance in the future. We’ll always be happy to help.

    Have a wonderful day!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.