MEJS Media Error

Support
#1

Hi there! getting the following errors on one of our sites with a video background. If I’m logged in, it works fine, but viewing as a regular visitor throws the error. Got the errors pasted below. I’ve tried flushing the cache and permalinks, removing and re-adding the video. This is a locally hosted video, not youtube or vimeo. I believe it was working prior to last update. Any other info I can give you to help troubleshoot? It is falling back to the poster, at least. Happy to get you a temp login if it’s helpful.

cs-classic.7.8.8.js?rnd=86733:1 MEJS media error. TypeError: Cannot read properties of null (reading 'indexOf')
    at s (mediaelement-and-player.min.js?rnd=86733:12:13580)
    at new e (mediaelement-and-player.min.js?rnd=86733:12:14611)
    at r.value (mediaelement-and-player.min.js?rnd=86733:12:81110)
    at MediaElementPlayer.init (mediaelement-migrate.min.js?rnd=86733:1:495)
    at new r (mediaelement-and-player.min.js?rnd=86733:12:76776)
    at HTMLVideoElement.<anonymous> (mediaelement-and-player.min.js?rnd=86733:12:112139)
    at ce.each (jquery.min.js?rnd=86733:2:3129)
    at e.<computed>.each (jquery.min.js?rnd=86733:2:1594)
    at o.fn.mediaelementplayer (mediaelement-and-player.min.js?rnd=86733:12:112089)
    at cs-classic.7.8.8.js?rnd=86733:1:94078
c @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
Oe @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
Bo @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1


cs-classic.7.8.8.js?rnd=86733:1 Failed to attach handler to element div.x-video.player.bg.transparent.hide-controls.autoplay.loop.muted.playsinline.poster (t,{poster:e,options:n={}})=>{let o=ct(t,"bg")||ct(t,"x-video-bg"),r=ct(t,"vimeo")||ct(t,"youtube"),i=t.getAttribute("data-x-video-options")||n;i=typeof i=="string"?Ci(i):i||{};let s=[];if(o&&(e&&(eu… {poster: 'https://[REDACTED FOR THIS BUG REPORT]/files/2025/12/[REDACTED].png'} TypeError: l.stopPropagation is not a function
    at c (cs-classic.7.8.8.js?rnd=86733:1:93533)
    at cs-classic.7.8.8.js?rnd=86733:1:94109
    at Oe (cs-classic.7.8.8.js?rnd=86733:1:36109)
    at cs-classic.7.8.8.js?rnd=86733:1:35897
    at Array.forEach (<anonymous>)
    at cs-classic.7.8.8.js?rnd=86733:1:35885
    at Array.forEach (<anonymous>)
    at Bo (cs-classic.7.8.8.js?rnd=86733:1:35832)
    at HTMLDocument.<anonymous> (cs-classic.7.8.8.js?rnd=86733:1:36565)
Oe @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
Bo @ cs-classic.7.8.8.js?rnd=86733:1
(anonymous) @ cs-classic.7.8.8.js?rnd=86733:1
#2

Hello @GL_creative,

Thanks for posting in! Your video may not be accessible to online users. Make sure that the video is cross-browser compatible as well. We would be happy to double check your site if we can log in. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

image

Best Regards.

#3

In theory it is accessible and compatible, since I did extensive browser testing before we went live. It’s only recently that it stopped loading and stuck to the cover image fallback. I checked it out in safari and chrome across various devices (the two most likely visitor browser choices). When I’m logged in? It’s all good. Not logged in, throws errors. Can’t think of any changes to file management that could cause it. But please look around and let me know what you find!

#4

Hey @GL_creative,

It seems the 3rd-party Breeze plugin is causing the issue.

image
image714×322 18.9 KB

I temporarily deactivated the plugin and viewed the site in private browsing mode. The issue is gone, and the video is playing on my end.

image
image832×469 89.8 KB

Please do check in your browser using Incognito mode (private browsing).

#5

Oh how frustrating! You’re absolutely right. Breeze has been up to some shenanigans lately, bit worried they’re vibe coding it now…

Edit: More specifically, it looks like the video lazy load feature was responsible for the errors. Looks like they last touched the lazy load functionality in 2.5.1 (which was recent I believe, they don’t date stamp releases) and probably broke it then fixing another issue.

So sorry to drag you into this, when it threw out the script-specific errors and clearing the cache repeatedly didn’t work, I thought for sure it was theme-related! Thanks for being an extra set of eyes on this.

Appreciate the team and everything you do!

#6

No worries, @GL_creative.