Sporadic warnings on top of Control Panel

Resolved aclassifier
(@aclassifier)

1 year, 2 months ago

Some times, but not always (like not _now_) I get these messages in the Control Panel. I have extracted these by inspecting the page source in Safari 17.6 on MacOS 12.7.6, since the WordPress window will not give me the leftmost part. A screen clip of the page is at https://www.teigfam.net/div/jetpack_warnings_17jan2025_teig.jpg. I have WordPress 6.7.1 and Jetpack (free) 14.2.1.

Warning: Undefined property: stdClass::$core in /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-content/plugins/jetpack-boost/jetpack_vendor/automattic/jetpack-protect-status/src/class-protect-status.php on line 261

Warning: Undefined property: stdClass::$version in /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-content/plugins/jetpack-boost/jetpack_vendor/automattic/jetpack-protect-status/src/class-protect-status.php on line 276

Warning: Cannot modify header information – headers already sent by (output started at /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-content/plugins/jetpack-boost/jetpack_vendor/automattic/jetpack-protect-status/src/class-protect-status.php:261) in /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-admin/includes/misc.php on line 1438

Warning: Cannot modify header information – headers already sent by (output started at /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-content/plugins/jetpack-boost/jetpack_vendor/automattic/jetpack-protect-status/src/class-protect-status.php:261) in /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-includes/functions.php on line 7137

Warning: Cannot modify header information – headers already sent by (output started at /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-content/plugins/jetpack-boost/jetpack_vendor/automattic/jetpack-protect-status/src/class-protect-status.php:261) in /customers/f/c/9/teigfam.net/httpd.www/oyvind/home/wp-admin/admin-header.php on line 9

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

Viewing 15 replies - 16 through 30 (of 31 total)

← 1 2 3 →

Thread Starter aclassifier
(@aclassifier)

1 year, 2 months ago

With deactivated WP-Optimize and UpdraftPlus I still get the warnings. So I have marked that thread [1] as resolved.

I don’t have the Redis Object Cache plugin.

But how do I downgrade? I use free Jetpack. I couldn’t find any menu for it..

[1] https://ww.wp.xz.cn/support/topic/sporadic-warnings-on-top-of-control-panel-2/#new-topic-0
Phi Phan
(@mr2p)

1 year, 2 months ago
I’m still encountering the error even after rolling back to version 14.1.. It seems to work at first but the error reappears after about a day.

The error is triggered at line 261 in the class-protect-status.php file:
```
// Ensure the report data has the core property.
if ( ! $report_data->core || ! $report_data->core->version ) {
  $report_data->core = new \stdClass();
}
```
I make a quick hotfix by modifying the code as follows.
```
// Ensure the report data has the core property.
if ( ! isset( $report_data->core ) || ! $report_data->core->version ) {
  $report_data->core = new \stdClass();
}
```
Phi.
Phi Phan
(@mr2p)

1 year, 2 months ago

I was wrong again. No way to get rid of this error. It keeps comming back after some time.

Thread Starter aclassifier
(@aclassifier)

1 year, 2 months ago

But, @mr2p you try very sincerely! Thanks!

For me, some times when I hit a page to edit after a search filtered on some month, I press on an edit entry in the list, and I get ONLY those messages. Then I do it again and it works fine without these warnings.

Bruce (a11n)
(@bruceallen)

Happiness Engineer

1 year, 2 months ago

Hi @aclassifier

One thing I noticed is that although your domain has a valid SSL certificate, it is still possible to access your site via HTTP. Your visitors and search engines can use either HTTP or HTTPS to access your site.

This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with Jetpack, as our system does not know whether it should connect to your site via one or the other address.

To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.

If your host is unable to help with that, you can follow the instructions here to do so:

https://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/

Once that’s done, try to reconnect your site to Jetpack once again.

Thread Starter aclassifier
(@aclassifier)

1 year, 2 months ago

Thank you @bruceallen. But I have done this years ago (2019), and I thought it worked. I also have the plug-in “Really Simple Security”. I also have a .htaccess file at my top level https://www.teigfam.net.

I have today included some tests at https://www.teigfam.net/oyvind/home/background/. Except for some real old stuff at Blogspot (even if also those are all set up to redirect), both one.com (my host) and WordPress in those cases redirect.

But I have kept my fingers as much as possible away from this, as I think I recall from 2019, that it was easy to lose access during the process. And this is not my speciality.

Could you please elaborate?

Bruce (a11n)
(@bruceallen)

Happiness Engineer

1 year, 2 months ago

Hi @aclassifier

So what this means is that your site loads on both of these addresses:

https://www.teigfam.net/oyvind/home/

http://www.teigfam.net/oyvind/home/

