Charles

We are hosting our first live video stream to chat about our October release.
This is a trial we are doing to see if everyone likes it and may start doing them with each release. 
Since it's a trial, please forgive us if we mess up or are otherwise awkward 🙂 
Feel free to post questions in the comments on the Event entry and we will try to cover some in the video.
 
 
 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

Please don’t encourage him. He would actually do it. 

This is fixed now.

I always advise clients to not put too much effort in a troll. If someone is just there to disrupt a community, ban them and give them no further thought.
If it's someone who just needs to cool off then you can do a warning but I usually say one warning is enough.
No time for distracting you from your good members to spend time worry about a bad member's feels.

There are platforms other than Apple?

We were recently comparing our page speed to a competitor that people always go "Oh they have an amazing page speed score!"
Turns out, they just hide all their JavaScript from Google. Totally a cheat and totally against Google's rules but the almighty page speed score was high!

I always advise clients to not put too much effort in a troll. If someone is just there to disrupt a community, ban them and give them no further thought.
If it's someone who just needs to cool off then you can do a warning but I usually say one warning is enough.
No time for distracting you from your good members to spend time worry about a bad member's feels.

I always advise clients to not put too much effort in a troll. If someone is just there to disrupt a community, ban them and give them no further thought.
If it's someone who just needs to cool off then you can do a warning but I usually say one warning is enough.
No time for distracting you from your good members to spend time worry about a bad member's feels.

Hey Adlago,
I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.
I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.

There's a lot of confusion here, so I'll do my best to address it all.
Why have you removed CSS editing?
First off, we have NOT removed the ability to edit and add CSS to your themes. When we released Invision Community 4.0 way back in 2012, we added a "custom.css" file and asked everyone to add their custom CSS to this file. This means that when we make changes to the core CSS, you do not have to merge changes, or re-apply edits. Your custom CSS is untouched.

This is exactly what CSS is designed to do. The core CSS may contain something like this.
body { font-size:14px; font-family: Helvetica; margin: 10px color: black; } So, what do you do if you want to change the colour to red? In the past you could edit this core CSS file directly and make it like so:
body { font-size:14px; font-family: Helvetica; margin: 10px color: red; /* Changed color here from black */ } This would work fine BUT if we changed our core CSS to change the font-size to 16 like so:
body { font-size:16px; font-family: Helvetica; margin: 10px color: black; } This will now overwrite your changes, which means you'll need to re-edit it back to:
body { font-size:16px; font-family: Helvetica; margin: 10px color: red; } This does work, but means you are constantly having to compare your changes to ours.
Fortunately, CSS (cascading style sheets) is designed to allow new CSS files to overwrite rules that we set, and that is why we have a custom.css file ready for you to make your upgrade-proof edits.

So, if you wanted to make the body colour red, instead of editing our code and maintaining changes, you simply add this to custom.css
 
body { color: red; } CSS knows to combine OUR rules with YOUR rules. It's exactly what CSS was designed to do. The computed result (how the browser sees it) of this is exactly the same:
body { font-size:14px; /* from our core css */ font-family: Helvetica; /* from our core css */ margin: 10px /* from our core css */ color: red; /* from custom.css */ } This is clearly a much better way of changing the CSS rules. You can keep all your custom code in one place and you no longer have to maintain copy and paste edits to core CSS.
In short, CSS editing STILL VERY MUCH EXISTS!
Why this change?
To be frank, it's 2022 and there's no valid reason at all to be editing core CSS when CSS itself was designed to cascade and make your lives easier.

We should have locked out editing of core CSS a long time ago. As the web moves on, we have to move on too. Serving CSS from a single CDN will improve the page speed of your site as it will come from a cached no-cookie domain.

No modern application out there will allow you to edit core CSS, there just is not the need.
I realise that for a very small number of people this means changing how you work, but this is how you should have been working since 4.0 was released a decade ago.
If you actually use custom.css I promise once you have completed the initial population of this file, your life will be made so much easier!
This is industry standard
If you look at other apps, they allow you to add custom rules that cascade over the core CSS files. Like Squarespace, and Wordpress which states: "You can use the CSS editor to customize the appearance of your WordPress.com site. It works by allowing you to add your own CSS styles to override the default styles of your theme."

If you want to schedule a call, just email sales and we can book a Zoom meeting 🙂 

We didn't make this up 🙂 we modeled it after literally every SaaS service out there.
I might submit that an "upgrade-friendly solution" is 100% what we should always choose.

We didn't make this up 🙂 we modeled it after literally every SaaS service out there.
I might submit that an "upgrade-friendly solution" is 100% what we should always choose.

We didn't make this up 🙂 we modeled it after literally every SaaS service out there.
I might submit that an "upgrade-friendly solution" is 100% what we should always choose.

This is EXACTLY what makes it the right solution. This file was specifically created for this purpose. It even says so when you open the file. 
/** * This file is for your custom CSS. * This file is not modified or overwritten during upgrades */ This describes the purpose and why changes should only be made there.
You have no argument against that, because there is none. You are essentially just in denial. You are saying “if I was allowed to do it the wrong way in the past, you better let me keep doing it the wrong way”. And ironically, this practise is NOT an argument to revert the change, but instead an argument to make sure that this practise is indeed being stopped. 

Oh I see. Thank you so much!! 

Make sure you are viewing your cloud account. I think you are viewing your self-hosted license.

All of our cloud plans have email support 🙂