Stats module of Jetpack causing core dump file

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 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

I think this patch should be applied to the next release of Jetpack.

We’ll run some more tests to make sure the patch doesn’t break anything, but we’re indeed planning on including the patch in the next major Jetpack release.

I don’t get why one installation will print [audio:file.mp3] as simple plain text and another one will strip that code away.

Do both installations run the same version of WordPress, and the same plugins?

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

Jetpack isn’t at play here, though. As you mentioned earlier:

I tried to deactivate all the plugins I run but that code is still being stripped from the front-end.

WordPress itself manages the rendering of shortcodes on your site.

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

Emanuele

Since you don’t use any plugins that can interpret this shortcode format, I think it’d be best to find and replace each instance of the shortcode by the current audio shortcode format. You’ll get all your audio players back, all using the built-in WordPress audio player, and you won’t experience any issues with Jetpack or another plugin.

Let me know how it goes.

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

So, only the bad formatted audio tag is being stripped.

I’d argue that the correct behaviour would be to strip the audio tag from the frontend, since it doesn’t provide any information to your readers. It would be nice if all shortcodes were stripped though, not just the audio ones.

It might be worth opening a Core Trac ticket to report this issue with WordPress, and have a similar implementation for all wrongly formatted shortcodes:
https://core.trac.www.ads-software.com/

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