This is a security issue for your site, but may not be the direct cause of the errors you reported. If you temporarily deactivate Jetpack Boost do you still get the errors?
Thread Starter aclassifier
(@aclassifier)

1 year, 2 months ago
Right! I have made two overviews here. One page with urls landing from http refs on different pages from outside of my WordPress domain, see https://www.teigfam.net/oyvind/tst/http_and_https.html. The other takes http “textual” in a WordPress page and does the same, see https://www.teigfam.net/oyvind/home/technology/264-http-and-https/. Here is an attempt at a summary. My explanation is rather void!
- It looks like WordPress changes every http “textual” url that points to inside the WordPress domain /home/.. to saved (as seen by viewing page source) as https only, so that it effectively masks possible lack of a redirect
- From the outside http urls to outside of /home redirects to https
- From the outside http urls to inside goes to http unsafe in Safari but safe in Chrome
Back to the original thread. Free jetpack is running here. Plus, I have not seen that problem for a couple of days.
- This reply was modified 1 year, 2 months ago by aclassifier. Reason: typo
- This reply was modified 1 year, 2 months ago by aclassifier. Reason: more info
- This reply was modified 1 year, 2 months ago by aclassifier. Reason: typo
- This reply was modified 1 year, 2 months ago by aclassifier. Reason: typo
Bruce (a11n)
(@bruceallen)

Happiness Engineer

1 year, 1 month ago
Hi @aclassifier,

Good news – we’ve identified the root cause of these warnings. They’re related to how Jetpack Protect Status handles certain API responses. This has been fixed in Jetpack 14.3.

To resolve the warnings:
1. Update to Jetpack 14.3 from your WordPress dashboard
2. Clear your site’s cache after updating
If you still see the warnings after updating, please let us know.

Regarding the HTTP/HTTPS access: While both protocols currently work on your site, we recommend enforcing HTTPS for better security. However, this is separate from the warning messages you’re seeing.
Thread Starter aclassifier
(@aclassifier)

1 year, 1 month ago
Well done! (Yes I assumed that the warnings had nothing to do with the http/https matter). I write in my last comment that “Plus, I have not seen that problem for a couple of days”. This was with 14.3 installed. I have now also cleared the cache. No warnings!

By the way, on the Jetpack Control panel, bottom of page, the “Version 14.3” points to Jetpack in general. I would have expected it to go to to the version history’s corresponding version.

I assume that you may reply and mark this as resolved whenever you want to. I mean, since I cannot prove absense from error as being a fix, you are at the root cause and can do this better than me.

This has been a good experience. Thanks!
- This reply was modified 1 year, 1 month ago by aclassifier. Reason: clarification
Plugin Support Animesh Gaurav (a11n)
(@bizanimesh)

1 year, 1 month ago

Hey @aclassifier – Glad to hear that the issue has been fixed now!

By the way, on the Jetpack Control panel, bottom of page, the “Version 14.3” points to Jetpack in general. I would have expected it to go to to the version history’s corresponding version.

Could you let us know exactly where you see that? If you’d like, you can also share a screenshot to help us identify the location.

Looking forward to your reply!

Thread Starter aclassifier
(@aclassifier)

1 year, 1 month ago

Above is to show that I only get “Insert from URL” when I try to add an image. Not from local file as the screenshot seems to indicate.

But here is what you asked for:

Plugin Support Animesh Gaurav (a11n)
(@bizanimesh)

1 year, 1 month ago

Above is to show that I only get “Insert from URL” when I try to add an image. Not from local file as the screenshot seems to indicate.

Hey @aclassifier – yes, on the forum, you’ll need to upload the image elsewhere first and then add it here using a link. On forum, direct uploading of images is currently not supported.

I reviewed your Jetpack Dashboard screenshot and looked at the Version number text in the bottom right corner, but I didn’t find any link attached to it. In your previous response, you mentioned:

“Version 14.3” points to Jetpack in general.

I initially assumed it would redirect to the Jetpack.com site. Could you confirm if you meant that you’d prefer a link to our Jetpack changelog on that version number instead of just displaying the version number?
Thread Starter aclassifier
(@aclassifier)

1 year, 1 month ago
https://jetpack.com/redirect/?source=jetpack&site=104683332
ends up at https://jetpack.com/?site=104683332

Yes, I would like it to end at the changelog 🙂
- This reply was modified 1 year, 1 month ago by aclassifier. Reason: additional info
Plugin Support Animesh Gaurav (a11n)
(@bizanimesh)

1 year, 1 month ago

Hey @aclassifier – thanks for highlighting it in the screenshot. I missed noticing it in your previous screenshot. However, for some reason, I don’t see the version number of Jetpack at the area you highlighted in the last screenshot. Here is the screenshot from my site. But let me check this with my team, and we will get back to you after that.