Title: JS Minification Bug
Last modified: April 1, 2019

---

# JS Minification Bug

 *  [Reuhno](https://wordpress.org/support/users/laboiteare/)
 * (@laboiteare)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/js-minification-bug/)
 * Thanks for your plugin which works very well.
 * However, I found a bug with Wp-Rocket concatenation, linked to wp-includes/js/
   dist/block(*).js
 * Javascript errors appears on Safari & Firefox (not on Chrome).
 * After some research, I found the gulty : block.build.js
 * Does this file needs to be loaded in fronted when you’re not logged-in ?
 * To resolve my problem I deregistered _direct-stripe-block-script_ from my theme
   if I’m not logged in and it’s working fine.
 * Maybe you want to do some investigations on this ?

Viewing 1 replies (of 1 total)

 *  Plugin Author [Nicolas Figueira](https://wordpress.org/support/users/nahuelmahe/)
 * (@nahuelmahe)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/js-minification-bug/#post-11387468)
 * Hello [@laboiteare](https://wordpress.org/support/users/laboiteare/) ,
 * Thank you for using Direct Stripe and sharing your concern.
 * I ‘ll definitely investigate this.
 * Kind regards

Viewing 1 replies (of 1 total)

The topic ‘JS Minification Bug’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/direct-stripe_7787ff.svg)
 * [Direct Stripe](https://wordpress.org/plugins/direct-stripe/)
 * [Support Threads](https://wordpress.org/support/plugin/direct-stripe/)
 * [Active Topics](https://wordpress.org/support/plugin/direct-stripe/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/direct-stripe/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/direct-stripe/reviews/)

## Tags

 * [concatenation](https://wordpress.org/support/topic-tag/concatenation/)

 * 1 reply
 * 2 participants
 * Last reply from: [Nicolas Figueira](https://wordpress.org/support/users/nahuelmahe/)
 * Last activity: [7 years, 1 month ago](https://wordpress.org/support/topic/js-minification-bug/#post-11387468)
 * Status: not resolved