WP 5.5 for the Magazine?

Project Conversations Magazine
#1

As some of you may be aware, the Magazine’s hosting is done courtesy of @jasonbrooks and his team in Red Hat’s Open Source Program Office, hosted via WPengine. Jason, do you know whether we should expect WP 5.5 to just roll out at some point, or should we arrange a time to try the upgrade, and roll back if there’s an issue? (I’m not sure when the last time was that we did a minor release upgrade i.e. 5.3 to 5.4, vs. just bugfixes like 5.4.1 to 5.4.2.)

–
Paul

#2

This reminds me that I’d intended to note the whining Chrome’s console has been doing lately when visiting the Magazine site, due to the lack of an explicit SameSite setting on its cross-site cookies:

A cookie associated with a cross-site resource at http://wordpress.com/ was set without the SameSite attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

A cookie associated with a cross-site resource at https://wordpress.com/ was set without the SameSite attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

A cookie associated with a cross-site resource at http://public-api.wordpress.com/ was set without the SameSite attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

Presumably an upgrade to the newest WP release would sort that out for free?

#3

I think there is a plan to migrate to 5.5 WP.

1 Like
#4
#5

Lol, thanks, I haven’t seen that movie in years.

#6

Sorry for the delay in replying, Paul, I missed this notification. WPEngine will automatically do the core update, they leave some time for things to settle down. We can trigger it to happen sooner manually, if that’s preferable.

Jason

#7

I’m fine with waiting! The hubbub about 5.5 and how it broke some plugins has me a little worried. I’m not sure how we go about testing to see if the site will be okay after upgrade, though.

#8

You may have noticed that the 5.5 upgrade went down about a week ago. Regarding plugins, WP Engine offers a service where they test and upgrade your plugins for you – we had one free seat of that service, and I applied it to the fedoramag instance. It seems like it’s been running smoothly?

#9

I’ve noticed zero problems, so as far as I can tell it went swimmingly. Thank you Jason!

#10

I updated one of the plugins yesterday and that went smoothly, no issues noticed. It was the “Featured images in RSS for Mailchimp and others” and is currently not activated. Should this be activated? I assume the update went smoothly since we are not currently using this plugin.

#11

I typically don’t change any activations. That ensures as steady a state as possible. Of course it’s possible to evaluate at any time whether to change the configuration like that.