Continuous PHP Warnings coming from module.php File

Hello,

Thanks for reaching out! 

These warnings are related to our plugin indicating that an attempt is being made to access user-related data (in this case, the user password and email property) but fails because the values are not set or are referenced incorrectly.

The error occurs when the Elementor code expects user information but it isn’t present, such as when there is no logged-in user or incomplete data for the current user. Sometimes conflicts with other plugins or your theme can cause issues with how user data is passed, especially if they modify or interact with the way Elementor processes user sessions.

1. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
2. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
3. Ensure that both WordPress and Elementor are up to date, as updates often fix bugs like these.

If the issue persists after these steps, you might need to restore a backup from a point before the issue started or if you using Elementor.

Let me know how it goes, or if you need further assistance!

As with any plugin issue and support I’d say I wouldn’t always be so quick to blame another plugin or theme.

I’d be glad to give you access to my site if you want to look around and reproduce the issue. This site isn’t using many plugins and the theme and plugins that I am using are highly used.

I’ve added some extra measures to help me log the issue and find a way to replicate it when the warning shows again. I’ll keep you updated when I learn more. Thanks for the help.

My hosting company has helped me drill further into the problem. It seems to definitely be coming from the Elementor plugin. Most likely from this cron event?elementor/tracker/send_event

The error is also showing in Elementor > System Info > Logs here:

PHP: showing 1 of 1

PHP: 2024-09-17 16:25:03 [warning X 3][/home/customer/www/mywebsite.com/public_html/wp-content/plugins/elementor/core/common/modules/connect/module.php::246] Attempt to read property “email” on null [array ( ‘trace’ => ‘ #0: Elementor\Core\Logger\Manager -> shutdown() ‘, )]

Here is the code it’s triggering:

foreach ( $users_query->get_results() as $user ) {
$connect_common_data = get_user_option( Common_App::OPTION_CONNECT_COMMON_DATA_KEY, $user->ID );

if ( $connect_common_data ) {
$users [] = [
‘id’ => $user->ID,
’email’ => $connect_common_data[‘user’]->email,
‘roles’ => implode( ‘, ‘, $user->roles ),
];
}
}

Is this an issue with how Elementor is tracking data when the Usage Data Sharing is checked?

Hope this helps.

It looks like the error is tied to the elementor/tracker/send_event cron, which collects tracking data. Here are some alternative steps you can take:

1. Disable Tracking via Code:
   Since there’s no UI option to disable usage tracking, you can add the following line of code to your wp-config.php file. This will prevent Elementor from sending any data to their servers:

   define('ELEMENTOR_CONNECT_TRACK_USAGE', false);

This should stop the cron event that’s causing the warnings.

2. Check for User-Related Issues:
   The warning suggests that Elementor is trying to access data for a user that doesn’t exist or doesn’t have the necessary data associated with them. You might want to check your users in the WordPress dashboard and ensure there are no users with incomplete data (such as no email).
3. Clear or Reset Cron Jobs:
   Sometimes, cron jobs can get stuck or misconfigured. You can use a plugin like WP Crontrol to inspect and remove or reset the elementor/tracker/send_event cron event, which could resolve the issue.
4. Update Elementor:
   Ensure that Elementor is updated to the latest version, as these types of warnings can be tied to bugs that have already been fixed in newer releases.

Let me know if any of these steps help!

Best regards,

Due to inactivity this ticket has been closed.