CoffeeCake

Hold up. It's still horrifically slow on your infrastructure. There is a penalty to all of your customers from the latency, shifting, and time to paint. This needs to be a very high priority, and is an item which requires consideration and planning over a stretch of time. When did/will you start that 6-12 month epic? Occam's razor and all would suggest that planning and consideration may not be organizational or leadership strong suits (as opposed to the notion that there exists meticulous planning practices behind the scenes and the screw it we'll do it live approach what could possibly go wrong on the public facing side of things). Investments in human capital with strengths in these areas may be a good idea.

Now, with lay-a-way!

I am concerned that you might think that the feedback is "send an e-mail a few hours before changing the look of your web site (and oh-by-the-way-side-note-pricing-models-for-existing-clients-go-into-effect-immediately-with-no-significant-advance-notice)." The feedback is that you should have provided notice on revised pricing models, inclusive of what those revised prices would be months before implementing those changes so that organizations could make appropriate changes in their expected operational expenses. Speaking for our organization, there's no issue with the changes other than you didn't give any notice to revise our operational forecasts and planning, and our renewal is also in November. Thankfully, we have the ability to reallocate funds unexpectedly, yet not all of your customers are in that position, and it's rather poor form for what we consider a partner in our organization's ongoing success. I receive an e-mail from a streaming video service that their monthly price will go up one dollar with more than a month's notice. It's just inexcusable to have tied this all into throwing a new shade of paint on your sales site.

I don't understand this at all. What do you mean there was no great way to communicate this? From: IPS Community To: CoffeeCake <[email protected]> Date: September 1, 2021 9:00 am Subject: Upcoming changes to your subscription Dear community administrator, Effective December 1, 2021, we will be making the following adjustments.... <insert changes here>

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?

Seems useful for any implementation of an activity stream. Create opportunities to engage with the content where ever it is visible. Excellent call out. At the very least, put a reply button, yet opening an editor right on the stream would be ideal that then took you to the new reply at wherever the context was (i.e. your reply's position in the thread). Not only when fixes go live, but what issues exist. We need to know: That IPS is aware of an issue that happens in <x> circumstances That an administrator can take <y> action to workaround the issue until a fix is in place (disable a thing, not use a thing, configure a thing a certain way, etc.) That the issue is being addressed by the IPS team That a resolution to the issue is expected/will be available/is now available with <z> release/patch As an example, we are testing an upgrade to PHP8. You announced that something involving PHP8 has been resolved, which then informed me of items 1, 2 (don't use PHP8 yet), and 3. I don't know 4. Being able to go to a "status page" of known issues (i.e. bug tracker, but not like the bug tracker that gets turned on in beta releases), and see what known issues exist, if there are any workarounds, and when a fix might be put in place (think knowledge base), would help drive self-service engagement with support issues and help people like me know what issues are already known and when to expect a resolution (or how I can work around it).

For those on your Community in the Cloud platform, the public status service is a step in the right direction. I'm sorry to hear there have been such significant problems and launching it is likely the result of an onslaught of inbound support chat requests that the world is on fire for them. It would be great to take that reactionary energy and channel it into useful proactive solutions by being equally transparent with the status of known bugs/issues (and workarounds if applicable) and the expected resolution availabilities beyond "some future version." Your list of issues is welcome, however formalizing this along with "available next maintenance release," "next minor release," "next major release," "4.6.3.1," etc. would be greatly appreciated. I have no idea when the PHP8 error will be made available that the team worked hard to fix this week. I know you probably don't know either right away, and that it takes a bit of discipline, yet so does maintaining a status page.

There have been four releases today as of the time of this post, only two of which are publicly numbered (4.6.5 and 4.6.5.1). It's best to wait a bit for the oopsies to settle down before downloading and committing to your local code repository. Fixes an issue upgrading from older versions of Invision Community Fixes an installer issue in some environments Yes, it's progress, but not a fan of the hidden progress.

With a security update! That hasn't been backported to 4.5.

I think the gist of the ask here is that administrators have the ability to write something in conjunction with the title of the achievement that is viewable by the member. A free text field. Maybe you need to "Loot all four houses of Hogwarts and find the hidden muggle" or "Demonstrate the ability to be an expert problem solver" or "Unlock four Schrute Nickels" or leave the description blank--what ever makes sense at the individual community and achievement level.

Desktop: Mobile:

Oh, wow. Our site is mostly mobile traffic. Surprised these don't appear in mobile view. Not that we're planning on turning it on, but for those that do.... it's like it's not even there unless you look at the profile.

We absolutely will! I'd encourage anyone here to install 4.6 on their test sites and doing a high degree of testing prior to upgrading their community when 4.6 is eventually released. This is to be expected and natural. What are the blockers for releasing a beta? The sooner we start to be involved in testing, the earlier feedback your team gets, and the sooner those who won't test (despite all my warnings to the contrary) get a release.

Things look a bit different this time around. With 4.5, there was the "alpha" domain hosted site, then there was a series of beta releases, followed by full releases that may as well have been beta releases. It didn't go as smoothly as maybe would be ideal. So I'm wondering if we take our lessons learned, and have adjusted things perhaps, what the plan this time is for 4.6.

If the bug tracker is any indication, you need client testing before it will be ready for production. What's the plan for releasing alpha/beta releases for testing purposes to self-hosted clients? We're not particularly interested in achievements and will likely not activate them in our community, however speaking from a 4.6 release as a whole the changes look like they would benefit from testing code revisions and third-party integrations.

This looks to be still broken (if the fix is included on today's update here). Will there be a beta? We'd like to start testing this in our QA environment similarly to what we did with 4.5 from 4.4.