Emanuele

Hello @muffinpeace thanks for your support! Actually I have seen the statistics are slowing coming back to the usual values during the last two days. If you noticed, there is an 8 days time span where the visits have been lost by WPStats (but noted by Matomo): that’s from May 3 to – I would say – May 11.
I know the results are not real-time but the installation is not new. I am using the stats plugin since July 2007.

@bruceallen thanks for your reply. Am I wrong or in that case I would still be able to see the stats from my wordpress.com dashboard? I see 0 visits from that dashboard too.

No, I didn’t. I had to leave active the option to select the srt using the drop-down menu.

It seems like that mediaelement does support startLanguage as attribute (https://github.com/mediaelement/mediaelement/blob/master/docs/api.md) but WordPress does not support it.

Thank you Bennett. The newer version fixes the issue and works like a charm.

Emanuele

Thanks for your support. Earlier version support would be appreciated since a lot of people have no control on PHP version install. I have already opened a ticket with my hosting provider but I don’t think they will solve in a day or two. Actually my solution was to delete the plugin, but obviously, I would like to keep using it (without removing it from auto-update list).
Thanks,
Emanuele

Same issue here. No way to make it work the last release. Support for older PHP versions would be appreciated.

I just opened a ticket as you suggested. You can find it here: https://core.trac.www.ads-software.com/ticket/36775
Let’s see how it will evolve.
Thanks anyway for your great support until now!
Emanuele

Yes yes yes. I already did this, and I already fixed the player everywhere in my blog. I was simply going on just to discover the root cause, even if it doesn’t have impact on my site anymore.

WordPress, since 3.6, introduced the audio tag. It should be used like it:
[audio src="file.mp3"]
My old & wrong code was formatted like this:
[audio:file.mp3]
Now I tried to use this non-existent shortcode:
[unuseful:file.mp3]
And the existent video one badly implemented:
[video:file.mp3]
Both are rendered as plain text on the front end. So, only the bad formatted audio tag is being stripped.

The funny thing is that I can’t actually type sentences like [audio is very loud] because are being stripped off.

Jetpack is not crashing anymore but that’s not the end…

Emanuele

Yes, I got it. Reporting it here was just a way to record the issue until its final resolution.

Emanuele

They are not running the same plugins but for sure the same WordPress version. I tried to deactivate all the plugins but that code was stripped off.
Using Notepad++, I have looked for into every file of my template but no strip_shortcode is present.
Then I looked for into the plugin folder the following regular expression strip_shortcodes|remove_all_shortcodes|remove_shortcode and these functions are used only by Jetpack within these files:

jetpack\class.media-extractor.php (1 hit)
jetpack\class.media-summary.php (1 hit)
jetpack\functions.opengraph.php (2 hits)
jetpack\json-endpoints\class.wpcom-json-api-post-endpoint.php (1 hit)
jetpack\json-endpoints\class.wpcom-json-api-post-v1-1-endpoint.php (1 hit)
jetpack\modules\contact-form\grunion-contact-form.php (1 hit)
jetpack\modules\custom-post-types\portfolios.php (1 hit)
jetpack\modules\minileven\theme\pub\minileven\inc\tweaks.php (1 hit)
jetpack\modules\related-posts\jetpack-related-posts.php (4 hits)
jetpack\modules\sharedaddy\sharing-sources.php (1 hit)
jetpack\modules\shortcodes\recipe.php (1 hit)

Emanuele

I tried to deactivate all the plugins I run but that code is still being stripped from the front-end. That’s funny. I uploaded via FTP all WordPress core files. I don’t get why one installation will print [audio:file.mp3] as simple plain text and another one will strip that code away.
Maybe the theme using strip_shortcode function?

Emanuele

There is nothing left in Jetpack that interacts with the Audio shortcode, so I’m not sure what else could be stripping the code at this point. Could you try to deactivate Jetpack, and see if the shortcodes get stripped?

Ok, I tested it and I can confirm that even with Jetpack deactivated that code is being stripped. I will have to deactivate selectively the plugins I am running to discover which one is doing that.

For sure, this test version of Jetpack solved the issue related to the crash. I am not using that code anymore in my blog but I think this patch should be applied to the next release of Jetpack.

Emanuele

I am already using the new shortcode format. I am still here just for the sake of clarity. I am curious to discover the reasons of this bug. I don’t think is WordPress core to be stripping that code because in other 2 blogs I own, that text is printed as plain text and I think it has happened during your tests too.
What does this Jetpack version do differently from the official one?

Emanuele

I am using your version and, this way, WordPress doesn’t crash but the code disappear (is not shown as plain text).

If, I insert this code on the text editor (not the WYSIWYG one)
<p align="center">[audio:file.mp3]</p>
I will have (on HTML code):
<p align="center"></p>
As if the audio tag is stripped off.

Emanuele