Kevin Pfeifer
Forum Replies Created
-
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.
To explain what happens in
/wp-content/themes/theme/inc/custom-fields.php(18): requirewe 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
));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 😜
- This reply was modified 2 weeks, 4 days ago by Kevin Pfeifer.
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
Pluginclass, your class won’t be defined.- This reply was modified 2 weeks, 6 days ago by Kevin Pfeifer.
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 80We 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 deaktiviertTo 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: SAMEORIGINWe had to remove those security recommended headers to get it to work again.
Thanks, we contacted Elementor Pro commercial support
- This reply was modified 5 months, 1 week ago by Kevin Pfeifer.
We are on
WordPress 6.8.3
Elementor 3.33.2
Elementor Pro 3.33.1
WPML 4.8.6
PHP 8.2.18Forum: Plugins
In reply to: [The Events Calendar] 4 arguments are required, 3 givenThat indeed fixes the problem. Weird, that a translation can break the website 😂
Forum: Plugins
In reply to: [The Events Calendar] 4 arguments are required, 3 givenWe 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 versionForum: Plugins
In reply to: [Pinpoint Booking System - Version 2] Security IssueI 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.
Forum: Plugins
In reply to: [Simple Membership] Broken website after 4.4.8 updateIndeed re-uploading the current 4.4.8 fixed the issue. Guess my hosting had a weird moment. Thanks for the quick response.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Could not retrieve order errorI 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.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Could not retrieve order errorSee https://wordpress.org/support/topic/paypal-checkout-item_total_mismatch/
There is a bug in 1.9.0 which is fixed in 1.9.1But 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.Forum: Plugins
In reply to: [ManageWP Worker] 4.9.8 where is the changelog ?Indeed that would be nice!