Percival

It was not something in which we could easily share, however as my colleague stated there, we have added into the latest patched release something that will resolve the issue during the upgrade process
I see your issue has also been resolved in the ticket on this one, so you should be good to go. Please let us know if you encounter any further issues

This was patched this morning so if you're encountering this, please ensure that you have the latest files from the Client Area.

It seems you're not alone with this issue: https://invisioncommunity.com/forums/topic/467994-update-to-ips-47-gives-me-this-error/ So anyway what was the fix there @Marc Stridgen? (just in case I or anyone else encounter similar problem during update)
 

It took me longer to read and understand what I just read. 

Maybe it's just me, but the bionic reading did not change my reading pattern at all. I just ended up reading it at normal speed. In fact maybe even slowly since the darker contrast to lighter contrast makes you pause more while reading. I understand what they are aiming for, but I preferred the normal paragraph in the link above. Maybe it's just me though. 

Hello,
The 4.7 version is already pending approval. I’ still have a lot of resources to check compatibility.
I’ll take a look at this after that. 👍

Yes, I think that is the plan all along. A marketing strategy to disappoint all the self hosting customers and gradually convince them to migrate to cloud. 
I do wonder how many live forums are out there successfully running and using the IPS cloud business plan.
Any links? I would like to see some.

Something must have happened along the lines/updates. I would encourage everyone to re-save because they may not be sending notifications. I also noticed reaction notifications not going out and this was the reason. Push notification alone were mostly not active. Weird, but glad I found this. All these months waiting for a fix...lol. I re-saved notification preferences on all my sites. Maybe it'll stimulate more activity...

And an option to hide it for those that do not want to upgrade to the cloud service.
I can no long use the global search field on my mobile, not even using my mobile's desktop mode. Why? Because the "Upgrade to cloud" link is using up the space where the SEARCH should be

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

I'm investigating this issue via a ticket.

I will probably do this until retirement, so we've got at least 20 years to go. 🙂 
Or unless I marry rich. Seems unlikely. And even then I'd probably work or I'd go crazy.

Of course only guest viewable content!

Does it submit all new content or is it permission based? I guess it should not submit content that is not viewable by guests.

@Matt has already explained this: "(...) that will likely take 6-12 months to really complete, so it's not something we can do on a development sprint."
 

You forgot: "In 5 years from now." 
And yes, i mean it.
 
Maybe they do, but they don't care. There are hundreds of community posts screaming for improvements but they couldn't care less. You're better off preparing for your funeral than waiting for a patch that adresses long standing issues. They simply don't have a big enough team to work on whatever they want + plus community requests.
5.x may address some issues, but you're better off not betting on it. Never take their word, there's still a ~3 years waiting list of other promises.
But what you can expect is another new re-design as usual. Because new looks and marketing sells best. Let's just cross our fingers that at least some of the underlying ancient code gets updated a long the way.
 

I was just reading the release notes for IPS Community Suite 4.6.8 Beta 1. I'm assuming that a fix for this issue has not made it into this version either, correct?

Regarding Marketplace, is it possible to post the date a new version was uploaded while it's awaiting review?
It is frustrating that we pay renewal fees on these apps and weeks of time are taken away waiting for approval.  Also, the only reason we purchase them is we find them to be an enhancement to our sites, those enhancements (like Bookmarks) are now missing.

Too bad it wasn’t tested enough when it was added in 4.6.2. It’s a really nice feature if it works.

Thank you @Matt @Charles @Lindy @Jordan Miller for stepping up, owning this and finding a compromise, especially one that is able to support and help protect struggling small fan communities and not for profits. It is hugely appreciated.
For what it's worth, I'll be re-adding my card details back and intend on renewing all my licenses that are due in the next 3 months.

I want to thank you all for your feedback. I appreciate everyone who took the time to leave their thoughts and concerns. I've read every single one and replied to almost all of them.
Firstly, I want to say that I understand that the messaging that went out ahead of this update fell short of what you deserve, and I want to apologise for that.
After spending two days reading every single post, almost all concerns fall into these three areas:
1) The future of support
I've seen many people use the phrase 'no more support', which isn't true. I know the change from ticket support to staffed community support is a significant change, but I genuinely believe that it will benefit customers. I believe that we can create a living knowledge base of solved issues just like many brands do. For example, when I have a problem with my iPhone, I google it and invariably end up with a link to a topic within their support forums with a solved answer. I don't need to raise a ticket with them and wait for a reply.
There are many "what about" concerns mixed in, and I ask you to try the new staffed community support areas and give us your feedback once you've used it regularly. We will work with you based on that feedback and make improvements where it is needed.
We have custom functionality that shows our team links to your client accounts, including license keys, etc., so we know who you are and have all your information right next to the topic. You will never need to divulge personal information, or even your site URL if you do not want to.
If your support issue is complex or needs developer intervention, with a click of a button, our technicians can convert this into a ticket for you and we will continue to resolve the issue with you in that ticket.
You will be in safe hands.
2) Price Rises
We have not raised our prices for well over a decade. We've always been reluctant to do it and held off for too long, resulting in a large jump to make up for a lost time.
We can't reduce the prices to their pre-September levels, but we will be much more mindful of price rises in the future.
3) Annual Renewals
We want to simplify billing and reduce the number of invoices we need to send, and you need to pay. An annual invoice seemed logical to achieve this.
However, you have made it clear that moving to annual renewals affects your budgeting, and we have listened to that.
We have reverted this decision and have restored 6-month renewals in your client area. This is not a temporary one-off offer; it's a permanent change.
Again, I want to thank you all for being so vocal and passionate about Invision Community. We want to keep offering you the very best community platform to help your communities succeed.

