bjf2000
Forum Replies Created
-
Version 4.7.3 (2023-02-02)
- Fixing PHP 8.1+ deprecated error notice (reported here)
- Making sure that the version query param is not added to the instantpage.min.js so that the modulepreload can work correctly
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read propertyAnd the log is staying empty despite doing ordinary work on the site, like creating a post and modifying one?
There are many changes in each rev of PHP despite the version numbers being close. I do recommend updating to 8.1.13 and then we can go from there.
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read propertyIf I figure that out, I’ll post back, but I haven’t yet. It’s something in the ordinary use of the site though: either creating or modifying content. Our people aren’t doing anything beyond that.
I would suggest adding the “Elementor Header & Footer Builder” plugin, since it could definitely be wrapped up in this given its apparent connection with class-astra-target-rules-fields.php.
If possible, you might also update to PHP 8.1.13, which is what we have.
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read propertyAFAIK, it’s simply having PHP 8.1.x.
It would be very helpful on your end if you could tell me whether or not you’re seeing the issue. If you’re not, and as I mentioned, it MAY require having Elementor.
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read propertyThoughts, comments?
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read propertyI didn’t say that it breaks the site, but I haven’t excluded that it actually causes no problems, either, since it’s impossible to test everything. Unlike the developer, I don’t even know what the purpose of the files in question are, so you’re in a much better position to answer the question of relevance.
Even if irrelevant, it’s better to fix a problem than having messages stack up like this in the log (and they definitely are stacking up) indefinitely.
Are you saying that you see the notices too, and is Elementor involved, as seems to be implied based on what I showed? If you’re not even using Elementor on your test site, then we know it’s not. I can’t test without Elementor being there.
Also, to clarify, I wouldn’t necessarily say that these even are deprecation notices in the first place, since the words “PHP Deprecated” are traditionally used for those.
Forum: Themes and Templates
In reply to: [Astra] PHP Warning: Attempt to read property@bsfherman That article, from the beginning of the year, was regarding 5.9 though. We’re at 6.1 now, and AFAIK it is onboard with PHP through 8.1.
But either way, what do you think is the meaning of the warnings? Normal PHP chatter or important?
Forum: Plugins
In reply to: [Jetpack VaultPress] Unsure of what happens after VaultPressSimply deactivating/removing VaultPress will not automatically trigger backups via the new Jetpack VaultPress system unless you purchase a new Jetpack VaultPress Backup plan or we make the switch for you from our system.
We’ve been proactively migrating users from the old VaultPress plugin to the enhanced Jetpack VaultPress Backup service, which allows you to access your site’s backups and activity log via WordPress.com or Jetpack.com. In those cases where it was technically okay to make the move for users, we’ve also communicated this to them.
I don’t think we received that communication though, and (see my last message) removing VaultPress has seemed to work, backups continue. We’ve been on a paid plan the whole time, so I guess we were migrated at some point and I missed the message.
Forum: Plugins
In reply to: [Jetpack VaultPress] Unsure of what happens after VaultPressA couple days later now and according the activity log on WordPress.com, backups continue, so I’ve now removed VaultPress entirely on top of having deactivated it.
I would recommend that JetPack bubble up some information in the main JetPack UI about the status of and need for the VaultPress plugin, because otherwise countless people are never going to have the slightest idea that it’s no longer doing anything and can be removed (if you have JetPack, obviously). I had no idea of that until I started looking into why the plugin hadn’t been updated in so long and then conducted the above experiment.
Nice finding amid the sea of Experiments defaulted to Active.
I wonder if it’s a problem to be corrected in Elementor or Wayfarer though (corrected so that others don’t have to find this obscure workaround).
These errors are beyond cool, but in case we’d rather not have them anymore, any realistic solution on the horizon?
Continues here too, though as many as 7 or 8 days can pass between instances sometimes (though there is no set interval, and they can happen frequently).
For us, it began about a month ago soon after installing Super Page Cache for Cloudflare plugin, which may or may not be coincidental. Due to how complicated it is to configure, I don’t really want to uninstall it to find out.
If you received that log, did anything jump out? It continues.
Oh, that’s interesting and really good to know, thanks. In that case, how you’re doing it is appropriate. We must still be updating most another way and it’s much faster.
I’ll send that along too, since we’re in the same boat.
It could be a coincidence, but this began not long after installing the Super Page Cache for Cloudflare plugin (no, I really, really don’t want to uninstall it to test that theory) in early March, especially since it seems to be working fine (as is Wordfence, best as I can tell).
We do not use the LiteSpeed caching plugin, but the server is LiteSpeed.
We’ve had Wordfence for a long time and haven’t made any recent changes to it.
It’s logged multiple times a day, but I have no idea what the pattern is.
I ran a check of our database in Cpanel: it passes.
Our __wfblocks7 is a mere 0.01MB. The database overall is a little under 400MB.
Site Health Status is fine in WordPress.
WordPress: 5.9.2
PHP: 7.4.28
MySQL Version: 10.3.34-MariaDB