SJ77

HI Stuart
I appreciate you clearing that up. Not sure how I missed that. But really glad this has been resolved.
Thank you 🙂

I can confirm this was addressed in 4.7.9
- Added status badges (pinned, hidden, etc) to the grid view.  

Yes, but iOS 13 is ~3 years old so we shouldn't abandon it so soon.

@Matt is there something that lists the requirements for IPB from the UI perspective?  Like what version of Safari, Chrome, iOS, etc?
I’d like to post something that outlines a set of minimum system requirements to ensure compatibility.

A fix is now available for this issue in new downloads of 4.7.9 and for those already on 4.7.9, it can be obtained from the AdminCP > support page in the top left box.

Very very very unlikely, given the previous issue. What resource, and what message is being received?

Red Hat based distros have one big advantage, they have a 10 years long term support, while Debian is only 5 years.
At least for me, that matters a lot.
Regarding 3rd party repos, security patches, etc, they also have all that.
From my experience on working with some Linux Distros, Red Hat distros are the most stable ones. 

I've taken a look at this issue, and it's caused by new javascript code in Invision Community taking full advantage of the ES (2020) syntax, specifically the chaining operator, like so:
ips.getSetting?.('baseURL')?.replace This is only supported from iOS 13.4 onwards (https://caniuse.com/?search=optional chaining operator)
We can remove the chaining operator from this line of code which will fix the issue, but moving forwards we are more likely to use it again - especially for Invision Community v5.

I have tagged a developer on this to see if there is anything more we can do to assist or any recommendations. Someone will be with you as soon as they can.

There is an issue we're looking into with lazy loading and these older iOS versions. 
What videos are they reporting? Are these videos which have been uploaded to a forum post? Are they embedded YouTube videos?
 
These two issues, I would recommend clearing their cache as it sounds like they have corrupted cache.

no forum images
happens on up to date chrome browser
just resize the window to tablet size to see it 

I can confirm that members of our forum have also had the same problems described above since upgrading to 4.7.8.
Older iPads experiencing layout issues, images in older posts not displaying correctly. 
 

A database backup size may also be added if your hosting account creates one

Or it's a recurrence of this:
Anyway...it's something for Invision to investigate.
 

Huge thanks to @Daniel F for risking his iPhone by installing the latest iOS beta to get this feature working for us!

Love this!! Super excited. Nicely done! 

oooooOOOOOOooooo!  I'm excited to see this! 

(And is that a feature that I see available to non-cloud users too?!  What will people start thinking??)

Yes, everything works fine on my other devices. Seems to be an issue with the older iOS versions?
I'm able to reproduce this issue on ipsfocus.net too even after clearing all website data in Safari settings.

Please see the attached screenshots.
The same issue happens on a Private tab.

Yes, it does - it randomly generates one specifically for each site. If you have the above repeatedly appearing, simply disable/re-enable the IndexNow integration to generate a new key.

Ha, thanks for the help. This was less painful then last months task of enabling NGINX and setting up an SSL cert to point to a subdomain with a port number. 15+ years of running a website and I still feel like I know nothing!

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.
 

viewtopic.php is most likely phpBB, which they may have used prior to vBulletin.

Steps to reproduce:
Enable the advanced setting Enable template disk caching? Add some random text/content in a template, and verify it shows in the template you edited. Revert the template, and verify that the page still shows the content you added in #2. Clear the cache from the Support page, and verify the content you added is now gone from the template. Re-saving the template as-is, with no edits, and then reverting it again also works.  
The issue is with the REVERT button not updating the cached file (unlike the SAVE button).

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.