Forum Replies Created

Viewing 15 replies - 1 through 15 (of 85 total)
  • Thread Starter chargeup

    (@chargeup)

    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.

    Thread Starter chargeup

    (@chargeup)

    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.

    Thread Starter chargeup

    (@chargeup)

    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.

    Thread Starter chargeup

    (@chargeup)

    All good now. After some more troubleshooting there was an issue on the Stripe side of things.

    Thank you so much for the quick response.

    Thread Starter chargeup

    (@chargeup)

    Thanks. I just submitted a ticket over there.

    I am also using WPForms and have had a pretty large increase in spam submissions the past few days. I barely ever got any spam before. One would sneak in every few months. Incredible plugin.

    Did you roll out the update to help with the WPForms issue or are you still in the testing phase?

    Thread Starter chargeup

    (@chargeup)

    Can you double check with your team to see if this is a possibility?

    I have seen a few other times (for example with a Paypal security issue on another plugin) they just added the patch only to that section of code in the old version and renamed the version by 1 number. They didn’t force an entire plugin update.

    Just making sure it’s not a further security issue that I need to roll back a backup on then update your plugin fully to 7.6.1.

    Thread Starter chargeup

    (@chargeup)

    I have 3 sites on 7.5.0. They were all updated to 7.5.1 not to version 7.6.1.

    Forum: Reviews
    In reply to: [Astra] Decent Theme
    Thread Starter chargeup

    (@chargeup)

    I’m not sure which customer of yours you are actually referencing here.

    1. For starters I DIDN”T put in a support ticket for the issue I’m experiencing with Ultimate Addons at the time. As stated in my review I’ve basically thrown in the towel on most support tickets unless it’s absolutely necessary. And while some errors are harmless, some others aren’t. As with any developers and site owners, no one likes to open up developer tools and see a bunch of red errors. It looks bad for developers and it looks bad for less skilled site creators if their clients can also see these errors. I wouldn’t be so casual throwing out comments like they are harmless. It’s also dishonest to openly say you are helping me with a support ticket I placed for Ultimate Addons when I didn’t submit a ticket.
    2. I do have tickets that are still open from much earlier in the year.
    3. Not sure what console errors you are referencing, but I have also had that experience with your team myself. If by “finding a solution” you mean simply clicking a setting that actually does work or changing a setting on your theme. From my current experience and there are still multiple tickets open so this could change but the settings that don’t work still don’t work and those issues haven’t been resolved yet.

    You may be referencing a different customer of yours in your response. Either way, you should make sure you take accountability and iron out these issues.

    I received the same automatic updates, although mine didn’t include a download link. I’d love an explanation as well. Unlike the last forced update over the summer I don’t see any mention online of security issues or anything in the changelog.

    The automatic update also didn’t update to the newest version on all of my sites which is 7.6.1. Some went from 7.5.0 to 7.5.1 for example.

    Thanks in advance.

    Thread Starter chargeup

    (@chargeup)

    I already updated to the latest version and I’m still having that folder fill up with malware. I’ve had to clean up that folder a few times. Is it possible that you may have missed another spot in the plugin that is vulnerable?

    I’ll keep an eye on it and let you know when it happens again. Everything on the site is up-to-date.

    Thread Starter chargeup

    (@chargeup)

    This temporarily fixes the issue. However, I’m using default Chrome settings (as I’m sure most other users are). This wasn’t an issue until one of the latest Chrome updates I’m assuming which is now conflicting with your plugin.

    Speaking out loud. Don’t you think it is a better option to fix whatever is causing the issue within your plugin as opposed to assuming a user knows how to dig through Chrome settings to turn off a setting that is default within Chrome?

    Seems that there is an issue with how the plugin is now interacting within Chrome.

    Thread Starter chargeup

    (@chargeup)

    I just reposted the original issue above for you to look into. The other issue with Astra Pro is separate and I didn’t think it needed to be mentioned here in the plugin thread.

    The Astra Pro thing a separate issue, but it also deals with that “Cannot modify header information – headers already sent by (output started…” error. That issue is obviously pulling from a file within that other plugin.

    I just reshared the Custom Fonts error in the prior message to make sure you saw it and are aware of it.

    Don’t take this the wrong way but Brainstorm Support is very frustrating and unfortunately I don’t have the energy or patience to work on another support issue with you. It takes weeks and weeks of deflecting the issue on another plugin or theme (even though I will show proof with everything deactivated that it’s coming from your product), telling me nothing is showing on your end and you are unable to replicate, then finally after weeks admitting there actually is an issue. At that point it could take months for a fix to actually be rolled out (if ever).

    I have 4 open tickets with you with and when I ask for updates I get “Our developers are working on the issue. Thanks for you patience.” This typically goes on for weeks at the minimum, but usually much longer.

    I do see another post for this exact same issue. Hopefully they have given you enough information to solve this

    • This reply was modified 1 year, 2 months ago by chargeup.
    Thread Starter chargeup

    (@chargeup)

    Here is the original thread starter with the error. I’m not sure what the issue is. This is for BSF to figure out. This is error is being shown on everything single page/post when I open a page on the admin side of the website.

    ——————————————————————

    I’m getting the following error when I open a page or post after the latest update. Any thoughts?

    Cannot modify header information – headers already sent by (output started at /home/customer/www/domain.com/public_html/wp-content/plugins/custom-fonts/classes/class-bsf-custom-fonts-render.php:292) in /home/customer/www/domain.com/public_html/wp-admin/admin-header.php on line 9

    Thread Starter chargeup

    (@chargeup)

    I’ve had a ticket out for this issue since May. They are aware of the problem, but have yet to release a fix.

    Since the new error has to do with Custom Fonts that’s why I’ve posted a new ticket here

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