Chris Anderson

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

Not just the current developers but how you can better foster the next cadre of programmers who might one day be great candidates to join your firm one day. 
Provide a crippled version of the suite to develop on and allow for one or two people to test the apps being developed but not be able to be used to run an actual site off of. 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers.  Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with.  Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.  
 

I notice that "Help and support" topics are open to guests and I find that a bit strange. On our own sites some of us have "About this community" forums, where people ask about problems with our sites, and then (now) we check the Help and support forum, or ask a question about it. It gets kind of awkward to discuss stuff like that open here then. I'm not a softwareguru whatsoever (even if som of my users might think I am) - and my own stupidity is displayed in public when it is 100% open for google and guests.
This topic here are not open for guests, and I see no good reason for having the Help forum open for guests either..
So - would it not be better to have all this support and help hidden from guests?

Not just the current developers but how you can better foster the next cadre of programmers who might one day be great candidates to join your firm one day. 
Provide a crippled version of the suite to develop on and allow for one or two people to test the apps being developed but not be able to be used to run an actual site off of. 

There are a finite amount of technical support staff and hours in the day.  If a community member happens to drop by the forums and sees a particular topic posting and provides some form of value-add then that will potentially lessen the burden on the support staff.  This might mean a site that is currently down and isn't paying for expedited support gets their site up and running that much sooner.
It's kind of like "paying it forward"...  A few moments of your time here and there just might pay dividends later. 

There are a finite amount of technical support staff and hours in the day.  If a community member happens to drop by the forums and sees a particular topic posting and provides some form of value-add then that will potentially lessen the burden on the support staff.  This might mean a site that is currently down and isn't paying for expedited support gets their site up and running that much sooner.
It's kind of like "paying it forward"...  A few moments of your time here and there just might pay dividends later. 

Generally speaking, after so many years I feel I can say that invision is a company that thinks well about the choices it makes. But this time, as others have already written, I am very concerned about the collapse of the Marketplace. It is quite clear to me that the new pricing policy and the type of support offered for a fee is aimed exclusively at the business sector. This means that hundreds of hobby forums will be looking for alternative software solutions and this also means less appeal for me and many other developers to develop app and plugins.
Although I don't know the reasons for a series of "blows" thrown at the customer at the same time, I find some of the choices made by Invision risky.
Even if I accept the price increase, which is something I can live with, I think it was a mistake to remove the possibility to pay every 6 months. This has disoriented customers even more, even giving a perception of a heavier increase than it really is.
Furthermore, it must be acknowledged that one of invision's greatest assets has always been its ticket support. 
In short, I'm a bit worried, I'm sure I'll be one of the last to abandon ship... I've been here for 20 years... but I confess that I've been looking for alternatives for the first time in many years.
The problem is not the price, I am more concerned about the choice to let the hobby communities go.
Unfortunately I don't think the the fresh new green buttons can turn this into good news.

Let's see, I understand that even the pandemic period is not the best but let's try to give confidence to Invision as Jordan asks. Instead I would ask invision to review at least the possibility of returning to payment every six months, not for me, but I think it would help many.

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year. 
 
 

Bottom line: You didn't communicate these changes effectively at all, and you didn't learn from the last time(s) you didn't communicate effectively.
What will the next surprise be that you don't communicate effectively to your customers be?

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year. 
 
 

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year. 
 
 

I knew the prices would rise with this site relaunch, but I expected more a generous correction for inflation for new orders (not renewals). But the changes are far from slight. And for people like me who have many licenses, it actually threatens my entire business, because the price change is multiplied by the number of licenses. And the new terms make it all even worse. For my oldest license, I had an upcoming renewal of $85 as the last payment in this financial year. Now that jumped to $310—well over 300%! Yes, it’s for 12 months, but I still need to pay it NOW without having earned this money through the site or even planned for it. And even if would manage with this one site, I certainly can’t manage it for 5 self-hosted licenses and their upcoming renewals. 
And it didn’t had to be this way. There is the established system of grandfathering existing prices while only charging more for new customers for example. Or it could be a slow transition that is announced a year or two in advance, so we could have prepared for it someone. Dropping these drastic price and terms changes on us like a bomb, effective and possibly charged immediately, was a bad move. 
 
 

I've done it - removed my payment method and exploring other options. No one likes price rises, but when people are still recovering from the pandemic this is like a sledgehammer blow.  It's also going to affect devs who supply much needed apps in the marketplace; if people start leaving then their revenue is going to slip and then they may leave too.  It's a slippery slope IPS has ventured into and may be something to regret later. I just bought another license this year for another project, now that's on the bonfire until I find another solution.  Talk about being hit between the eyes!

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year. 
 
 

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year. 
 
 

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time.  This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year.