Wow...  spent the last hour or so reading through the 16 page thread so that I would not just post the same thing that has been said a million times already and hopefully bring some constructive feedback.
Communication
Using terms such as "modest" when describing an increase of 48% (if someone licensed all applications) and anywhere from 36-60% on a per product basis struck me in a bad way.  Statements like "It's not bad news" also did not sit well.  In fact, reading the entire message there was nothing at all that came across as "positive".  If you're going to break a bunch of bad news, it might help to drop in some "good" tidbit of something to look forward to.  Bring both the carrot AND the stick.   I understand costs are higher and this is a quality service.  I love the product and I have supported the company for literally decades.  (I've actually met and spent nearly a week with Matt/Charles/Lindy several years back when I was considering working for IPS.)  However instead of simply noting the price change is effective immediately, I would have suggested having it take place after the following renewal.  Whenever your NEXT immediate renewal is, it would renew at the existing rate, however on the SUBSEQUENT renewal, the new price would take effect.  This gives people time to adjust and prepare.  At the end of the day, it won't break the bank for me... however it would have been much more appreciated to have had a bit more heads up.   Support
I generally try to come to the forums and find the answers to my questions first by searching before I've ever opened a ticket.  I also appreciate the fact you're trying to simplify the support process.  One thing I might suggest you consider is having a section within the support forums be configured as "Users can see topics posted by other users?" being set to no. This would allow the forums to be utilized, but also allow individuals to ask questions in a more private fashion.  Information that is helpful and could be of benefit to the community could be exported using a moderation rule to the "public" forum or into whatever KB system you're looking to implement.   What is going to happen to the Support tool within the ACP?  One of the features that I loved was that if I had to create a ticket, at the same time a support login was created.  By needing to visit the community, there is no way to allow the support team to quickly login and check what is going on.  I foresee the following situation playing out: I have a problem and come to the community asking for help.  Given that I would have already searched for an answer before posting, I'll create a thread.   If it's not a general "how do I" question and instead is "something is broken" situation, the IPS support person will need to create a ticket on my behalf and collect information.  They'll also have to ask me to create a support login for them most likely.   This will then put the delay back on me to get this information and reply to support who can then engage to help. If this is a situation where "something is broken", typically it's more urgent than a "how do I" question where minutes can matter.  If my site is offline or if a major feature is working, having a delay of a full round of back and forth can be painful.  Can we come up with a way to reduce this step?  If the support tech IS going to create a ticket on my behalf, he/she should have access to everything they need to engage without feeling like we're starting over.  I'm hoping those tickets that are created by staff are prioritized so that not only do we have to wait for a ticket to be manually created for us, but then also assigned to someone to actually help. Developers
Having the Marketplace and the developer community is a feature I see as being critical to my ability to be successful.  There are certain features that are VERY important to my community that I understand that does not make sense to include in the base product.  So having 3rd parties that can customize your product in a way that makes me successful is super important for me. Matt noted about it being difficult to determine how to support developers in terms of who should be able to get free licenses, etc.  My suggestion on this front is to consider something like Microsoft and some other large software companies do....  offer a tiered developer program.  The base developer account gets you a base set of features and access to the developer forums.  The next tier includes maybe access to a private slack channel, etc.  And the "gold" tier developers might get that a free license as well as maybe something like priority app review.  You can define milestones to reach each tier such as XX in sales or YY number of installs.  I'm most likely not the best one to suggest what those milestones would be, but I think that would be a great conversation to have with your 3rd party developers.  This would make a fair system and reward those that drive the most value within your developer community.  It would also provide incentives/goals for those newer developers to reach those higher standards.  (You're making an effort to gamify communities, maybe this is an opportunity to do the same thing within the developer community here?) I appreciate no one likes getting bad news and that these are hard things to do when they need to happen.  Hopefully some of my notes above can help as you move forward.  Finally I hope my feedback is received as it's intended... as thoughtful constructive suggestions and not a general "b***h fest".   Good luck and here's to the next twenty years.

It's not our fault that IPS chose to be competitive and not raise the prices in line with cost of inflation each year. I'm very grateful they didn't, but that's honestly on them. They just can't come along out of the blue and ramp up the costs for whatever reason is behind this and expect people to embrace it.
Whatever it is that's causing the company to dismiss the feedback of their loyal core community customer base and steadfastly refuse all requests for some reasonable compromise, like retaining 6 month renewals.
It's very difficult justifying the cost of IPS 4.6. Since we're paying over and over again for it, we lose all our investment if we our cancel renewals, but I'm not willing to pay a year up front. I couldn't do it anyway. It's been the most problematic buggy release for quite some time.
Honestly, I've been with you since Ikonboard and I've never felt so disillusioned.
I'm also so tired of the all the patronising 'Fam' and bizarre hump day rubbish, please grow up already especially if you're being so corporate. It's a shame to see what this forum community has become in the last year.

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.