Title: Plugin not reacting
Last modified: October 13, 2022

---

# Plugin not reacting

 *  [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/)
 * (@jmgarciabonilla)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/plugin-not-reacting/)
 * Hi Michael,
 * First of all, let me say how thankful I am for your plugin. It’s been brilliant,
   you developed a clever thing, I must admit this.
 * A couple of days ago I uploaded a .DOCX no problem at all. Today, I wanted to
   upload another one and the plugin would not react when I click on the ‘Choose
   document’ button. I tried the following:
    – Clear the cache of my browser – Clear
   the cache of the website – Used Safari instead of Chrome – Then changed to another
   website I mange (same issue) – Went to the staging of my main website same issue–
   Disabled all the plugins in the staging, same issue.
 * Then I checked the inspect element and in the console, there was a warning about
   a file not being able to load.
 * `DevTools failed to load source map: Could not load content for https://staging-
   mejorbanco.kinsta.cloud/wp-content/plugins/mammoth-docx-converter/underscore-
   umd.js.map: HTTP error: status code 500, net::ERR_HTTP_RESPONSE_CODE_FAILURE`
 * I’ve created a screen recording so hopefully you can see the issue, in case my
   explanation is not clear. Here the link to the G. Drive video: [https://drive.google.com/open?id=1gsreYMNLy5Sd0Fkq2d263Wo828dOz7ik&authuser=jmgarciabonilla%40gmail.com&usp=drive_fs](https://drive.google.com/open?id=1gsreYMNLy5Sd0Fkq2d263Wo828dOz7ik&authuser=jmgarciabonilla%40gmail.com&usp=drive_fs)
 * I use Kinsta as my server, also asked them if it’s something at their end – so
   far they haven’t find an issue on their side.
 * Please do let me know if you need any other information.
 * Cheers,
    Josep
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-not-reacting%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/)
 * (@jmgarciabonilla)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/plugin-not-reacting/#post-16096878)
 * Hi MIchael,
 * It’s me again 🙂
 * Checked with the support team at Kinsta, I was hoping the issue was a silly thing
   on tjeir end, and they told me this.
 * >     ```
   >     Looks like this is the issue. A fatal error is occuring due to a call to an undefined function named get_field(). It looks like Mammoth is making this call.
   >     2022/10/13 15:58:52 [error] 62836#62836: *569 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined function get_field() in /www/mejorbanco_853/public/wp-content/themes/mejorbanco/header.php:17
   >     Stack trace:
   >     #0 /www/mejorbanco_853/public/wp-includes/template.php(770): require_once()
   >     #1 /www/mejorbanco_853/public/wp-includes/template.php(716): load_template('/www/mejorbanco...', true, Array)
   >     #2 /www/mejorbanco_853/public/wp-includes/general-template.php(48): locate_template(Array, true, true, Array)
   >     #3 /www/mejorbanco_853/public/wp-content/themes/mejorbanco/404.php(10): get_header()
   >     #4 /www/mejorbanco_853/public/wp-includes/template-loader.php(106): include('/www/mejorbanco...')
   >     #5 /www/mejorbanco_853/public/wp-blog-header.php(19): require_once('/www/mejorbanco...')
   >     #6 /www/mejorbanco_853/public/index.php(17): require('/www/mejorbanco...')
   >     #7 {main}
   >     thrown in /www/mejorbanco_853/public/wp-content/themes/mejorbanco/header.php on line 17" while reading response header from upstream, client: 68.116.174.247, server: staging-mejorbanco.kinsta.cloud, request: "GET /wp-content/plugins/mammoth-docx-converter/underscore-umd.js.map HTTP/1.1", upstream: "fastcgi://unix:/var/run/php8.0-fpm-mejorbanco.sock:", host: "staging-mejorbanco.kinsta.cloud:61513"
   >     ```
   > 
 * Not sure if this offers you any clue into what is off here.
 * Thanks a lot,
    josep
 *  Plugin Author [Michael Williamson](https://wordpress.org/support/users/michaelwilliamson/)
 * (@michaelwilliamson)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/plugin-not-reacting/#post-16096952)
 * 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

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin not reacting’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/mammoth-docx-converter.svg)
 * [Mammoth .docx converter](https://wordpress.org/plugins/mammoth-docx-converter/)
 * [Support Threads](https://wordpress.org/support/plugin/mammoth-docx-converter/)
 * [Active Topics](https://wordpress.org/support/plugin/mammoth-docx-converter/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mammoth-docx-converter/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mammoth-docx-converter/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Michael Williamson](https://wordpress.org/support/users/michaelwilliamson/)
 * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/plugin-not-reacting/#post-16096952)
 * Status: not resolved