• Phastpress seems great and while I love the “no customization” approach, there’s one big problem with this: If we can’t exclude certain scripts and stylesheets, Phastpress will break a ton of stuff and a lot of users won’t be able to use the plugin.

    Here’s an example:

    Klaviyo, an ultra-popular email marketing tool, has an integration with WooCommerce. Their scripts are optimized by Phastpress and tracking no longer works. Hence, I can’t use Phastpress on any of the client sites I work on. Shame!

Viewing 1 replies (of 1 total)
  • Plugin Author Albert Peschar

    (@kiboit)

    Hi @crunchybar,

    The idea is that it should never be necessary to manually disable PhastPress for scripts. Of course PhastPress sometimes breaks things, and sometimes it’s possible to fix the issue in PhastPress itself.

    Right now I’m away for a few days so I won’t be able to dive into this until next week. It would be great if you could give me any additional details I need to reproduce the problem. Then I’ll look at it next week.

    For now, you could disable PhastPress’ script optimization, or add the data-phast-no-defer attribute to the problematic script.

    –Albert

Viewing 1 replies (of 1 total)
  • The topic ‘Exclude scripts’ is closed to new replies.