Title: Darren Ethier (nerrad)'s Replies | WordPress.org

---

# Darren Ethier (nerrad)

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

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

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 581 total)

1 [2](https://wordpress.org/support/users/nerrad/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/nerrad/replies/page/3/?output_format=md)…
[37](https://wordpress.org/support/users/nerrad/replies/page/37/?output_format=md)
[38](https://wordpress.org/support/users/nerrad/replies/page/38/?output_format=md)
[39](https://wordpress.org/support/users/nerrad/replies/page/39/?output_format=md)
[→](https://wordpress.org/support/users/nerrad/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] [BUG] WooCommerce 10.6.1 – Analytics Dashboard Crash: “tz is not a function”](https://wordpress.org/support/topic/bug-woocommerce-10-6-1-analytics-dashboard-crash-tz-is-not-a-function/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 month, 1 week ago](https://wordpress.org/support/topic/bug-woocommerce-10-6-1-analytics-dashboard-crash-tz-is-not-a-function/#post-18871866)
 * I did some digging [@emacencini](https://wordpress.org/support/users/emacencini/)
   and I’m convinced this is due to a plugin conflict (potentially the one that 
   [@shahzeenfarooq](https://wordpress.org/support/users/shahzeenfarooq/) discovered).
   Here’s a few more details to highlight why I think this:
 * There **is** [a PR that was introduced in the 10.6.0 release](https://github.com/woocommerce/woocommerce/pull/62872/changes)(
   which would also be in 10.6.1 in your case) which fixed a bug with timezone not
   being detected correctly. The fix is a good one, but one nuance is that in fixing
   the bug, it exapanded the conditions under which `moment().tz()` is called which
   in surfaced a latent plugin conflict. Prior to 10.6.0 this plugin conflict wouldn’t
   have surfaced because of the timezone detection bug.
 * The `.tz()` method comes from the `moment-timezone` script, not base `moment`,
   which WooCommerce bundles in it’s scripts –`moment` is externalized to WordPress;`
   moment-timezone` is bundled into WooCommerce’s JS**.**
 * Here’s the dependency chain:
 * **`moment` is externalized to WordPress; `moment-timezone` is bundled into WooCommerce’s
   JS.**
    1. **WordPress** ships `moment` as a registered script handle. It’s declared in
       the `$vendor_scripts` array in [`wp_default_packages_vendor()`](https://github.com/WordPress/wordpress-develop/blob/abf9109166099011904710d1e8c63f444d0b862a/src/wp-includes/script-loader.php#L90-L133).
       The `@wordpress/dependency-extraction-webpack-plugin` externalizes `import moment
       from 'moment'` to the global `window.moment`.
    2. **`moment-timezone` is NOT externalized** — it’s **bundled into** WooCommerce
       admin’s JS chunks. The [`MomentTimezoneDataPlugin`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/plugins/woocommerce/client/admin/webpack.config.js#L267-L271)
       trims timezone data at build time, confirming it’s processed by webpack. At 
       runtime, `moment-timezone` extends the global `window.moment` object with the`.
       tz()` method. It’s declared as an npm dependency in both [`packages/js/date/package.json`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/packages/js/date/package.json#L37)
       and [`plugins/woocommerce/client/admin/package.json`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/plugins/woocommerce/client/admin/package.json#L198).
    3. **`@woocommerce/date`** is listed in [`wcAdminPackages`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/plugins/woocommerce/client/admin/webpack.config.js#L49)
       and bundled into admin chunks. It [imports both `moment` and `moment-timezone`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/packages/js/date/src/index.ts#L4-L5).
       Its [`getStoreTimeZoneMoment()`](https://github.com/woocommerce/woocommerce/blob/6da1e349b86e057d5dd0965509326ba3995859a6/packages/js/date/src/index.ts#L175-L190)
       calls `.tz()` on the moment instance when the store timezone is a named timezone(
       e.g. `America/New_York`).
 * Since `moment` is a **global external** and `moment-timezone` extends it by mutating`
   moment.prototype`, the conflict vector is: if a third-party plugin enqueues a
   script that replaces `window.moment` _after_ WooCommerce’s bundle has loaded,
   the `.tz()` method disappears. A lazy-loaded chunk like `customizable-dashboard.
   js` then calls `.tz()` on the clobbered `moment` and gets `tz is not a function`.
 * So, it’d be really helpful [@emacencini](https://wordpress.org/support/users/emacencini/)
   if you could verify in your environment this is due to a plugin conflict. It’d
   be any other plugin that is using `moment`. In general, we’re going to be moving
   away from using the moment library because it’s fairly heavy. But until then,
   risk of conflicts like this still exist unfortunately. We’ll also take a look
   at implementing a more defensive check for this type of error.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] [BUG] WooCommerce 10.6.1 – Analytics Dashboard Crash: “tz is not a function”](https://wordpress.org/support/topic/bug-woocommerce-10-6-1-analytics-dashboard-crash-tz-is-not-a-function/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 month, 1 week ago](https://wordpress.org/support/topic/bug-woocommerce-10-6-1-analytics-dashboard-crash-tz-is-not-a-function/#post-18871836)
 * [@emacencini](https://wordpress.org/support/users/emacencini/) it looks like 
   at least one other person has reported this being due to a conflict with another
   plugin. Are you able to share more details about the error from the browser console?
   Also, have you done a plugin conflict test to see if that plugin might be triggering
   the issue?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] WooCommerce Carding Attack (different IPs)](https://wordpress.org/support/topic/woocommerce-carding-attack-different-ips/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/woocommerce-carding-attack-different-ips/#post-18132943)
 * Hi there,
 * Carding attacks are the bane of online commerce! A solution like [Anti-Fraud for WooCommerce](https://woocommerce.com/products/woocommerce-anti-fraud/)
   might work for you?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Problem with Google Merchant center plugin Woocommerce – Cannot get any support](https://wordpress.org/support/topic/problem-with-google-merchant-center-plugin-woocommerce-cannot-get-any-support/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/problem-with-google-merchant-center-plugin-woocommerce-cannot-get-any-support/#post-18132834)
 * Are the login issues still happening for you [@qrest](https://wordpress.org/support/users/qrest/)?
   I’ve done some checks internally as well as testing myself and there doesn’t 
   seem to be problems with logging in at the moment but it may have been something
   that got fixed in between when you reported and I did the check.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Extremely high memory usage in browser and 503 error on Product editing](https://wordpress.org/support/topic/extremely-high-memory-usage-in-browser-and-503-error-on-product-editing/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/extremely-high-memory-usage-in-browser-and-503-error-on-product-editing/#post-18129897)
 * Do the affected products have a large amount of variations/attributes? I noticed
   you have a high value for the PHP `max_input_vars` config.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Extremely high memory usage in browser and 503 error on Product editing](https://wordpress.org/support/topic/extremely-high-memory-usage-in-browser-and-503-error-on-product-editing/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/extremely-high-memory-usage-in-browser-and-503-error-on-product-editing/#post-18129713)
 * Hi there! I see you mentioned this only appears to be happening to certain (duplicated)
   products. Are there specific routes you are seeing this happen (i.e. when editing
   a product, or when viewing the product on the frontend)?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Problem with Google Merchant center plugin Woocommerce – Cannot get any support](https://wordpress.org/support/topic/problem-with-google-merchant-center-plugin-woocommerce-cannot-get-any-support/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/problem-with-google-merchant-center-plugin-woocommerce-cannot-get-any-support/#post-18127630)
 * Hi there, I posted an [update in a separate thread](https://wordpress.org/support/topic/support-request-not-working/#post-18127562)
   about this issue. Submitting a ticket via the form should work now (but chat 
   is not working at the moment – there’s an issue with the service provider that
   we’re working on).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Official “Get Support” broken (for paid official plugins)](https://wordpress.org/support/topic/official-get-support-broken-for-paid-official-plugins/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/official-get-support-broken-for-paid-official-plugins/#post-18127623)
 * Hi there, I posted an [update in a separate thread](https://wordpress.org/support/topic/support-request-not-working/#post-18127562)
   about this issue. Submitting a ticket via the form should work now (but chat 
   is not working at the moment – there’s an issue with the service provider that
   we’re working on).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] ‘502 Bad Gateway’ error always keep](https://wordpress.org/support/topic/502-bad-gateway-error-always-keep/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/502-bad-gateway-error-always-keep/#post-18127617)
 * You may need to set the [`max_input_vars` configuration for PHP](https://www.php.net/manual/en/info.configuration.php#ini.max-input-vars)
   on your server to a higher value with that many variations.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Support request not working](https://wordpress.org/support/topic/support-request-not-working/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/support-request-not-working/#post-18127562)
 * It looks like there was an issue with the chat service that is being investigated
   further, in the meantime the form should work for submitting a ticket now. I 
   checked and it seems to work. Let us know if you’re still not able to use the
   form.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Support request not working](https://wordpress.org/support/topic/support-request-not-working/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/support-request-not-working/#post-18127512)
 * Hi there, thanks for posting about this. I’ve shared this with the relevant folks
   on WooCommerce.com and it’ll be looked into. Will you share more details about
   what options you are selecting from the form?
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WooCommerce] The switch to react destroyed an entire philosophy](https://wordpress.org/support/topic/the-switch-to-react-destroyed-an-entire-philosophy/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/the-switch-to-react-destroyed-an-entire-philosophy/#post-17462962)
 * Hey there, I appreciate you taking the time to leave your feedback. We’re definitely
   listening and want to work with folks to help them understand, utilize and get
   all the great value that is unlocked through the improvements shipped with WordPress
   and WooCommerce. I’m going to address a few of your points here which hopefully
   will help!
 * > Documentation for DEV unclear and absent, major shortcomings
 * We’ve recently launched some updates and improvements to our developer documentation
   on [developer.woo.com](https://developer.woo.com/) which you might not be aware
   of. What documentation is missing that is important to you?
 * > Option settings scattered between customiser and settings
 * The WordPress Customizer is still available for classic theme development and
   ideal for that use-case. For block themes there’s much more rich customization
   options via the site and block editors. Are there specific options/settings which
   you would like to discoverability and usability improved with?
 * > Release versions with major BUGs blocking normal operation
 * Our last couple releases did drop the ball there and we’re making some significant
   adjustments to avoid that in the future. No excuses, we must do better.
 * > Gutenberg is handy, but there is no clear documentation on how to use it from
   > the basics.
 * What would you consider are the basics? This will be helpful to understand the
   gaps in existing documentation that can be surfaced to Gutenberg and within Woo’s
   documentation.
 * > The transition from** PHP to React** was too fast and with blocks that don’t
   > work properly, even in BETA within a release for production sites? Perhaps 
   > you are exaggerating.
 * Very complex interactions will require some React knowledge, but PHP isn’t going
   away. A good example is the thought going into ensuring the [new product editor is extensible via PHP](https://developer.woo.com/2023/11/17/getting-to-know-woo-extensibility-in-the-new-product-editor/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] 8.5.1 is a nightmare](https://wordpress.org/support/topic/8-5-1-is-a-nightmare/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/8-5-1-is-a-nightmare/#post-17358101)
 * If you are experiencing firewall issues, [this advisory](https://developer.woo.com/2024/01/16/woocommerce-8-5-1-issues-with-web-application-firewalls-modsecurity/)
   should provide some guidance.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] More than 39 JS files are loaded on version 8.5.1](https://wordpress.org/support/topic/more-than-39-js-files-are-loaded-on-version-8-5-1/)
 *  Plugin Contributor [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/more-than-39-js-files-are-loaded-on-version-8-5-1/#post-17358047)
 * Hi there. Thanks very much for the report. This is not good and I’ve [created an issue for our team to look into this](https://github.com/woocommerce/woocommerce/issues/43829).
   We’ll update this thread once we have more info.
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[Storefront] After updating Storefront theme Metrix showing long time laps](https://wordpress.org/support/topic/after-updating-storefront-theme-metrix-showing-long-time-laps/)
 *  [Darren Ethier (nerrad)](https://wordpress.org/support/users/nerrad/)
 * (@nerrad)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/after-updating-storefront-theme-metrix-showing-long-time-laps/#post-16921663)
 * Hi [@overyah](https://wordpress.org/support/users/overyah/)
 * You mentioned earlier:
 * > Also noted one more thing in the protocols sections of Redirecting plugin ,
   > this url [https://sab1000.com/wp-content/themes/storefront/storefront-style.min-rtl.css/](https://sab1000.com/wp-content/themes/storefront/storefront-style.min-rtl.css/)
   > is showing 404 error. Is its the reason that website speed is effected . Please
   > help me understand this.
 * That file is not present in the built Storefront theme and I don’t see anywhere
   in the repository where the Storefront theme requests/enqueues that style. The
   request for that URL might be coming from something custom on your site or child
   theme.
 * > Where as in the Storefront child theme every thing is fine because SG optimiser
   > has that combining option enabled for me. 
 * Is this a custom child theme you are using for Storefront, or one of the themes
   in the WooCommerce marketplace? If from the marketplace, can you share the name
   of the child theme you are using? Also what does “SG optimiser” refer to? Is 
   this a special plugin/extension provided by your host or is it something downloaded
   from the WordPress.org plugin repository?
 * You also mentioned that you ran your site through the [GTMetrix tool](https://gtmetrix.com/reports/sab1000.com/EfRasRCs/).
   I’m not seeing any of the original errors you reported in this thread via that
   report. Have you made changes since first starting this forum thread?

Viewing 15 replies - 1 through 15 (of 581 total)

1 [2](https://wordpress.org/support/users/nerrad/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/nerrad/replies/page/3/?output_format=md)…
[37](https://wordpress.org/support/users/nerrad/replies/page/37/?output_format=md)
[38](https://wordpress.org/support/users/nerrad/replies/page/38/?output_format=md)
[39](https://wordpress.org/support/users/nerrad/replies/page/39/?output_format=md)
[→](https://wordpress.org/support/users/nerrad/replies/page/2/?output_format=md)