Marc Stridgen

Well that's a good example @Sonya*! 
Kudos to @Marc Stridgen on that 10 minute response time! 🙂
Also saw @Mark H opened a ticket to track it within 30 minutes and stayed on top of the ticket all within an hour, nicely done!
I think if the future support works in that responsive and cohesive manner between IPS Staff and clients, it can work out well, however there will probably be a lot of duplication (which may be unavoidable anyway and likely the situation today with tickets). 

Glad you managed to find what was causing your issue there, and good luck with your theme updates

One of my colleagues has just been able to replicate this on your site, so I have sent this to a ticket so that we can further investigate

i had a feeling that &amp was a bad guy !
I changed my language and will be back as soon as i have a notification 🙂

There are no descriptions that can be added to badges, no. These are indeed rules. For example the conversation one is as below. So you would add a rule to give the badge, and add the public description to that rule. In this manner, you can actually use a badge in multiple ways. Take for example you have a "helpful" badge. You may want to give that for 10 topics being marked solved, but also add it for when they hit 10 reputation points. 2 descriptions of why they got it, but only one badge.

The only other way a member can receive a badge is if you give them one manually from a post. In which case it will say "xyz for a post in a topic". You can add a reason for giving the badge when you do so, and that reason will appear on the post in question it is linked to 
 

I usually feel the editor is beneath me and then I’m like no don’t be editorlitist. 

Well, that was quick. 😉
Thanks, and sorry, @Jim M.
All good now.

It's version 6, was fine... It was on 6Gb of 8Gb storage per node. guessing it didn't have enough storage to do the rebuild, just scaling it up to a larger storage... Still a good chance to find out a deployment isn't quite as tweaked as one hoped for 🙂

I removed it, refreshed, and then added it back in. 
Caching is afterall one of the two hardest things right...
Initial review seems to show a few users now. The old turn it off and on again trick worked. Onwards to the next niggle 🙂

OK, so instead of selecting "Plugin" select "Custom. You are then given the option of using the editor, which is the same thing. So the flow is this
 
Select custom

Add a name

Add some content on the content tab, then save

Select the permissions and save

Hope that helps

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.

There isn't currently any facility for doing this within the platform. What is it you are trying to achieve however? In most instances where this is the case, it tends to be for advertising subscription sign up. If you can give more information, there may actually be ways around this, by suppressing items from certain groups, amending error pages etc

The only way to do this within the software itself, would be instead of creating 2 pages, you just create 1 with different blocks that the different groups can see. 
Example
Topic feed - Thats fine as people can only see their own
WYSIWYG block - Permission only given to group A
WYSIWYG block - Permission only given to group B
Some page builder block- Permission only given to group A
Some page builder block- Permission only given to group B

And so on

It’s the profile field. If the user fill this field (or any other Editor profile field) will appear as a new tab in user profile. 

This sounds like a bug, which I'm investigating right now:) 

Done and done.  Problem fixed.  Thanks Marc!

Have you applied the latest patch within your support area? If not, please apply that and test again. There was a patch release directly related to custom profile fields.

Long time no post! 👋
Just checking in, going a bit against the grain - absolutely no issues with the price increases or changes to the support structure.

Communication could have been a bit better handled (a bigger warning before things coming into effect), but none of us are perfect.

With Matts head of hair, I can concur his barber works hard
#jealous 

The decision on the ACP support request button is still being decided as there are a few ideas. Once that has been fully decided, we will let you know.
With anything private in nature we recommend directly reaching out to us on our contact us form. Alternatively, if a support topic naturally starts heading in a direction where something is more private, you can straight up say that and we can transfer it to a ticket. We won't ask for these items (like logs, credentials, etc...) we will transfer it to a ticket.

With Matts head of hair, I can concur his barber works hard
#jealous 

With Matts head of hair, I can concur his barber works hard
#jealous 

Please could we have the conversation regarding our changes within the appropriate topic, rather than in someones support topic. Thank you.
With this, actually it's the opposite. We previously provided no support on the community, then provided little support on the community, now we provide full support and better staffing levels of support on the community. With regard tickets, we can send to tickets from here if there is a need to do so, as you saw above, so that part really hasnt changed. We can escalate as we did previously, report bugs as we did previously. You simply type your issue in a different location

With Matts head of hair, I can concur his barber works hard
#jealous