3 minutes ago, Como said:

Heads-up: the PWA videos do not load. Tested in Edge, Firefox and Chrome.

And, since I just noticed this, a bug in the above highlight-quote. The link is not preserved.

Im not sure which videos you are looking at there, but all videos load here with no issues

15 minutes ago, Marc said:

Im not sure which videos you are looking at there, but all videos load here with no issues

I just took a closer look. In Firefox, it reports no suitable mime type. I don't have an unusual system here - and I experience no problems with videos elsewhere - except, I am using a Win 10 machine. I don't know if that is relevant and helps.

Edited July 31, 2025Jul 31 by Como

Unfortunately I'm not really sure what to tell you there. I can play all videos no problem at all. It appears to be an issue on your end there

Just now, Marc said:

Unfortunately I'm not really sure what to tell you there. I can play all videos no problem at all. It appears to be an issue on your end there

I guess so. I have no idea why though. What type of videos are they? I'll test it out if I can to confirm.

They are mp4 (apart from the top one which is a youtube embed)

@Marc Those video's don't work intergraded in your website either. When pressing play nothing shows up.


However directly going to the source chrome just plays it ok.
https://media.invisioncic.com/a319035/monthly_2025_07/Badges.mp4.71507939b9602bbb87c7c10c5942028a.mp4

Appears to be an issue only on firefox. I will get that reported internally

15 minutes ago, Marc said:

Appears to be an issue only on firefox. I will get that reported internally

The problem appears across browsers for me. And videos displayed for me at an MP4 test.

https://www.tekeye.uk/html/html5-video-test-page

1 hour ago, Moestuin said:

@Marc Those video's don't work intergraded in your website either. When pressing play nothing shows up.

However directly going to the source chrome just plays it ok.
https://media.invisioncic.com/a319035/monthly_2025_07/Badges.mp4.71507939b9602bbb87c7c10c5942028a.mp4

Confirmed - this worked for me too using Firefox.

Edited July 31, 2025Jul 31 by Como

51 minutes ago, Marc said:

Appears to be an issue only on firefox.

I am using Chrome.

Beta 4 is on its way!

There is only one tiny change and that is to fix the issue with PWA splash screens. After upgrading, head into your AdminCP and re-upload a new splash screen image (ACP > Settings > Web App). Then delete any installed PWA on your phone, then re-add it.

On 7/24/2025 at 4:25 PM, Matt said:

We have a lot going on, including a website refresh and documentation which is all in progress.

Why not see if knowledgable community members can assist with the documentation, then have a staff member review it before updating?

There's always willing helpers within a community, that would assist in those areas where time is restrained for those who take on more time consuming tasks. I am sure there's capable people who can at least take some of the strain off you guys, the amount of things you do will always leave some areas difficult to update.

---

Eagrly awaiting the release of 5.0.10. 😁

On my test install with the beta 4, i see the following in javascript console.

<meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes">

On my 5.0.9 site i don't have that.

Edit: Did also something change in javascript parsing? If you have a custom javascript. That contains: =>
Then the javascript that is used will become =&gt; so it gives an error in the javascript console. And custom javascripts don't work. This does however not happen on all the =>

Edited August 1, 2025Aug 1 by Moestuin

7 minutes ago, Moestuin said:

On my test install with the beta 4, i see the following in javascript console.

<meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes">

On my 5.0.9 site i don't have that.

Edit: Did also something change in javascript parsing? If you have a custom javascript. That contains: =>
Then the javascript that is used will become =&gt; so it gives an error in the javascript console. And custom javascripts don't work.

=> still works on my end. I can confirm the JS console error though.

It happens on on this first line with =>, however not on the second line.

const observer = new MutationObserver((mutations) => {
  mutations.forEach(mutation => {

In chrome console.

Edited August 1, 2025Aug 1 by Moestuin

I just got on my non IN_DEV site the message to update to the Beta 4. Seems wrong to me :)

The changes are from 5.0.9.

Edited August 1, 2025Aug 1 by Hatsu

1 hour ago, Hatsu said:

I just got on my non IN_DEV site the message to update to the Beta 4. Seems wrong to me :)

The changes are from 5.0.9.

Fixed.

I have never seen a beta version suggestion (Upgrade suggestion) on my board before....

I got the popup upgrade to beta 4 too (On my 5.0.9)....

Version 5.0.10 Beta 4 of Invision Community is now available. You can upgrade your community now from your AdminCP.

Here's what's new in this version:

Edited August 1, 2025Aug 1 by media

14 hours ago, Moestuin said:

On my test install with the beta 4, i see the following in javascript console.

<meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes">

After some testing, I believe the Apple meta tag is required for PWA splash screens to work. Yes, it’s a deprecated tag but one which Safari still requires unfortunately. Ironically, the “mobile-web-app-capable” tag which they recommend is redundant in modern browsers (they use the manifest file instead).

What I can do is only include the Apple meta tag when a splash screen image has been uploaded. That’ll prevent the console error in some situations 👍

So this beta version showing on my live board is legit upgrade or NOT??????

Fixed in 5.0.10? It's been around for a while, this is the second time reported.

Thanks

Thanks @Ehren , what about tje JS error?
Perhaps related to: #5051: Fix an issue where custom JS defined in the ACP was not being parsed

If you want i can PM the entire javascript sample.

40 minutes ago, Square Wheels said:

Fixed in 5.0.10? It's been around for a while, this is the second time reported.

Thanks

Yes. According to our Github, it was fixed by Esther in 5.0.10

21 minutes ago, Moestuin said:

If you want i can PM the entire javascript sample.

Sure, go ahead 👍

I've not yet tried Beta 4 but I tested Beta 3 and noticed Javascript in AdminCP Theme Settings was still appearing in the page source even when PHP tags wrapped around it were set not to show it (depending upon a theme setting value). This may have been under PHP not being processed rather than JS not being processed though.

I hope they don't release 5.0.10 until the issue preventing theme resource images from showing in the CSS is fixed, as it was still waiting on a fix in beta 3.

I have just upgraded to beta 4 and these 2 bugs are still present:

the CSS one:

and the JS one seems to be partially fixed after coming out of the Enable Theme Designer Mode with the theme setting disabled, the script dissapeared.

but if I toggle the setting back on in the front end theme settings, the Javascript code doesn't come back.

Edited August 4, 2025Aug 4 by The Old Man
Corrected

3 minutes ago, The Old Man said:

I have just upgraded to beta 4 and these 2 bugs are still present:

the CSS one:

and the JS one:

the theme setting is switched off, but the script still shows in the page source

<!-- Theme javascript -->
<script>
    

//  Make sure the DOM is ready first ;)document.addEventListener('DOMContentLoaded', (event) => {
    
// console.log('DOM is ready!.')

// Check if IntersectionObserver supported    if ('IntersectionObserver' in window) {
  
// Remove the transition classconst inv_scroll_top = document.querySelector('.inv_scroll_top.inv_scroll_top_icon');
    inv_scroll_top.classList.add('inv-hidden');
    inv_scroll_top.classList.remove('inv-visible');


etc

</script>

Do you have a link for the bug reports for these so I can take a look and see whats happening?