Matt

I would like to suggest two new actions for Achievements based on two settings in ACP:


I would like to award automatically members who:
Created a topic that gets “Popular now” Gives an answer that is highlighted as content with positive reputation

There's a bit of confusion here from my brief responses. I'll be a little more verbose in this reply. 😄
Here's how the system should work and why:
The rule 'Member logs in for the first time that day'...
 
... offers two options. "Time since registered" and "concurrent daily login". These are two different things.

The time since registered, is simply an award based on the length of time since they joined.
The concurrent daily log in is simply an award based on the number of days concurrently logged in (so logged in daily without fail for N days).
This rule is triggered by a new session being started. A new session is started in the code for you when you either manually log in with a form/button or visit with cookies stored.

Starting with Invision Community 4.6, we record the log-in date in a separate table.


With 4.6, when a session is created, a row is either added or updated for that day.
This means that from 4.6, future rebuilds CAN award the "concurrent log in" badges without a user needing to log in again IF they have logged into your 4.6+ version at any time.
With regards to time since registered: if you chose to rebuild your achievements, the rebuild iterates through your members and looks for valid full members, who have visited at any point since you launched your community and checks to see if their joined date is old enough for the badge.
If you chose not to rebuild your achievements, then you would need to wait until a user comes back and log ins to create a new session and trigger the event.
Hopefully this clears it up. I understand it's a bit confusing and it seems like you've had overlapping answers because it's a fairly complex part of the suite and what happens is really conditional on the length of time since you've upgraded to 4.6, and when you last rebuilt your data and when your users last visited.

Just six short weeks ago, Ehren hit record on a video that changed everything for Invision Community.
The blog was called "Introducing a fresh new vision for Invision Community 5," and it ripped up the rule book on what forums should look like and revealed a slick new look featuring a new forum home feed view and sidebar navigation.
A lot has been discussed, but we're not even close to done!
Before we bring you news of more features after Thanksgiving, I wanted to take a mid-season break to recap what we've seen so far.
First up was the introduction video, which gave a broad overview of the new UI Invision Community 5 would be sporting. Ehren takes us through many new elements, including the sidebar navigation, forum feed view, simplified post view and more.
 
 
Up next was a focus on dark mode, accessibility and mobile views. Invision Community 5 features the ability to have native dark mode without additional themes or complex variables to set up. Our aim with Invision Community 5 is to hide the complexities and technology and just let you focus on creating a great community experience for your audience.
 
 
Bringing complex theming to everyone was the message in the blog talking about the new theme editor. Now, you can make wide-ranging changes to your theme without the need to edit CSS or manage HTML templates, all driven by a smart and simple interface.
 
 
Next, it was my turn to talk about a new feature. I introduced two new features designed to help those who run support-based communities. Finding the most helpful answers and identifying community experts help your members do more with less time and frustration.
 
 
Last week, Ehren demonstrated our new icon and badge builder, which is an amazingly powerful tool to produce slick and professional badges along with the ability to customize your community further with emojis and icons for menus, reactions and more. Building ways to reduce the barrier to customization has been a strong theme for Invision Community 5.
 
 
Phew!
We can all agree that we've showcased a lot of impressive functionality coming with Invision Community 5 already.
But what does the future hold?
Lots! We have a lot of new functionality that we're putting the finishing touches on, and we can't wait to show you more. These new features further help to reduce noise in topics, make the community feel alive and bring long-needed updates to core components such as the editor. Not to mention, there is a significant update to Pages underway.
We also have a lot of less flashy updates, such as the new consolidated Feature/Our Picks feature, which is now a single feature.
 
Feature-window.mp4
 
An improved Moderators Control Panel brings a more uniform experience across deleted, hidden, and content waiting to be approved.
 

We're still on course for a release of Invision Community in early 2024 and can't wait for you to experience the future of forums.
What has been your favourite feature so far? I'd love to know; drop a comment below!

View full blog entry

Ehren is a superstar, he's barely scratched the surface on what he's been working on for the past six months. I'm really excited by these new views and the sidebar mode gives a very desktop app like experience, whereas the new mobile view is truly fit for purpose and not just a squished desktop view.

2030 at the earliest, I'd say.

We are not going to simply allow all our customers to never use Google Chrome again. 😅 That would be a terrible decision.
We will ensure it's resolved ahead of the removal later this year. We use an older plugin for jQuery to manage browser history state. We already plan to move that to native JS APIs in v5 and v4.

2030 at the earliest, I'd say.

You won't be able to place ads anywhere on the Live Topics UI. The advertisement system has had an update for v5, but I don't think we've spoken about it much.

I think I spent more time making up fake adverts than writing about it.

We are not going to simply allow all our customers to never use Google Chrome again. 😅 That would be a terrible decision.
We will ensure it's resolved ahead of the removal later this year. We use an older plugin for jQuery to manage browser history state. We already plan to move that to native JS APIs in v5 and v4.

We are not going to simply allow all our customers to never use Google Chrome again. 😅 That would be a terrible decision.
We will ensure it's resolved ahead of the removal later this year. We use an older plugin for jQuery to manage browser history state. We already plan to move that to native JS APIs in v5 and v4.

New blog: IC5: Developer Center.
 

2030 at the earliest, I'd say.

New blog: IC5: Developer Center.
 

New blog: IC5: Developer Center.
 

Yes but during 5’s lifecycle we will be removing it and using native. Any new front end functionality is mostly native. 

2030 at the earliest, I'd say.

2030 at the earliest, I'd say.

New blog: IC5 Commerce
 
 

Hi all,
Next week we plan on releasing a few blogs outlining what development looks like for Invision Community v5.
I was curious as to what changes you'd like to see, and what changes do you think are coming?

New blog: IC5 Commerce
 
 

New blog: IC5 Commerce
 
 

Hi,
No, we're not going to distribute other developers IP through a method they did not agree to.
If you have the app installed, you already have the files on your server. A competent developer would know where to look to get those and build whatever changes you want on top of that.

I have to admit, I find that to be quite an unfair assessment, as this is not the case at all. What is actually happening is that we tend not to add software functionality to solve what are ultimately hosting issues. To further clarify that statement, we don't even do that for cloud either. If there is a cloud problem, we solve the cloud problem, rather than writing things into the software to work around it.
So in this instance, we're trying to solve the problem of mail limitations by limiting the mail that is sent. The correct way to resolve this is to ensure you don't have a mail provider with limitations which will hinder the running of your software.
It's worth noting too, that solutions such as these come with their own problems. Using your example, we would end up seeing people who have limited it to the 1000 every 10 mins, and yet have 1500 emails needing to be sent being produced. Meaning that the backlog simply builds up indefinitely until something breaks. This is just one I can think of straight of the bat. 

I still remember when  Ikonboard 3.X looked so much nicer than Ikonboard 1.X 🤣

You won't be able to place ads anywhere on the Live Topics UI. The advertisement system has had an update for v5, but I don't think we've spoken about it much.

I think I spent more time making up fake adverts than writing about it.