GlenP

When you have a section that has many subsections, it is impossible to go thru each section because it will collapse the tree each click and you have to find the section you were in and open in t again.
it would be most helpful if there was a dynamic previous/next links at the end of the article on the content page 
 

As a Cloud customer, I'm happy to wait for the final release. I also like to spin up a 5 day demo to get familiar with the changes in an environment closely resembling our live site. Will the demo site be upgraded prior to final release? I assume not as it is for attracting potential clients who may not like testing a beta.

It's better than nothing, but unless I'm mistaken we can't set it to be changed depending on post count anymore.

I've been experimenting with some options that should help improve the behavior in an upcoming release. 👍

That won't work across time zones though.
I'm in Australia and see times in my time zone. Many of our members are in the UK which is 9 or 10 hours behind. What I see as September 13 19:00 would show as September 13 10:00 in the UK.
Our members liked the Post Number plug-in but if doesn't return I won't be upset. I see how the numbers change after deleting, hiding, splitting posts. The PostID idea is interesting but I can't see too many members quoting numbers like this - 2931519 (a real post number from a few minutes ago on my Forum)
With collapsed quotes, we'll just keep educating people on linking rather than saying "post 1234"
Now, about the old Automatically hide/delete inactive posts feature......😮
 

That won't work across time zones though.
I'm in Australia and see times in my time zone. Many of our members are in the UK which is 9 or 10 hours behind. What I see as September 13 19:00 would show as September 13 10:00 in the UK.
Our members liked the Post Number plug-in but if doesn't return I won't be upset. I see how the numbers change after deleting, hiding, splitting posts. The PostID idea is interesting but I can't see too many members quoting numbers like this - 2931519 (a real post number from a few minutes ago on my Forum)
With collapsed quotes, we'll just keep educating people on linking rather than saying "post 1234"
Now, about the old Automatically hide/delete inactive posts feature......😮
 

you must be new to the internet if you think that would've happened 😛 

That won't work across time zones though.
I'm in Australia and see times in my time zone. Many of our members are in the UK which is 9 or 10 hours behind. What I see as September 13 19:00 would show as September 13 10:00 in the UK.
Our members liked the Post Number plug-in but if doesn't return I won't be upset. I see how the numbers change after deleting, hiding, splitting posts. The PostID idea is interesting but I can't see too many members quoting numbers like this - 2931519 (a real post number from a few minutes ago on my Forum)
With collapsed quotes, we'll just keep educating people on linking rather than saying "post 1234"
Now, about the old Automatically hide/delete inactive posts feature......😮
 

That won't work across time zones though.
I'm in Australia and see times in my time zone. Many of our members are in the UK which is 9 or 10 hours behind. What I see as September 13 19:00 would show as September 13 10:00 in the UK.
Our members liked the Post Number plug-in but if doesn't return I won't be upset. I see how the numbers change after deleting, hiding, splitting posts. The PostID idea is interesting but I can't see too many members quoting numbers like this - 2931519 (a real post number from a few minutes ago on my Forum)
With collapsed quotes, we'll just keep educating people on linking rather than saying "post 1234"
Now, about the old Automatically hide/delete inactive posts feature......😮
 

There is something similar here
 

We have talked about hashtags a lot internally over the years.

The core issue is that we're just not sure how useful they are on a forum. They work on Twitter because it's the only way to create a 'channel' of similar discussions. There is no other way to separate out conversations. So adding the tag makes it clear you're talking about that topic.

Obviously, with a forum you have categories, forums and topics. Adding a hashtag would be largely superfluous.

We have a tagging system for content already, and I would say that 98% of Invision Communities do not use it, and of the 2%, a small handful use it in a meaningful way that aids content discovery.

Hashtags are often mistyped further diluting the usefulness. Using your example, on twitter I've seen:

#blacklivematter
#blacklivesmatters
#blm
#blackouttuesday

Twitter actually is smart enough to know these are largely the same topic, so you will often see something like:

Trending
#Blacklivesmatter
Also talking about: #blm, #blackouttuesday

That's a great system but takes a lot of AI/human collating and computing power.

So our current position is simply that adding hashtags won't really increase content discovery in any meaningful way.

Facebook has hashtags but almost no one uses them.

Most hashtags are added for irony, like:

We're not going to add hashtags into 4.5

#sorryNotSorry

This creates a bunch of records and consumes a chunk of computing power and database size for almost no purpose at all.

