DawPi

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

Here 🙂

It was done as a custom work. I'll check what I can do.

Buy one product with X quantity. 

Happy Hump Day, team! Shout-out to @nodle for being a big fan of these posts. 👏 
In today's community management hump day topic, I wanted to chat about one of the most powerful ways you can inspire kindness throughout your community. Kindness is an essential ingredient to a successful community. 😌 I know it's a little cheesy, but it's important.
Some times you may experience negative players attempting to derail your day because, well... misery loves company. In my experience, one of the most profound ways to fight toxicity in an online community is by... not fighting at all. Instead, it’s by offering kindness to those who need it the most. That’s done through understanding, outreach and personal displays of vulnerability. 
 

Like a drop of ink in a glass of water, a troll's negativity spews throughout the community (and possibly other communities) in such a profound way that it dissuades others from participating. The compounding effect of their flippant responses, snide remarks, sarcasm, arguments and attacks ultimately creates chaos. 
Fight the ick with understanding, compassion and vulnerability. The act of opening up to an anonymous person in need not only can inspire them to change, but it opens a door towards further self-discovery. 
Being vulnerable with your members also empowers them and you.
Next time you notice a toxic member’s pattern regarding how they post, remember there is more that meets the eye. Hurt people hurt people, so take the opportunity to be kind, practice being vulnerable and watch your community blossom. 
How do YOU battle toxicity in your Invision communities? Sound off in the comments below.
As always, here is a list of changes made to the platform in the last seven days. Nicely done, team!
PS - I have an exciting blog post on the way. Stay tuned. 🙃

Thanks - I have fixed this issue for a future version.

As you may have noticed, we've been doing a lot of work to prepare Invision Community to use PHP8 as the minimum version.
If you are an Invision Community Cloud client, then you do not need to worry about any of this, and can happily click out of this topic.
For those who host Invision Community on their own servers, then please read on.
PHP7 is now end of life and from November, PHP will no longer offer security updates. PHP8 is a major update which brings many changes including how errors are either logged and means that what was a harmless notice or log entry is now a fatal error which Invision Community cannot capture.
We have introduced the application and plugin scanner to ensure that your site is not "bricked" (unrecoverable from a fatal error) when you upgrade to PHP8 although you currently have the option to re-enable any disabled applications or plugins.
From the November 2022 release, we will require PHP8.0 as the minimum version. If you are currently using PHP7 then you must contact your host and plan your PHP8 upgrade to ensure compatibility with Invision Community from November onwards.

We are rolling out dismissible AdminCP banners to those who are currently on PHP7.
If you are unsure what version of PHP your server is running, simply log into your Admin CP then navigate to System > Get Support and check out the PHP version block.


The November release of Invision Community will also mean that you are no longer able to re-enable plugins the application scanner disables. We continue to work on this tool to refine its error checking and logging verbosity.
If you have any questions, please let me know below.
 

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."

I have mod for that if you are interested. 😉
 
 

Rather than deleting topics when you resolve your issue, it is better to comment with how you resolved the issue. This way, as a community, we help other individuals who may be searching for the same answer or may help you find another way of doing it that you didn't think of.

What I can suggest is add new column to the right area with last update date also. That should works then.

New template, waiting for aproval!
 

As a SULK dev I can handle it for you.

Hi. Update the software to the latest version where only registered users can make donations.
More here: https://invisioncommunity.com/forums/topic/468875-delete-mass-pending-invoices/?do=findComment&comment=2903729
 
 

public static function roundedDiffFromSeconds( $seconds, $memberOrLanguage=NULL ) { $now = static::ts( time() ); $then = static::ts( time() - $seconds ); return $now->roundedDiff( $then, $memberOrLanguage ); } Don't panic! This is not related to all the other DateTime shenanigans going on. Just a small bug with a big return - routinely 52 years.
The problem is having $then calculated as time() - $seconds. That needs to just be seconds:
$then = static::ts($seconds);
You only use this in one spot (admin\stats\timeToSolved.phtml) that I can see so probably just been overlooked for a while.
Full Explained working on something not quite two minutes old:
$now: 1663390800
$then:  1663390800 - 1663390700 = 100
$now->roundedDiff ($then);
roundedDiff then immediately calculates its own difference:
$this->diff($date) which in this case is $this->diff(100) which is the difference between right now and 100 seconds after January 1, 1970 midnight UTC.
 

This has now been resolved in the latest release (4.7.2). Please update to this version to resolve the problem. If you are still experiencing the issue after upgrade, please let us know.

Trying to use the CSS field to customize the results, but not working.
Another great feature could be adding Google option on Advanced Search. CSE is used for "all". I suggest that "all" uses IPS search and for CSE should be added another option, that should be Google.
😬

It's always possible to just restore the backup in a different location (even locally), retrieve the photo, and upload it to the user's profile on the live site. As long as you're willing to go through with it just for a photo. 😋

You may use my mod for that:
 

Only if you restore the database backup made before merge operation.

Ask your host provide to increase the specs of your account. I think they are too low to your needs.
On default skin too? I doubt. Update your skin.

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Hi 🙂
My system logs are bombarding with these logs:

 
There is a "1 prefix" in the plugin path which is very weird. 😉
 
It's a known issue or am  first with that?