Forum Replies Created

Viewing 15 replies - 1 through 15 (of 36 total)
  • Thread Starter Kevin Pfeifer

    (@beardcat)

    Thanks for the quick answer and the awesome support!

    We understand, that this is caused due to our custom implementation in the theme, so we will temporarily fix it like you explained via disabling it, logging in via the backend, and then re-apply the custom field logic.

    This worked fine.

    A long term solution will need to be done down the line to make this more upgrade safe.

    Thread Starter Kevin Pfeifer

    (@beardcat)

    To explain what happens in

    /wp-content/themes/theme/inc/custom-fields.php(18): require

    we are trying to fetch all segment lists from the repository like so to make it available in custom fields we programmatically added in our theme

      $segmentsRepository = \MailPoet\DI\ContainerWrapper::getInstance()->get(\MailPoet\Segments\SegmentsRepository::class);
    $segments = $segmentsRepository->findAll();

    $list_segments = [];
    if(!empty($segments) && is_array($segments)) {
    foreach($segments as $segment) {
    $list_segments[$segment->getId()] = $segment->getName();
    }
    }

    $options_general_fieldgroup->addField( 'select', __( 'MailPoet Liste', 'apostore' ), 'nl_list_id', array (
    'choices' => $list_segments
    ));
    Thread Starter Kevin Pfeifer

    (@beardcat)

    Can confirm, that 2.19.24 works fine.

    Happy to see, that you now correctly use class_exists() 😁

    Maybe a static analysis tool like PHPStan or even Rector would help you notice this before releasing 😜

    Thread Starter Kevin Pfeifer

    (@beardcat)

    Guys, all your class_exists() calls are wrong.

    You are inside a namespace, so you need reference the FQCN inside the class_exists() call, not just the classname.

    See https://3v4l.org/PO6VU#vnull

    you always just do this kind of check in your files

    namespace One_Onboarding\Core;

    use One_Onboarding\Admin\Admin;
    use One_Onboarding\Ajax\Ajax;
    use One_Onboarding\Api\Api;

    if ( ! class_exists( 'Plugin' ) ) {

    /**
    * Main Plugin Class
    *
    * @since 1.0.0
    */
    class Plugin {

    }
    }

    if any other plugin or theme defines a global Plugin class, your class won’t be defined.

    Thread Starter Kevin Pfeifer

    (@beardcat)

    I did what you said, still the same error.

    Here is the stacktrace again

    [21-Apr-2026 12:00:29 UTC] PHP Fatal error:  Uncaught Error: Class "One_Onboarding\Api\Api" not found in /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/includes/core/plugin.php:80
    Stack trace:
    #0 /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/includes/core/plugin.php(39): One_Onboarding\Core\Plugin->init_components()
    #1 /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/includes/core/plugin.php(50): One_Onboarding\Core\Plugin->__construct()
    #2 /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/loader.php(142): One_Onboarding\Core\Plugin::get_instance()
    #3 /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/loader.php(208): One_Onboarding\Loader->load_plugin()
    #4 /var/www/vhosts/mywebsite/httpdocs/wp-includes/class-wp-hook.php(341): One_Onboarding\Loader->load_onboarding()
    #5 /var/www/vhosts/mywebsite/httpdocs/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
    #6 /var/www/vhosts/mywebsite/httpdocs/wp-includes/plugin.php(522): WP_Hook->do_action()
    #7 /var/www/vhosts/mywebsite/httpdocs/wp-settings.php(742): do_action()
    #8 /var/www/vhosts/mywebsite/httpdocs/wp-config.php(137): require_once('...')
    #9 /var/www/vhosts/mywebsite/httpdocs/wp-load.php(50): require_once('...')
    #10 /var/www/vhosts/mywebsite/httpdocs/wp-blog-header.php(13): require_once('...')
    #11 /var/www/vhosts/mywebsite/httpdocs/index.php(17): require('...')
    #12 {main}
    thrown in /var/www/vhosts/mywebsite/httpdocs/wp-content/plugins/ultimate-addons-for-gutenberg/lib/one-onboarding/includes/core/plugin.php on line 80

    We are on WordPress 6.9.4 with PHP 8.4.20

    Astra Pro: version: 4.13.1, author: Brainstorm Force, Automatische Aktualisierungen deaktiviert

    Duplicate Page: version: 4.5.7, author: mndpsingh287, Automatische Aktualisierungen deaktiviert

    Elementor: version: 4.0.3, author: Elementor.com, Automatische Aktualisierungen deaktiviert

    Elementor Pro: version: 4.0.3, author: Elementor.com, Automatische Aktualisierungen deaktiviert

    Germanized for WooCommerce: version: 4.0.3, author: vendidero, Automatische Aktualisierungen deaktiviert

    Germanized for WooCommerce Pro: version: 4.3.3, author: vendidero, Automatische Aktualisierungen deaktiviert

    ManageWP - Worker: version: 4.9.33, author: GoDaddy, Automatische Aktualisierungen deaktiviert

    Post Types Order: version: 2.4.6, author: Nsp Code, Automatische Aktualisierungen deaktiviert

    Saferpay WooCommerce Gateway: version: 5.0.1, author: PITSOLUTIONS, Automatische Aktualisierungen deaktiviert

    Sentry for WordPress: version: 8.10.0, author: Alex Bouma, Automatische Aktualisierungen deaktiviert

    Spectra: version: 2.19.22, author: Brainstorm Force (latest version: 2.19.23), Automatische Aktualisierungen deaktiviert

    Ultimate Addons for Elementor Pro: version: 1.44.2, author: Brainstorm Force, Automatische Aktualisierungen deaktiviert

    WooCommerce: version: 10.7.0, author: Automattic, Automatische Aktualisierungen deaktiviert

    WooPayments: version: 10.7.1, author: WooCommerce, Automatische Aktualisierungen deaktiviert

    Yoast SEO: version: 27.4, author: Team Yoast, Automatische Aktualisierungen deaktiviert
    Thread Starter Kevin Pfeifer

    (@beardcat)

    To follow up on anyone who encounters this problem as well:

    Elementor Pro ALWAYS uses the domain, which is registered to the license. Therefore, elementor is NOT multi TLD setup compatible (like you can do with WPML or WordPress Multisite)

    I have to add, that this only is a problem if you add recommended HTTP XSS Headers like these where this kind of problem appears:

    strict-transport-security: max-age=15552000;
    x-xss-protection: 1; mode=block
    x-content-type-options: nosniff
    referrer-policy: same-origin
    x-robots-tag: none
    x-frame-options: SAMEORIGIN

    We had to remove those security recommended headers to get it to work again.

    Thread Starter Kevin Pfeifer

    (@beardcat)

    Thanks, we contacted Elementor Pro commercial support

    Thread Starter Kevin Pfeifer

    (@beardcat)

    We are on
    WordPress 6.8.3
    Elementor 3.33.2
    Elementor Pro 3.33.1
    WPML 4.8.6 
    PHP 8.2.18

    Thread Starter Kevin Pfeifer

    (@beardcat)

    That indeed fixes the problem. Weird, that a translation can break the website 😂

    Thread Starter Kevin Pfeifer

    (@beardcat)

    We use a custom-built theme but do not have any overwritten templates.

    PHP: 8.2.24
    WordPress: 6.8.3
    The Events Calendar: 6.15.12
    No Events Calendar Pro version

    Thread Starter Kevin Pfeifer

    (@beardcat)

    I have not looked into the CVE in detail since you as the plugin author should have gotten more details on what the exact problem is.

    I only post this, since my monitoring tool marks my websites as having a security issue due to this CVE.

    Thread Starter Kevin Pfeifer

    (@beardcat)

    Indeed re-uploading the current 4.4.8 fixed the issue. Guess my hosting had a weird moment. Thanks for the quick response.

    I don’t know but just download the 1.9.1 release and check the changelog.txt inside the plugin. Maybe you find something in there which gives you your answer.

    See https://wordpress.org/support/topic/paypal-checkout-item_total_mismatch/
    There is a bug in 1.9.0 which is fixed in 1.9.1

    But for “some reason” the Plugin DEV decided to wait till the fix is released.
    So either download the beta version from the linked thread or stay on 1.8.1 till that new release is published.

    Indeed that would be nice!

Viewing 15 replies - 1 through 15 (of 36 total)