Anomalien If you turn "Only allow WordPress login" on and off, forum registration will still be closed
This is intentional. Because first off it's complicated to "remember" the value of the setting before the change, I would have to store that in the background, and make sure it's still valid even if the extension gets disabled and re-enabled later, or some other change. And since the sign up setting can still be changed anytime by the admin, I would also need to decide what to do if it was manually changed in the meantime. And second even if I went the trouble to do all this, I still don't want to unexpectedly re-open registrations if the forum owner doesn't expect it, so I would have to add a whole UI to ask the admin whether they wish to re-enable sign up.
So to save all this work I decided to not implement sign up re-opening, leaving it for the admin to decide.
But I kept the auto-close because there's no reason to keep it open when enabling the WP-only sign up, and if the step was skipped it would allow users to circumvent the protection they think they just enabled.
Anomalien here's interesting solution for iframe height
I am familiar with that library. It was in fact part of the plugin in one of the early betas. It was also part of the flarum/embed extension but I think it's not included anymore looking at the source code.
But it doesn't work correctly with Flarum's discussion infinite scroll. If the iframe expands, it completely breaks the ability to load more pages. And if it somehow worked, then it would prevent reaching the footer of the WordPress site if a discussion has thousands of comments.
I am researching solutions to make the iframe more seamlessly integrate with WordPress. Unfortunately it seems like we have to choose between infinite scroll and auto height, and keeping Flarum's built-in infinite scroll is the least work and least risky solution for now.
I will probably add options for a paginated iframe view in the future, as well as maybe a "summary" view that only shows the top comments and the composer and forces you to open the Flarum page to browse through the full list.
NetConfig it's unfortunate that the Extiverse-Flarum.org migration happened right about at the same time as my WPI V2 release, as this causes a number of extra steps to be needed 😅 I haven't re-written my upgrade guide since those are really 2 different things, and if you have multiple Extiverse premium extension you luckily only need to update the Extiverse repository once.
