Matt

ips4_oauth_authorize - session cookie (expires when tab closed or browser quit) ips4_clearAutosave - session cookie (expires when tab closed or browser quit) ips4_lastSearch - whatever the flood limit is (usually 30 seconds) ips4_noCache - 20 mins, or when tab is closed/browser quit ips4_guestTermsDismissed  - session cookie (expires when tab closed or browser quit) ips4_language  - session cookie (expires when tab closed or browser quit) ips4_cm_reg - session cookie (expires when tab closed or browser quit) ips4_location - session cookie (expires when tab closed or browser quit) ips4_currency - session cookie (expires when tab closed or browser quit) ips4_guestTransactionKey - 30 days ips4_forumpass_* - 7 days

ips4_oauth_authorize - session cookie (expires when tab closed or browser quit) ips4_clearAutosave - session cookie (expires when tab closed or browser quit) ips4_lastSearch - whatever the flood limit is (usually 30 seconds) ips4_noCache - 20 mins, or when tab is closed/browser quit ips4_guestTermsDismissed  - session cookie (expires when tab closed or browser quit) ips4_language  - session cookie (expires when tab closed or browser quit) ips4_cm_reg - session cookie (expires when tab closed or browser quit) ips4_location - session cookie (expires when tab closed or browser quit) ips4_currency - session cookie (expires when tab closed or browser quit) ips4_guestTransactionKey - 30 days ips4_forumpass_* - 7 days

Last visit is not the same as last activity.
When a user's session is active, we update the last_activity column. When the user's session times out, or when they come back for the first time, we update last_visit time with the last_activity time.
 
It does look a bit odd when the sessions are so close, so perhaps we can do something being mindful of anonymous logins.

It's to ensure lots of HTML and markup isn't sent along in the schema, which is primarily for search engines. It just confuses and takes up space that is better served getting content over.

ips4_oauth_authorize - session cookie (expires when tab closed or browser quit) ips4_clearAutosave - session cookie (expires when tab closed or browser quit) ips4_lastSearch - whatever the flood limit is (usually 30 seconds) ips4_noCache - 20 mins, or when tab is closed/browser quit ips4_guestTermsDismissed  - session cookie (expires when tab closed or browser quit) ips4_language  - session cookie (expires when tab closed or browser quit) ips4_cm_reg - session cookie (expires when tab closed or browser quit) ips4_location - session cookie (expires when tab closed or browser quit) ips4_currency - session cookie (expires when tab closed or browser quit) ips4_guestTransactionKey - 30 days ips4_forumpass_* - 7 days

ips4_oauth_authorize - session cookie (expires when tab closed or browser quit) ips4_clearAutosave - session cookie (expires when tab closed or browser quit) ips4_lastSearch - whatever the flood limit is (usually 30 seconds) ips4_noCache - 20 mins, or when tab is closed/browser quit ips4_guestTermsDismissed  - session cookie (expires when tab closed or browser quit) ips4_language  - session cookie (expires when tab closed or browser quit) ips4_cm_reg - session cookie (expires when tab closed or browser quit) ips4_location - session cookie (expires when tab closed or browser quit) ips4_currency - session cookie (expires when tab closed or browser quit) ips4_guestTransactionKey - 30 days ips4_forumpass_* - 7 days

ips4_oauth_authorize - session cookie (expires when tab closed or browser quit) ips4_clearAutosave - session cookie (expires when tab closed or browser quit) ips4_lastSearch - whatever the flood limit is (usually 30 seconds) ips4_noCache - 20 mins, or when tab is closed/browser quit ips4_guestTermsDismissed  - session cookie (expires when tab closed or browser quit) ips4_language  - session cookie (expires when tab closed or browser quit) ips4_cm_reg - session cookie (expires when tab closed or browser quit) ips4_location - session cookie (expires when tab closed or browser quit) ips4_currency - session cookie (expires when tab closed or browser quit) ips4_guestTransactionKey - 30 days ips4_forumpass_* - 7 days

