Jim M

AAAAAAAHHHHHHHH
User error, sorry to have taken your time.
I intended to take this away from moderators and instead took it away from admins.  I did this a couple of weeks ago.

This is the Pages application. We do not use the Blogs app here but you can create a free demo to see it in action: https://invisioncommunity.com/demo

Ugh, I blame you for that, it came up as a warning to switch that.  🙂
I updated my details in the client area with the email.

Thanks for the steps/videos. I was able to reproduce this and got together some steps/further info for our developers. I reported this internally so our developers review and a fix will be available in a future maintenance release. Thanks for reporting this!

Please remove the redirect temporarily while you perform the URL reset in our tool and then you can then re-enable the redirect. 

Nice suggestion! We were thinking of possibly implementing tags somehow. This would be a great thing to discuss in its own dedicated topic 🥲 Appreciate the feedback! 

Thanks for the steps/videos. I was able to reproduce this and got together some steps/further info for our developers. I reported this internally so our developers review and a fix will be available in a future maintenance release. Thanks for reporting this!

Thanks for the steps/videos. I was able to reproduce this and got together some steps/further info for our developers. I reported this internally so our developers review and a fix will be available in a future maintenance release. Thanks for reporting this!

I would advise editing those configurations so you can see the custom URL. From that screen, you still cannot see it but the uploads configuration is in use. 

Sounds like something is not working correctly then. I created a ticket for you in our system (you should receive an email) to further investigate what is happening here.

Very interesting topic and while I fear, I may not be a direct help, as there are a lot of things which may be better served from a hosting perspective or otherwise fall outside our scope of support, I hope clarifies some of what you asked. (Of course invite others to chime in.) 
The biggest impact of the "score" that I see a lot are actually from third party services/resources being integrated. This includes all around from your server, to within our software, to even Javascript you load into the software. Even using Google's own PageSpeed tool, it will flag and bring down your score for using AdSense and some more of it's own products (which I always thought to be ironic). Everything will need to be weighed on whether or not you need the integration and what impact it brings to your goals. There are some items like "Remove unused CSS or Javascript", "Eliminate render blocking resources", etc... basically, anything that requires editing our core code will not be something which we support so these items would be up to us under our support policy to help improve.  While, I do not believe this may have been the answer you were looking for, I hope it helps.
 

I lost 😞 I had under 15 minutes for Adlago to post in this topic.

Support is still available for all. Just how you obtain support has changed. Support will be available via our support forum and is completely staffed by our support team. You can submit a topic as you previously submitted a ticket with an issue. We have the ability to transfer your topic to a ticket for items which need to be escalated or warrant it. So far though, things are going great on the forum 🙂 
Our priority support is available for purchase which does include email support, along with same-business-day response time and software upgrades performed by us.

My assumption would be is that your CDN is caching the output of a banned error page. Invision Community outputs "no cache" headers for those messages to prevent this from happening but you would want to be sure your CDN is honoring those.

Come here 🥲

Sorry to see you were having issues there. As a cloud customer, we are able to resolve that on  your behalf, and this has now been done for you. If you are seeing the same issue still, please clear your browser cache and test again. 

Please be advised I have transferred this to a ticket so a technician can investigate what is happening here with your Cloud Community. Thanks for bringing this up 🙂 .

I was a terrible skeptic (still am), but if this is how "tickets" are going to work moving forward, this is good.  🙂

I assume someone with that issue would not go into detail on the forums. Instead they would post that they have a security concern and need help privately.   

I also participate in a communal embrace. 

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

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 🙂

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.

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.