-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suboptimal rewrite handling causes plugin conflicts #1075
Comments
Actually, the flushing is happening at |
As per the support topic, Polylang deletes the The PWA code in question here: pwa-wp/wp-includes/class-wp.php Lines 9 to 31 in 62961cd
The PWA plugin calls However, flushing like that should typically only occur on plugin activation/deactivation or when a new site is created in Multisite, or (if the plugin has that) in some sort of upgrade routine / migration script. That's how we do it in the Web Stories plugin for example: https://github.com/GoogleForCreators/web-stories-wp/blob/afe6e41af3f0086181a4cdf12060c2c2b6d4bf29/includes/Infrastructure/ServiceBasedPlugin.php#L116-L208 |
Alternatively, we can avoid flushing the rules entirely because the plugin also contains this failsafe code which runs at the pwa-wp/wp-includes/service-workers.php Lines 215 to 218 in 62961cd
|
So is there a code change planned? |
Yes. I need to set aside some time this month to do this and the 0.8 release. |
Here we go: #1096 |
I ran into constant rewrite issues with Polylang and the PWA plugin as reported here, so I had to disable the latter for now.
Turns out the way the PWA plugin adds and potentially flushes rewrite rules on
init
is flawed. See Chouby's explanation.The text was updated successfully, but these errors were encountered: