Robert Angle

Which is perfectly normal. Maintaining security and stability in a forum is crucial, and a 24-month renewal policy helps ensure that. So, it encourages users to stay up to date with the latest upgrades and security enhancements, and thus creating a safer and more reliable environment for community members.
Also from a business perspective, it also makes sense for Invision Community to implement such a policy. Think  platform's sustainability, allowing them to continue providing valuable services and support for us. So, while it might seem strict, it's a necessary step to secure your community and ensure Invision Community's future success.

Surprise leaks from the video:
Change in location to Mark site read Easier access to Subscriptions Iconography for +Create and Report Not yet identified features related to Helpful Check out my in-depth commentary (with screenshots!) on Invisioneer.org, where I break down what clients can expect not just in the upcoming release but potentially as a larger theme on v5 (hint: start making suggestions about Subscriptions!):
https://www.invisioneer.org/forums/topic/217-deep-dive-a-very-brief-look-at-invision-community-5/

Not really a fix but workaround. The new member always receives an email regardless of which setting previously.

Support for self-hosted clients is provided right here in this forum. It's currently after hours. While someone at Invision might happen to read this tonight, they usually aren't actively monitoring until they open in the morning.
At least it's running on the front end. I don't think it's going to be easy to upgrade from 3.3 to the latest release. You're gonna have to jump through some hoops.

This is true on my well-established, long running board. I've spoke to a lot of members who visit and go straight to the Unread Content section of the Activity Feed, bypassing everything else.
 

In addition to Matt’s post, each of your members (where a new group permission allows) can also choose their own preference out of the views. So if you’d prefer to use the traditional table view for the forum index and the traditional column view for topics (even if the admin has assigned other layouts), that’s of course possible. We’re absolutely not forcing change, just offering more options than before 🙂 

Carole had a support ticket open for this on my site too. The two issues are related to the configuration on the WordPress side. The registration page Carole wanted to use wasn't properly registered as the registration page via `wp_registration_url()`. And unfortunately, the replacement login page isn't acting quite right. It's instantly redirecting requests back to the community instead of asking the end-user to sign in first.
@Robert Angle That's a good work around for the registration issue though!

BUG: If you have a forum where a Guest is allowed to post, then when the Guest submits his post the Auto-Welcome script will try to send an email to Welcome the Guest. The only problem here is that the Guest's don't provide email addresses, so the Email will returned as Failed: Missing recipient address.

So you going to have this file elsewhere on another site now?
I mean https://www.devfuse.com/forums/files/file/386-auto-welcome/  Not even updated version

This works perfectly. Thank you.
Yes, that is what I see too.

https://www.sosinvision.com.br/index.php?/file/100-promote-posts-to-articles/

I think this inordinate fear of Invision abandoning self-hosted clients is way overblown. This is probably due in part to truly evil companies like Quickbooks who literally forced the majority of their desktop users to the cloud. 
The difference is Intuit/Quickbooks have proven themselves to be greedy bastards. The Invision staff on the other hand have proven themselves to be reasonable and accommodating.
 

I would certainly mention that within the ticket, in case this is indeed related.

Some clarification here. We can certainly understand why people would feel like that, but that is incorrect.  Indeed we have actually made changes to our classic self-hosted licensing specifically to ensure it remains viable. 

Yes, I read their reply at their other topic. In that case the OP is in very good hands. The Ips staff will sort this out for them. 

It loads right up for me 🙂

I could load this last night. But I cannot this morning
This link works for me. You seem to have a lot of members posting just fine.
I was also able to access your AdminCP's login screen.

I would like to ask why the structure of the Invision Marketplace couldn't still exist here, but instead of financial transactions and downloads being handled by Invision, just remove the commerce aspect of it and just let it be a "Downloads" directory with hyperlinks back to the author's site. The author could still update the application or theme's description, changelog, and compatible versions here at Invision, and the client would still be able to shop around here where they feel comfortable, and if they find something in your [former] Marketplace, they click through to the authors personal site.
Downloads allows for URL submissions as it is. Why not retain that directory of applications here? What Joel is proposing to do, you could set up in a short amount of time and then it would be almost on autopilot. An existing Invision directory would only increase exposure to the applications that 3rd party devs have created and sell.

Currently they are...
Everyone can see this album Only the owner can see this album I want to choose who can see this album It would be better if it were like this...
Everyone on the web can see this album Only Registered Members can see this album Only the owner can see this album I want to choose who can see this album The reasoning is that some members don't mind their sharing their photos with fellow community members, but they don't want it exposed to innumerable random guests perusing the site.

I would like to ask why the structure of the Invision Marketplace couldn't still exist here, but instead of financial transactions and downloads being handled by Invision, just remove the commerce aspect of it and just let it be a "Downloads" directory with hyperlinks back to the author's site. The author could still update the application or theme's description, changelog, and compatible versions here at Invision, and the client would still be able to shop around here where they feel comfortable, and if they find something in your [former] Marketplace, they click through to the authors personal site.
Downloads allows for URL submissions as it is. Why not retain that directory of applications here? What Joel is proposing to do, you could set up in a short amount of time and then it would be almost on autopilot. An existing Invision directory would only increase exposure to the applications that 3rd party devs have created and sell.

This means no more sexy lonely women using the Contact Us form, lol

Well I have some mixed emotions.
On the one hand, this is fantastic for my established community. I currently have everything except for Commerce and my 6 month renewals are $105, or $210 per year. I will be converting this license to gain the extra functionality and lower my annual costs.
On the other hand, I am about to start a new community, and was was heading over here to buy JUST the forum and maybe one other app, then was shocked that it's all bundled together for $500 now. I was willing to invest a little bit on an idea that may or may not succeed, but now I'm back to wondering if I should start with a freeware script at first, and convert later. I would rather not do that because I am very fond of and very familiar with the Invision Suite. And if the new community should fail, I would use the license to try again with another one.
It would be nice if existing users got a discount or coupon code for subsequent licenses.

I have moved this to a ticket so we can assist you.

Sounds like it went well.
I just did 2 migrations. One was small, and it was easy enough to do a full site backup in Cpanel and Restore it in DirectAdmin. The other forum was huge and didn't have enough room for a backup, so we had to copy it over in pieces. This was very slow and we had a lot of downtime but it worked.