That’s a PHP 8 issue, and yes, it is addressed in the next release (3.4). I expect the beta of 3.4 to be released over the weekend or early next week, but the bleeding edge development version is available on github (https://github.com/rocketgeek/wp-members-dev).
(If you try the dev version or even wait for the beta or full production release, this is a major version upgrade, so backing up prior to updating will be recommended in case a rollback is necessary)
Hey Chad,
Thanks for getting back to me so quickly and clarifying everything! Will check out the dev version but I think I’ll wait until for full release before upgrading. Will definitely do a backup prior.
Cheers,
Cam
-
This reply was modified 4 years, 4 months ago by
camparry.
Semi-related, and since this was fresh in my mind I thought I would mention it…
Doing some final upgrade testing for the beta and the actual changes in the db for updating are negligible. The only specific change made for upgrading is that the value that holds post IDs marked as hidden is changed from a transient (a type of cached value) to a static WP option.
The only time that would be an issue would be if you updated, rolled back, then changed (adding or removing) hidden posts, then rolled forward again a second (or more) time. The hidden post value wouldn’t be updated in that event since the db version had already been updated on the first upgrade. But as soon as a new hidden post was created/updated/deleted, the value would be refreshed. (Again, that’s only in a roll forward, roll back, roll forward again situation where a hidden post/page is changed – I don’t see that being much of a likely issue)
So updating shouldn’t be too much of an issue in terms of the database changes.
(This will all be noted in the release notes when the beta is released)
