TDBF

Okay, I must be ignorant in this particular subject then, so I'll try to educate myself by asking a question. What exactly about your hosting costs more if our websites have more traffic?  I went and viewed 3 of the most popular website hosts on the market and I don't see anything about traffic/impression limits. Am I missing something?
Sorry, the clarification wasn't to insinuate that it was expensive, I was just pointing out that in reality for most of those upset in these comments about the new renewal schedule that it would actually cost them $9 more per month in actuality. 

Woke up today to find out that we have a 48% rise in the renewal price and no email support, and that is the final straw for us. So, instead of $70 every six months, we will be paying $220 yearly and that starts next January. Sorry, not on guys.
With all the negative changes to the marketplace recently, and now this, means I will be moving away from IPB to one of your competitors instead.

You can make me reconsider, in fact, it would be quite easy for you to do so, just reduce the price increase to a 'reasonable' amount and still let me pay 6 monthly.
If you had increased your prices by 5-10%, then I would have grumbled a little, moved on, and would still be a loyal IPS customer. But this is a 48% price rise and you're removing Email support to boot. Sorry, that is a game changer for me, especially with all the other price rises I have from my hosting company and WHM/Cpanel recently.
So with that $220 saved, I can put that towards Xenforo, add another $50 and get access to Downloads and Gallery at the same time, and still pay less for my yearly subscription going forward.  Sure my users will probably miss some features, but they will get used to them eventually.

As a long time user of approaching 20 years who has been a customer since the Ikonboard days and has a first recorded invoice here in 2005 for "Purchase: Invision Power Board Perpetual License".
For what it is worth, here is my feedback on the e-mail I received about the price hike and reduction in support levels.
Six years ago you contacted me as a "lifetime" member to tell me that the lifetime agreement I signed up for, which helped set the the financial foundation of these forums, was to be replaced with an annual fee. It was nice to get a little credit on account by way of apology, however, I bought a lifetime licence and it should have been for lifetime. Offering a lifetime licence is a marketing incentive, and not something that should be reneged on further down the line once a company has reaped the benefits of the marketing drive. Telling customers its one payment for lifetime access, then changing the goal posts to an annual fee is not the type of thing that reflects well.  
Onto the new e-mail....
Forums: was $50, now $80 (increase of $2.50/month) The marketing team really earned their wage this campaign as $2.50 doesn't sound like much, however this represents a 60% price hike from $50 to $80.
A 60% price hike needs to be backed up with some serious upsides.... however...
For most customers, support is simply “how do I do this?” and these questions tend to be quite similar. Rarely, support questions are “this went wrong” Not my experience. My support experience is basically the same every year - my forums go offline with errors every time I do an upgrade. It fills me with dread every year or so, and true enough I need to submit a ticket to try and get the forums back online. To think that that base line support for a quick turnaround on outages is either now reliant on an additional payment for a support plan, or posting in publicly accessible forums is not a sustainable proposition for me.
Creating a strong support community backed by our support technicians will result in a more detailed and richer set of answers For "how to I customise this" or "how does this feature work", the above statement is true. For critical board offline situations, the above sets alarm bells ringing loudly. Critical issues need a formal support ticketing system - which is included in the licence fee. Come to think of it, no other service I use has separate support and licence fees.
For those that wish to retain ticket support longer term, we will be unveiling a premium support option soon. No, just no.
 
I already discontinued my other IPB forums as the cost/benefit ratio slid off the scale.
A 60% price hike means I will now have to look at other options for my final licence, it would be easier if I felt any degree of trust or loyalty to Invision as I would just pony up and pay the money, however - and sadly for such a long time customer, this is far from the case. I cannot trust you as evidenced through the lifetime licence fiasco, and I feel absolutely no loyalty due to this 60% price while reducing access to critical support.
Very disappointed.
What I would like to see?
Cancel premium support plans and retain this as part and parcel of customers licences. Maintain current pricing plans for existing customers and roll out new price structure for new customers.  
 

Woke up today to find out that we have a 48% rise in the renewal price and no email support, and that is the final straw for us. So, instead of $70 every six months, we will be paying $220 yearly and that starts next January. Sorry, not on guys.
With all the negative changes to the marketplace recently, and now this, means I will be moving away from IPB to one of your competitors instead.

After a quick and dirty calculation, you even win if you lose 30% of your customers. So, from a financially viewpoint it's a good business decision. And another plus, your support effort will be reduced too Congrats.

Woke up today to find out that we have a 48% rise in the renewal price and no email support, and that is the final straw for us. So, instead of $70 every six months, we will be paying $220 yearly and that starts next January. Sorry, not on guys.
With all the negative changes to the marketplace recently, and now this, means I will be moving away from IPB to one of your competitors instead.

Thanks, I have added this step to https://invisioncommunity.com/developers/docs/development/extensions/coremodcp-r151/

Please, please, point them at this discussion and request that they actually read it - because the moment you mention this application, they will switch to "3rd party issue" mode.

I suggest that those members clear their browser cache on their device. I use Firefox on all my devices and do not have issues, so it could be a cache issue maybe?

I have an update for 4.6. If any of you would like to test it before I release it, please feel free to PM me.

I have an update for 4.6. If any of you would like to test it before I release it, please feel free to PM me.

I have an update for 4.6. If any of you would like to test it before I release it, please feel free to PM me.

When updating an application, have been having issues with Notifications being displayed while in development mode.
I would get this error while trying to view Notifications from the  "View All Notifications" in the frontend of the forum.
And the spinning wheel of death:

If there is a saved Notification within the 'core_notifications' database with a notification_key in the table which does not have a notification_parse function, you will get the above error. This only happens when in developer mode.

ah, i had to clear system caches, now all errors are gone and it's working as expected. thanks @Adriano Faria
 

Turns out this was caused by @DawPis DP45) Mod Action Notify Enabled 2.0.5.1 plugin which was creating custom notifications which were associated with the core application. So once the plugin was disabled, the 3rd party notifications were still loaded because they were associated to the core application but the parse method was missing because of the disabled plugin.
We're going to catch the error on the frontend, but this will also result in a guideline change, any future submissions which need own notification types will have to be a proper application with an own notification extension.

When updating an application, have been having issues with Notifications being displayed while in development mode.
I would get this error while trying to view Notifications from the  "View All Notifications" in the frontend of the forum.
And the spinning wheel of death:

If there is a saved Notification within the 'core_notifications' database with a notification_key in the table which does not have a notification_parse function, you will get the above error. This only happens when in developer mode.

This sounds like you may have a php extension (for example Redis, PHP-FPM) which requires a module/RPM update for PHP 8.
I would check to see which php extensions are installed on your server, and install/update the ones required for php 8.
 

Will be checked soon. 🙂

I could tell you another secret for getting the dev files but...
<muffled sounds>
<you catch a glimpse of a random IPS staffer dragging a limp body into the distance>
 

Oh I never thought that, but I couldnt find any others so gave it a go.
This is fantastic, thank you. I must have checked every possible link except the changelog. 🤦‍♂️
 

Not sure how they can change that to be more obvious, other than maybe altering the language bit there to say "Changelog / Previous Versions".
Maybe make that an actual button rather than just a subtle link?
🤷‍♂️

I don't have developer mode on.
I didn't think this was the normal behaviour, hence the reason asking for clarification on this.
I will update to version 4.6.2 and see if that fixes the issue. If that fails, I will do a fresh install instead.

not normal
unless you have enabled developer mode! which is... normal in that case 🦝