Matt

Yes, I'd like swipe gestures and pull down to refresh.

We've got a solution coming for 4.7.9.

Expect significant breaking changes to CSS, HTML and JS. PHP less so.

"The Old Man" telling us to get with the times is a special moment. 😆 Dark mode is 99.98% likely to be included with v5 without the need for multiple themes.

To be clear, data is not transferred from EU to US servers to troubleshoot issues on your community. People geographically located in the US may troubleshoot issues via the AdminCP, but we do not move data from EU to US servers to do this. I can't think of a reason we'd need to transfer PII out of EU and into US servers, even if we need to repair data or tables, etc. The article is a little confusing when it says: “Support access for persons in a third country to data in data centres in the EU also constitutes a third country transfer.” I think this means that someone in the US who needs to copy the data to a local data centre to work on it would fall foul of GDPR, but we do not operate like that.

It definitely removes the need for a native mobile app now.

There is much more to a SaaS platform than just servers and services. There are micro-services that tie these services together. We believe it was a micro service that we have used for over four years that failed. Our investigation is ongoing with AWS. As Lindy mentioned, please get in touch if you want to lodge a formal complaint and we will do our best to resolve it. I want to underline again that we are proud of our platform stability, with 99.99% uptime over several years. Incidents like this are rare but we do not take them lightly and have implemented an audit of alert systems, uptime monitoring, service statuses, etc to ensure we do not have a repeat of this event again.

They are, yes. It’s so the service workers can run.

Yes, we just had to tweak some our our JS code to allow iPhone to register as supported to the rest of our normal notification system. We'll update our docs, but to get iPhone notifications working you must complete the manifest in the ACP and use the 'add to home screen' feature. It won't work just with mobile safari in a tab, for example.

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

The longest awaited iPhone feature is almost here, native iOS notifications, and we couldn't wait to ensure it is enabled for your Invision Community. Invision Community 4.7.9 is iPhone push notification ready for when Apple release their latest iOS update later this month. This means you'll finally get notifications on your phone, even when you do not have your browser open, to alert you of new content on followed items and more. A feature Android owners have enjoyed for a while. With notifications, you can have an authentic native app experience with built-in Invision Community features such as the manifest editor. The manifest editor allows you to edit your theme icons, colours and URL for when your members add your community to their phone's homepage. This manifest file helps mobile devices understand how to display your community site when launched from the home screen. Your members can add your community to their home screen with the share button. Once it has been added, it looks and feels like a native app downloaded from the App Store. With Apple finally allowing native notifications and Invision Community's mobile-ready UI coupled with the manifest editor, you can have a real app experience without needing a mobile app. iPhone PWA.mp4 We intend to bring more functionality and ease of use to mobile devices over the coming releases. We hope you're looking forward to iOS native push notifications as much as we are! The features discussed in this announcement are available in both Invision Community and Invision Community Classic. View full blog entry

Thanks Randy, We're taking this very seriously. More information will follow.

We did experience an outage, however it was 6 hours, not 12 hours. Our status page monitors this forum (which was down for 6 hours) and the US cloud platform (also down for 6 hours). Your screenshot adds them together. This doesn't make it right, any extended outage is not ideal, but I just wanted to fact check the 12 hours claim which is double the downtime that occurred. As Charles said, it is very unusual for us to experience this, so we are incredibly frustrated. Our uptime for 2022 was 100%, and so far this year including this event, it's 99.68% so it really is a very rare occurrence. It doesn't mean we're being complacent, but it illustrates that this isn't the usual experience.

What Randy said.

Pre-checking isn't really how email works. We are however adding bounce management tools to our cloud platform to help prevent multiple bounces and to manage blocked emails.

@Matt Finger did all the hard work (JS, node, React, etc). I got the easier jobs.

We plan on bringing more video platforms to Live Topics, but as of its first release, Zoom is not directly embeddable. You can do an unlisted Youtube Live video too if you wished.

I can actually reproduce, I think it's a Cloudflare issue. We rely on the new Image() javascript method to tell us if the image is valid or not. It appears in this case, Chrome is reporting that those links are valid images, while Safari is not. I'll do some digging but it might be beyond our ability to fix if Cloudflare is manipulating the response.

I really can’t reproduce it on any browser. The link shouldn’t attempt to embed as it’s not a whitelisted URL.

Do you have any chrome plugins that may affect the editor?

Should be fixed now, thanks.

I cannot reproduce this issue, can you record a video so we can see what is happening please?

Yes, then we'll remove it and put it back, then remove it again then put it back. It's now a tradition.

We expect this limitation to be removed in our April release. We have merged two different concepts into one. We previously had "Publish Date" in pages, but "Future Publish Date" everywhere else. Merging them did cause some issues which we've been resolving. The final one was when you have Pages records (any publish date) synchronised with a forum (only future publish date).