Finally, one of the most requested features for clubs in Invision Community is coming with our March 2024 release: Pages databases in Clubs.
You may be surprised to see a new feature being introduced for Invision Community 4 during our flow of news for Invision Community 5, but as we're committed to Invision Community 4, we wanted to continue to bring optimizations and improvements to the platform.
What is the benefit of this new feature?
Clubs enable communities to host multiple micro-communities with many benefits. Clubs allow more specialized and focused discussions on specific topics. This can lead to higher-quality content and a deeper exploration of niche subjects that may get overlooked when posted on a busy forum. Clubs also offer the ability to tailor the community experience based on the needs of that community. That customization is what this feature focuses on.
Pages is a powerful application that allows truly custom layouts for content areas. Simply by adjusting templates, you can create a news feed layout (it is what we use for this news blog area!) or something even more customized to your needs.
The March 2024 release allows you to create Pages database categories directly inside clubs, including custom fields and templates.
How does it work?
Setting up your Pages database to allow clubs to use categories is simple. Simply allow categories to be created within clubs when creating or editing a database.

Once that is done, club owners can add a Pages database category to their club in the same way they can add topics, galleries, etc.

Once the Pages database category has been added, you can then add content as you would any other club area with the added features of Pages, including custom templates and custom fields.
This example club uses a custom Pages database listing template to show the articles in a custom format along with custom field data.

Likewise, viewing an article in this example club showcases the use of custom templates to present the content differently from the standard topic templates Invision Community uses elsewhere.

Allowing Pages database categories inside clubs brings the opportunity for more complex custom areas making use of multiple custom fields along with truly custom layouts using templates. This is a great way to bring additional areas, such as news articles, into your club areas to compliment discussions.
We hope you enjoy this feature, and if you have any comments, please leave them below!

View full blog entry

Another Invision Community 5 blog is on its way right now.

There's been a lot going on, but we're waiting for a few things to be finished before we can show it off. We're currently revamping the theme resources UI, lots of Pages things in progress including a brand new easy page builder along with QA of what's already been added.

Thanks for the feedback. We do have robust spam management in place because a trial account is a full account which costs us a not insignificant amount of money. The trial is just for you and you have the option to convert it to a full account at the end of the trial. 
I'll see if we can tweak things a little though.

Thanks for the feedback. We do have robust spam management in place because a trial account is a full account which costs us a not insignificant amount of money. The trial is just for you and you have the option to convert it to a full account at the end of the trial. 
I'll see if we can tweak things a little though.

Thanks for the feedback. We do have robust spam management in place because a trial account is a full account which costs us a not insignificant amount of money. The trial is just for you and you have the option to convert it to a full account at the end of the trial. 
I'll see if we can tweak things a little though.

It does.

It does.

It does.

It does.

It does.

It does.

I am really hoping that Invision will see fit to include a save draft feature, at least for Pages, in IC5.  I have lost so much work over the years due to the lack of this simple feature.
I just lost 3/4 of an article I wrote because I was going to click another button, and some menu popup jumped in front of me.  But also, I have been attempting to work around this for years by setting the post date several days in the future, saving repeatedly, and then backdating it to the current time once I'm ready to publish. This workflow, frankly, is absurd in the year of our lord 2024.  Furthermore, it messes with block and new activity sorting by showing those articles that originally had future publish dates at the top of the list, even if they've been read or their backdated date has passed.

Probably so, some problem in PSI.
Now  I tested sites with other platforms - and popular sites. Everyone has this issue.
Apparently, it is a coincidence in the time of updating your patch, and the appearance of an issue in PSI.
You can close this topic.
Sorry for the trouble.

Looks like Topic Moderators, would be great to be able to migrate from it 😛 
Will it be possible to assign an “ordinary” member without any moderating rights to a topic ?

Not for this feature no, as its not related to banning in any way

It's great, but there's not enough user ban in a specific topic and a specific section.

Very nice feature! Definitely looking forward to this . . . and appreciating this advance notice, since we will build a few areas of the site with this feature in mind. Thanks so much!!

Good one indeed, many thanks for IPS team and well done.