Brady Vercher

@GaryJones I guess I never noticed that before! This approach seems to strip the `` tags out, though:  I poked around in...

@tyrann0us The project I built SatisPress for is currently using it without any issues, so I've considered it to be pretty stable. I realize there are maintenance tasks that need...

I released an updated version of SatisPress that includes a number of updates and compatibility with the latest versions of PHP. Feel free to open any issues if you run...

@acketon Those errors *seem* like they're related to loading the Grunt tasks. Is the only thing that changed updating to the latest version of `grunt-wp-i18n` (and it's inclusion of `[email protected]`)?...

Nope, not expected. I haven't installed without `composer.lock` in awhile, so didn't run into that. You can lock that package down to a specific version first: `composer require --dev wp-cli/i18n-command:^2.6`

I believe that header is a directive for the client only (browser, Composer, etc) and doesn't affect the server's caching policy. It sounds like the caching rules need to be...

@rmpel As @BrianHenryIE mentioned, this is by design when `WP_DEBUG` is enabled. Let me know if it doesn't work as expected when `WP_DEBUG` is disabled or if there's a reason...

@rmpel I went ahead and added a filter in 77b8a1f50c2ef8f0a6b8baadcc5764128cd064e5 to override debug mode for that request handler. That'll be included in the next release.