Title: Peter Nowee's Replies | WordPress.org

---

# Peter Nowee

  [  ](https://wordpress.org/support/users/now77/)

 *   [Profile](https://wordpress.org/support/users/now77/)
 *   [Topics Started](https://wordpress.org/support/users/now77/topics/)
 *   [Replies Created](https://wordpress.org/support/users/now77/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/now77/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/now77/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/now77/engagements/)
 *   [Favorites](https://wordpress.org/support/users/now77/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] update](https://wordpress.org/support/topic/update-172/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/update-172/#post-6207537)
 * Not sure why it has not been released yet, but you could try the latest development
   master from GitHub (commit `cc624b5387`). [https://github.com/nodecode/wp-minify-fix](https://github.com/nodecode/wp-minify-fix)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] PHP Error log](https://wordpress.org/support/topic/php-error-log-7/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/php-error-log-7/#post-5746674)
 * I’m not seeing these errors anymore with the latest development master from GitHub(
   commit `cc624b5387`). [https://github.com/nodecode/wp-minify-fix](https://github.com/nodecode/wp-minify-fix)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] wp_enqueue_script in_footer ignored / Broken Menu button Jetpack Mobile Theme](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/)
 *  Thread Starter [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/#post-5590123)
 * Just to confirm, the problems with `wpgroho.js` (Jetpack’s Gravatar Hovercards
   module) and `sharing.js` (Jetpack’s Sharing module) still exist with the latest
   development master from GitHub (commit `cc624b5387`).
 * Only the script error for Jetpack Sharing has changed, but that is probably due
   to changes in that plugin:
    `TypeError: WPCOMSharing is undefined`
 * I will continue excluding these two files from minification.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] wp_enqueue_script in_footer ignored / Broken Menu button Jetpack Mobile Theme](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/)
 *  Thread Starter [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/#post-5590100)
 * Wow, great, that sure looks like a big step in the right direction. Doesn’t completely
   work for me yet, though. Here are my test results:
    - For `wpgroho.js` (Jetpack’s Gravatar Hovercards module) and `sharing.js` (
      Jetpack’s Sharing module), their variables (`WPGroHo` and `sharing_js_options`)
      are normally set _just_ before loading the javascript file:
    - Without minification:
    -     ```
          </footer>
          ...
          <script type='text/javascript'>/*  */
          var WPGroHo = {"my_hash":""};
          /*  */</script> <script type='text/javascript' src='http://localhost/example/wp-content/plugins/jetpack/modules/wpgroho.js?ver=4.1'></script>
          ...
          <script type='text/javascript'>/*  */
          var sharing_js_options = {"lang":"en","counts":"1"};
          /*  */</script> <script type='text/javascript' src='http://localhost/example/wp-content/plugins/jetpack/modules/sharedaddy/sharing.js?ver=20140920'></script>
          ...
          </body>
          ```
      
    - With minification, the minified script files are loaded after the `</footer
      >`-tag, but still before the variables are set:
    -     ```
          </footer><script type="text/javascript" src="http://localhost/example/wp-content/plugins/wp-minify-fix/min/?f=wp-includes/js/jquery/jquery.js,wp-includes/js/jquery/jquery-migrate.min.js&b=example&m=1000000000"></script><script type='text/javascript' src='http://localhost/example/wp-content/plugins/wp-minify-fix/min/?f=wp-content/plugins/akismet/_inc/form.js,wp-content/plugins/contact-form-7/includes/js/jquery.form.min.js,wp-content/plugins/contact-form-7/includes/js/scripts.js,wp-content/plugins/jetpack/modules/wpgroho.js,wp-content/plugins/jetpack/modules/minileven/theme/pub/minileven/js/small-menu.js,wp-includes/js/comment-reply.min.js,wp-content/plugins/jetpack/modules/sharedaddy/sharing.js&b=example&m=1234567890'></script>
          ...
          <script type='text/javascript'>/*  */
          var WPGroHo = {"my_hash":""};
          /*  */</script>
          ...
          <script type='text/javascript'>/*  */
          var sharing_js_options = {"lang":"en","counts":"1"};
          /*  */</script>
          </body>
          ```
      
    - This results in the same script errors as before:
       `ReferenceError: WPGroHo
      is not defined` If `wpgroho.js` is excluded: `ReferenceError: sharing_js_options
      is not defined`
    - `small-menu.js` (Jetpack’s Mobile Theme, containing code for the menu button
      for Twenty Eleven) now works, provided it is not minified together with `wpgroho.
      js`, which normally precedes `small-menu.js`. Because of the error `wpgroho.
      js` throws (see above), the code from `small-menu.js` does not get executed,
      resulting in a non-responsive menu button after all.
 * Perhaps load the minified scripts even further down the page, not just below `
   </footer>`, but all the way down, just above `</body>`?
 * Just let me know if you need more information.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] wp_enqueue_script in_footer ignored / Broken Menu button Jetpack Mobile Theme](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/)
 *  Thread Starter [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/#post-5590012)
 * That would be nice. Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Minify Fix] wp_enqueue_script in_footer ignored / Broken Menu button Jetpack Mobile Theme](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/)
 *  Thread Starter [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/wp_enqueue_script-in_footer-ignored-broken-menu-button-jetpack-mobile-theme/#post-5589853)
 * I was afraid you were going to say something like this 🙂
 * I don’t want to put everything in the footer, because I read that might cause
   problems when things are depending on scripts loaded at the top of the page.
 * By the way, Jetpack’s Gravatar Hovercards also doesn’t work with WP Minify Fix
   for the same reason: `gravatar-hovercards.php` uses `wp_localize_script()` to
   place a piece of javascript on the page that sets a variable `WPGroHo`. That 
   piece of script is placed in the footer. Normally, it would be followed by the
   loading of `wpgroho.js`, which is enqueued with `$in_footer=true` and needs `
   WPGroHo`. When using WP Minify Fix, `wpgroho.js` is minified at the top, but `
   wp_localize_script()` still puts the script setting the variable `WPGroHo` at
   the bottom. Result: `wpgroho.js` runs before `WPGroHo` is set, gives an error(`
   ReferenceError: WPGroHo is not defined`) and all the following scripts that it
   was combined and minified with are also not executed anymore. In this case, I
   solved it by excluding `wp-content/plugins/jetpack/modules/wpgroho.js` from minify.
 * A similar problem seems to be going on with Jetpack’s Sharing module. It uses`
   wp_localize_script()` to set a variable named `sharing_js_options`. This variable
   is needed by the script `sharing.js`. Although I don’t see it enqueued with `
   $in_footer=true`, the setting of the variable and the script are normally placed
   in the footer. With WP Minify Fix active, `sharing.js` is moved to the head, 
   while the setting of `sharing_js_options` stays in the footer, again resulting
   in an error. I solved this as well by excluding `wp-content/plugins/jetpack/modules/
   sharedaddy/sharing.js` from minify.
 * I can imagine that in certain scenario’s WP Minify Fix’s current behavior is 
   a feature, not a bug, but for me it is giving me a lot of trouble right now.
 * Thanks anyway for an otherwise great plugin,
    Peter
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[Twenty Eleven] Missing author and updated – Google Structured Data Testing Tool](https://wordpress.org/support/topic/missing-author-and-updated-google-structured-data-testing-tool/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/missing-author-and-updated-google-structured-data-testing-tool/#post-5447199)
 * To resolve the missing:updated error, follow [this guide by Daniel Marquard](https://netidy.com/blog/warning-missing-required-field-updated-wordpress).
 * See also: [https://wordpress.org/support/topic/twenty-eleven-warning-missing-required-field-updated](https://wordpress.org/support/topic/twenty-eleven-warning-missing-required-field-updated)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Use Google Libraries] Possible conflict with Jetpack Custom CSS CodeMirror editor](https://wordpress.org/support/topic/possible-conflict-with-jetpack-custom-css-codemirror-editor/)
 *  Thread Starter [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/possible-conflict-with-jetpack-custom-css-codemirror-editor/#post-5567539)
 * Thanks for the quick reply. I’m posting here only the differences between loading
   from my remote webserver and loading from my local MAMP copy:
 * **Net**
    Webserver (Edit CSS CodeMirror editor not showing)
 *     ```
       GET http://www.example.com/example/wp-includes/js/jquery/jquery.js [HTTP/1.1 200 OK 163ms]
       GET http://www.example.com/example/seriousceliac/wp-includes/js/jquery/ui/jquery.ui.core.min.js [HTTP/1.1 200 OK 156ms]
       ```
   
 * (And yes, this is with the Use Google Libraries plugin enabled.)
 * Local MAMP (Edit CSS CodeMirror editor showing)
 *     ```
       GET http://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js [HTTP/1.1 200 OK 100ms]
       GET http://ajax.googleapis.com/ajax/libs/jqueryui/1.10.4/jquery-ui.min.js [HTTP/1.1 200 OK 208ms]
       ```
   
 * **CSS**
    A lot of the same warnings when loading from both webserver and local
   MAMP. Only difference is the order in which they are shown.
 * **JS**
    Two identical warnings when loading from webserver or local MAMP. One
   additional warning on webserver (editor not showing): `TypeError: a(...).sortable
   is not a function postbox.min.js:1`
 * **Security**
    Empty in both.
 * Let me know if you need the detailed reports anyway and I will send them to you
   by email.
 * Thanks,
    Peter
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[mqTranslate] Pre-Path mode Hide URL language information](https://wordpress.org/support/topic/pre-path-mode-hide-url-language-information/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/pre-path-mode-hide-url-language-information/#post-4892689)
 * Yes, it works now, thanks!!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [plugin: jetpackt](https://wordpress.org/support/topic/plugin-jetpackt/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/plugin-jetpackt/#post-4951480)
 * You might try to make this change in plugins/jetpack/modules/modules.php
 * [https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f](https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f)
 * It’s a bug that should be resolved in a next update of the Jetpack plugin.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] Jetpack related post not working](https://wordpress.org/support/topic/jetpack-related-post-not-working/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/jetpack-related-post-not-working/#post-4954542)
 * You might try to make this change in plugins/jetpack/modules/modules.php
 * [https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f](https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f)
 * It’s a bug that will be resolved in a next update anyway.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] Related Posts](https://wordpress.org/support/topic/related-posts-25/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/related-posts-25/#post-4947496)
 * You might try to make this change in plugins/jetpack/modules/modules.php
 * [https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f](https://github.com/Automattic/jetpack/commit/78a0d5e5cd05cbda233f3e192b6c700db3c6371f)
 * It’s a bug that will be resolved in a next update anyway.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[mqTranslate] Pre-Path mode Hide URL language information](https://wordpress.org/support/topic/pre-path-mode-hide-url-language-information/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/pre-path-mode-hide-url-language-information/#post-4892662)
 * Same problem here. My site also uses Pre-Path Mode and the default language is
   English.
 *     ```
       [hide_default_language] =>
       [url_mode] => 2
       ```
   
 * [http://www.peternowee.com/seriousceliac/en/](http://www.peternowee.com/seriousceliac/en/)
   Works
    [http://www.peternowee.com/seriousceliac/](http://www.peternowee.com/seriousceliac/)
   Page not found [http://www.peternowee.com/seriousceliac/fr/](http://www.peternowee.com/seriousceliac/fr/)
   Works [http://www.peternowee.com/seriousceliac/de/](http://www.peternowee.com/seriousceliac/de/)
   Works etc.
 *     ```
       [hide_default_language] => 1
       [url_mode] => 2
       ```
   
 * [http://www.peternowee.com/seriousceliac/en/](http://www.peternowee.com/seriousceliac/en/)
   Page not found
    [http://www.peternowee.com/seriousceliac/](http://www.peternowee.com/seriousceliac/)
   Works [http://www.peternowee.com/seriousceliac/fr/](http://www.peternowee.com/seriousceliac/fr/)
   Works [http://www.peternowee.com/seriousceliac/de/](http://www.peternowee.com/seriousceliac/de/)
   Works
 * IIRC, everything was working ok under qTranslate. Hope chsxf can find the time
   to wade through so many support requests. Anyway, thanks for continuing the work
   on this great plugin!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[mqTranslate] Unnecessary inline CSS](https://wordpress.org/support/topic/unnecessary-inline-css/)
 *  [Peter Nowee](https://wordpress.org/support/users/now77/)
 * (@now77)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/unnecessary-inline-css/#post-4941818)
 * I agree.
 * I’m coming from an old version of qTranslate, where I used to override the locations
   of the flag images in a custom CSS stylesheet, pointing instead to a combined
   sprite image (to speed up page loading).
 * Because inline CSS overrides everything, it now seems quite impossible to override
   the flag image locations.

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