We considered something like that a while ago. Once we reaslised that nearly all the swearing was in the off topic forum, we thought itwould only encourage posters to have a competition for the most ridiculous sentence possible and there's alreay enough rubbish in that forum.
In the end we just used 16 *s for all words we replaced. That destroys any chance of people inferring the meaning and thus it is impossible for members to get the context or get offended. IT has virtually stopped it now apart from 'jokes' copied over from other sources.

I wouldn't put any credence whatsoever into random "oh your site can be hacked you should scan it" type reports like that.
The one link you provided is for legacy 1.x/2.x/3.x versions (none of which are even supported anymore). That would be like someone telling you your computer running Windows 10 is insecure because they managed to find an exploit for Windows 95 posted somewhere on the internet.

Hello I would suggest a improvement for categories and tags introducing  taxonomy concept:
1. assign a basic structure, not a simple tree but a network model
2. extending it on posting new content
3. custom fields relationship useful for feedback/survey
4. define upsell, alternative, raccomanded content
5. multiple author/group for single posts/comment (relationship with other members share same/similar content)
This could improve the understanding of the order of things inside the community with some schema visualization and a genuine growth of it
Benefits: increase findability of content, great addition to Zapier @Matt, multilingual community thank you for it
some articles:
https://www.uxbooth.com/articles/introduction-to-taxonomies/
https://uxdesign.cc/hierarchical-taxonomy-ux-designs-secret-weapon-9510eb91a4d
https://www.seoptimer.com/blog/website-taxonomy/
https://invisioncommunity.com/search/?&q=Taxonomy

I can only say that this is on an internal suggestions tracker and is being considered for a future release.

So many misconceptions.
If @daveoh were to share his site, you would see it's very clean, well organized, has high quality content and a glance shows his backlink profile is strong. He also has little to no apparent ads.
@Nesa while I understand your concerns and understand your frustration, the sitemap itself is not the cause of your issues. This was posted earlier today and was already indexed by Google hours ago. I've checked some of our larger enterprise sites and their content from today is also being indexed in a timely fashion. I just searched the topic you referenced and it too is listed. There's no magic bullet in 4.3 or even other software that's going to put you on the front page of Google or instantaneously push new content directly to Google.
The big algorithm update of 2017 targeted a lot of sites with some losing as much as 90% of their traffic. Some of these sites flew under the radar with what Google considers low quality content and in Google's eyes, they were righting the scale. There are many factors that influence your position in Google, your index rate and frankly, whether or not Google just likes or hates you.
Ads
If your site has ads that detract from the user experience and content on your site, Google WILL penalize you and that was the single most biggest hit in the "Fred" update. An ad in the header and footer are ok. An affiliate link or "sponsored content" that is appropriately placed and blends with content is ok. Ads all over the page and in the sidebar are obnoxious to users and Google agrees and doesn't want to subject us to it (for which I'm, as a user, appreciative.)
Backlinks
Backlinks can account for up to 1/3 of your overall standing with Google -- that is, quality backlinks; not "hey, link to me and I'll link you back."
Content Freshness/Quality
You may very well have 15 million posts, but if they're all from 2003 and you get very little new content, your old content is going to have less value to Google and they may drop it. Keep it fresh, keep users engaged.
Google has gotten very intelligent and can distinguish rehashing the same musings over fresh information. General discussion sites with loose/generic content won't likely fare as well as those with unique, relevant content. Pages with thin content (such as picture threads, a bunch of "lols", etc.) are likely to get hit by Google.
 
Again, Google cleaned house in 2017 - many sites got hit, including those using Wordpress, vB, etc. There's just too many variables to get all up in arms over one component: a sitemap. A sitemap, even the complete absence of a sitemap is not going to cause your indexed pages to drop. If this has happened to you, it's because Google penalized you and dropped your content. A sitemap is also not a magic wand and Google will not consider it the be-all for indexed content. A sitemap is a good gap filler and provides Google additional insight, but most content is still indexed organically through links.
4.3 will provide for the mentioned improvements to the sitemap. Given 4.3 is so close, I'm sorry, but it would not be worth re-engineering those improvements for 4.2 and again, it's not going to be the magic solution you believe it to be. Unfortunately, I can only suggest focusing on the above list as one or more of those items is the likely culprit for your site being dropped.

I could REALLY use a prune feature.