Morgin

@Jordan InvisionCan I propose a brainstorm session over how to store and easily highlight these extremely helpful and long running posts in a way that pinning doesn't always fit perfectly for? I'm wondering if maybe a subforum called "Community Guides" or something where only long running and extremely helpful community generated guides could live. There used to be a whole lot more of those pinned in the server and self hosted topics forum, but some of that has gotten lost in the consolidation and forums refresh. Pinning is not great for mobile especially with a lot of pinned posts because it pushes new content below the first page fold, but I do appreciate how @Woodsmanis able to quick reference this thread to alleviate all the e-mail traffic. Anyway, just a thought! There's so much great community content on these sort of (now) niche topics, and having a one stop shop to see some of the great long running threads might be helpful.

@Jordan InvisionMight want to look at the pinned topics (including this one) and think about a refresh. Should be very very very few people left on the 3 family now.

Currently on 4.4 with upgrade planned for next week, so forgive me if this issue is resolved already. I have a section of my forums that requires a minimum content count to see or access (the "off-topic" section). Every few months, I'll get a member who will randomly start a topic in our support area asking how they get access to these "hidden" topics. Usually some variation of "I see a bunch of topics in the "Recent Updates" block that I can't access and get error code 2S136/V. How do I access them?". I've checked every time to see if somehow "honor permissions" on the block setting got turned off, and it's always fine. The user can't see the topics (or even the forum itself). Settings on the forums are: Minimum content count to see forum: 10 approved items of content (posts, comments, etc.) Users without read permission can open forum? (UNCHECKED) I'm assuming this is perhaps some sort of caching issue? Strangely, if I login as that user, I can't ever see these topics in the sidebar block. Apparently they don't consistently see them either - they just pop into the block from time to time. Is there any possibility the block caching is somehow bypassing the permissions system? Alternatively, is there some possibility that because the user is a member of a group that CAN access once the requisite content has been contributed, the block permissions is ignoring that and focusing on whether the member group as a whole has permission? I also use cloudflare, but it doesn't cache any dynamic content so shouldn't be interfering with my block permissions. At a bit of a loss on what's going on. Any advice appreciated!

My only comment is I would strongly urge someone to look at Discourse to see what a typical "basic" set of badges looks like and make it very easy for Invision users to implement such a "basic" set to very easily have a great user onboarding experience. This is the only area I think Discourse has been crushing us, and they really have pretty much nailed user onboarding through badges and gamification. I've joined two discourse communities recently related to some smart home stuff I'm doing (Hubitat being one of them) and the user onboarding with badges to reward participation and elevating to higher and higher trust levels the more things a person does to engage is just *chef's kiss*. Sort of like the below (although I dobn't think this is the default set):

The only reason I would say this is redundant is that both iOS and Android have built in capability to do a quick scroll to top. In iOS it’s universally just tapping the top of the screen. Android has a few different implementations but you can set it up with a gesture in any event. I understand that a button is super easy, but in this case it does seem like replication of native OS behavior.

Nothing to add, great video, but omg please don't ever ask me to smash a like button again.

I had a user note that they had spent a good deal of part of a day working on a post before submitting, and discovered that after submitting they were unable to take advantage of the 60 minute edit window we provide. They “tested” and seem to suggest that perhaps the window is being calculated from when the post draft is first started, and not when posted. I can’t seem to reproduce, but wanted to check with the community here to see if anyone has more specific technical knowledge of how the edit time is calculated and what triggers it.

Latest version of IPS? I haven’t personally benchmarked, but I’m going off what most the trusted PHP experts (and the PHP development team) have said about 8. Expect performance gains from JIT in certain specific calculation tasks and long running php apps. Most web apps (which aren’t either of those things) aren’t not expected to specifically benefit from the initial release of 8. If IPS is seeing a x2 performance gain, I would be shocked and that goes against everything written about the purpose and expectations for 8, but would obviously be a welcome surprise.

PHP 8 is not faster than PHP 7.4 for the vast majority of web applications. There are many great new features and language improvements, but speed improvements for web apps was not the focus of PHP 8. There will be limited reasons for IPS to officially support PHP 8 until it's baked a few versions, minimum.

Yeah sorry! Horrible reply on my part. @Ryan Ashbrook covered one of the big issues I had which was that ckeditor would randomly fail to load or would load improperly so certain functions were disabled. I don’t know how to characterize it other than very weird and annoying bugs that didn’t happen every time so were hard to replicate, but always related to JavaScript. There were also times the entire site would just stop loading about halfway through initial paint so you were left with broken stylesheets etc. As soon as rocket loader was disabled, all of that went away

Cloudflare Rocket Loader usually breaks IPS, as a heads up.

Going to be an issue if iOS9 is the latest the device supports. Your users are on nearly decade old hardware at this point

Thanks for the update! Looks great.

The comment Matt made was in reference to push via web, which isn't supported in iOS without using native apps. They now have a native app.

It’s easy, but man, I would never recommend to anyone who values their time and having a secure server to run their own mailserver. It is not low maintenance.