Dion Hulse
Dion Hulse
Not even `$this`?
I've released version 0.8 which resolves this.
See #95 for the discussion around it, notably, it's about the maintenance burden and ongoing maintenance of the plugin, rather than intentionally leaving older installs "out in the cold". Older...
> The use case is, that an older install of WP will fail to install that importer from the tools menu. Oddly enough, this isn't actually true - A WordPress...
These files appear to be bypassing the ServiceWorker's fetch listener. The thing they all have in common is being triggered for fetch via react-dom
There's another option here - Make WordPress not output scoped URLs for static resources in the first place.. bypassing the need for the serviceworker to handle it. This can probably...
FWIW I feel like a "Login with emailed link" feature (aka "magic login link") is out-of-scope of this plugin, and there are a number of existing plugins which provide that...
I don't think using the `authenticate` or `auth_cookie` filters are very appropriate here, and using those has the potential of breaking other use-cases which has to use those filters. However,...
> > I don't think using the `authenticate` [...filter is] very appropriate here > > Why is that? If we only modify `send_auth_cookies`, will that leave a gap when other...
Regardless of what follows below, two quick pointers on reading this PR: - SECURE_AUTH_SALT as used as the encryption key isn't going to always be defined on older installations -...