The plugin supports PHP 8.2, although 8.0 or 8.1 are recommended. (Plugin version 3.5.0, which is due out before year end will fully support PHP 8.2. The only issue with 8.2 is the PHP notice about dynamically generated object vars.)
From your question, it would appear that you’re conflating two things – redirect TO registration/login and redirect AFTER registration/login.
If you put a redirect in the shortcode, that is where you’ll send the user after the process (login or registration) is completed. Note that I do not recommend this unless necessary, although that recommendation is strictly based on UX/UI. Don’t redirect just because you can – do it if it will make better sense to the user. There’s nothing more annoying for a user trying to log in on a page, be redirected somewhere else and then have to find the original page they were trying to view.
You do not need to redirect TO the login or registration. You can simply set the plugin to show those forms in place of blocked content (although sometimes, if you’re using a builder plugin, it is recommended to redirect blocked content to the login page for layout reasons). But if you do choose to redirect blocked content, here’s how you can redirect it to the login page (and the login will include the link to registration if the user is not registered).
This plugin has performed really, really well for over 5 years on our site right up to the point where I updated the php to 8.1. It was a wrong move! Wiped us right out. To be sure wp-members plugins are not the only culprits involved. I got all plugins deactivated and have been working through the list to restore functionality. So far wp-members and about 5 other wp-members related plugins all seem to cause things to lock up. Interestingly, the mailChimp integration does not seem to have issues. I notice 3.5 is not yet on offer. Is it likely the update will cure whatever is not working?
