Pleeb

New version is pending approval. It will add a setting:

In your case, you may want to disable it.

I will release a new version with a setting so the admin will be able to choose how want it to work. 👍

We have a native dark theme for the ACP, let’s give a dark theme for the front end! Then I can happily 100% use the default invision community theme for my community, while still letting my users choose between dark and light.

We have a native dark theme for the ACP, let’s give a dark theme for the front end! Then I can happily 100% use the default invision community theme for my community, while still letting my users choose between dark and light.

Including night mode, if that wasn't obvious!

Night mode button.

Just an update.. The credentials are working and we're investigating this now:)
 

I updated the client area with the information.

When anyone tries to embed videos in my forum by typing out the video, they're getting the error: "The link could not be embedded because www.youtube.com does not allow embedding of that video."  Happens with youtube and youtu.be.  Strangely, if I add the "embed video" button to the toolbar, that actually works (see below).
I have the latest version of Invision Community with the default theme (I have one css modification), and I generally use cloudflare.  I have 14 plugins and applications that are up to date.
I can embed here on this forum, so I'm not sure what else I'm doing wrong or what's failing where.
For troubleshooting up to this point:
I cleared caches I disabled cloudflare I disabled all of the plugins and applications Switched to newly-created fully vanilla theme Updated all software and OS on the server itself  Updated from php7.3 to php7.4. This started happening about last month, with no changes on our end so I'm not sure where it's faltering.  Does anyone else have issues automatically embedding videos on their forums?
Please see screenshots with https://www.youtube.com/watch?v=BFNekjEgvuk:


 
I can add an "embed youtube video" button (notice it exists in the following screenshots) and that works, so the video itself can be embedded:


 
And finally, embedding does work here:
 

No errors, just a warning about cross-origin read blocking:

Except when I do that on this forum it happens too:

I was able to solve this using member groups, group promotions, and this plugin:
I was already using it to prevent spammers from signing up with 0 posts then editing their profile fields with URLs; what you can do, is create a special member group that promotes a member to that group on say, 500 posts.  Then simply enable this field for that membergroup to edit.

I bought this plugin and mentioned it in my last post on this very thread, when pointing out how Invision Community needs to better listen to requested common-sense features along with my grievances of the marketplace.  Fosters' update has been rejected once already, and it takes weeks for a plugin to come out of review.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

The quick fix here for all is for IPS to halt the switch to annual renewals up front. I get that some people might like to switch to annual renewal but at least give us a choice, please.
Looking at my Client Centre earlier, I'm shocked.
Next month October 1st, I have about 2 weeks to find $155 then another $30.

 

 
Then November, I now have to find another $185.

 
Then the final kick in the nuts, a week before Christmas, I have to find $310.
 

 
$680 in the next 3 months without any notice. Great, thanks IPS.

Hello,
I just got up, read this email and I am absolutely furious.
I am told that I will get a "small" increase of 90$ every 6 months, that is 180$ per year, which is more than a 30% increase, but it is a small increase! 
Also, no more support by ticket, but by the forum, a good way to tell your customers to take care of themselves, but on the other hand, they can pay to open a ticket.
But frankly, are you kidding us? Is this a joke? And you justify this with "We feel that Invision Community offers exceptional value for money with its rich functionality and power at your fingertips." ? No, we use Ipboard out of habit, nowadays there are other solutions.
Moreover, I'm still waiting for a proper integration of Webp with conversation, an update of elasticsearch, a real mobile application, a real mobile optimization (IPB is completely lacking in this area), an evolution of the api, and that for years! 
Oh and I forgot, the ponpon, features that are not present on our self-hosted versions but on your versions that we don't want!
We are users and contributors of mediawiki and they have a real update tracker, yet it is an open-source solution (like Discourse, Phpbb, SMF, etc...) and we almost get a faster response from them than by opening a "ticket".
Frankly, what advantage do you think you have today? I tell you, none, we pay a licence (and other users too I think) for the convenience, but we will clearly review our strategy, especially as we are informed at the last moment.
 
 

Hello,
I haven't dared go look at my Client Centre yet! The few groats I've earned from the Marketplace are all I've had as income since 2017 since being made redundant due to UK austerity cuts. So it's a scary prospect.
Honestly... Nobody likes change. It's rarely good. Someone always gets the pointy end of the stick. It's usually me or the little guy, but rarely the enterprise corporations who can afford the change.
However I appreciate that prices haven't increased for a decade, and a reasonable increase would be understandable, we know this, it's overdue but it needs to be said these significant changes are sadly once again being poorly implemented and probably compounded by an almost total lack of notice, no dialogue, a lack of communication, causing major headaches and increasing uncertainty.
Yes, of course you don't have to consult or engage, but in my experience, just like change between employers, managers and employees, if you do, you'll often find it makes change a lot more smooth and easier to swallow. Both company and customer may come to appreciate things they were unaware of, and/or offer suggestions or alternatives.
A few points of feedback for what they may be worth...
Re the price changes...
I think there has been an obvious failure to give fair and reasonable notice of the financial changes, in particular to those needing to renew in the real short term (meaning days, weeks) but especially to everyone who needs to renew in the next few months. Hopefully Lindy and Charles will realise this oversight, take ownership of the situation from a customer service perspective and immediately ensure no financial impacting changes until the next 6 month renewal period for all non-enterprise clients has expired. After all IPS says it's all about supporting communities. So do the right thing.  This is a decision that will strike at the heart of IPS communities that were already struggling even before COVID impacted, and those under significant financial pressure. For many, having to find more than double the funds up front for a year in advance, is not an easy sell, but for many is not easy to accommodate either especially with short notice. The lack of a small discount for multiple license holders is disappointing. Don't compound things, please space them out and easier to swallow!  
Re the Support changes:
Removing Support Ticket facility is a seriously poor and frankly ridiculous decision. Increasing the license costs at the same time is pretty terrible and almost ridiculous. IPS Support should make better use of the Support Forums, absolutely, but in addition to Support Tickets, not instead of them. Many I suspect are fed up already with being to create a ticket for most Support Topics they create reporting problems. You tell us it's because you need site access to investigate or fix things, so how will this help? I don't want to name my website communities that be having problems in a public forum, my clients wouldn't appreciate it but also I like many are reluctant to post links and references to specific communities mainly because those topics appear on search results, it's unprofessional and gives a poor impression aside from anything else. Others may not appreciate doing so because of privacy or sensitivity considerations. If you don't use your own ticket system, I can see a time coming when you drop it entirely from Commerce. Maybe even move it to a separate app or module for Commerce. "Our enterprise clients use dedicated solutions like Zendesk, so we're dropping it" sort of thing.

This plugin was also the last 4.5 holdout in my community too; I understand there's been a lot of design changes so I'm more interested in a working plugin with no bugs than a rushed plugin.  Just renewed my license and looking forward to the update so I can start using it again.