Michael Williamson

I can’t say I’m familiar with Wordfence, but I haven’t received any reports of the plugin not working on the latest version of WordPress. So far as I know, it continues to work, so I haven’t spent any time on it.

Is the plugin not working on WordPress 6.9? If not, could you provide reproduction steps and a description of what’s not working?

When editing a post, there should be a meta box titled “Mammoth .docx converter”. If the meta box isn’t visible, you might need to select in the “Screen Options” for a post.

From the meta box, you can select a docx file to upload and then insert into the post.

I’m afraid the answer is no again!

Ah, I see. The images haven’t yet been uploaded to the server, so the raw HTML preview shows a placeholder path. Once the document is imported, the images will be uploaded, and the paths to the images will be updated accordingly.

I can’t check against an actual WordPress installation right now, but I can’t seem to find any reference in the WordPress docs for core/editor being removed or deprecated. For instance,

• https://developer.ww.wp.xz.cn/block-editor/reference-guides/data/data-core-editor/: insertBlocks is still referenced, and not mentioned as deprecated
• https://developer.ww.wp.xz.cn/block-editor/contributors/code/deprecations/: core/editor is not mentioned in the list of deprecations (at least, that I could see)

I only had time to do a very quick search, so it’s entirely possible I’ve missed something. Do you have a reference for the deprecation?

Mammoth only runs on the initial import of the Word document. If you change the Word document, those changes won’t be reflected in the WordPress post until you upload the Word document again.

Hello Josep,

Looking at the first link of your error:

PHP Fatal error: Uncaught Error: Call to undefined function get_field() in /www/mejorbanco_853/public/wp-content/themes/mejorbanco/header.php:17

it seems as if the problem is in your theme, rather than in Mammoth. I don’t think the Mammoth PHP code ever (directly) calls get_field.

Having said that, I wouldn’t expect a failure to load a source map to cause the problem you’re seeing (but I’m often wrong!).

However, I’m still not sure that the problem is with Mammoth. Mammoth just uses an ordinary file input, and the JavaScript only adds a change listener, so it shouldn’t affect the appearance of a dialog to select a file. My suspicion would be that something else in your theme or other plugins is causing the click to be intercepted and cancelled.

Michael