ddur

Branches are available. Problem is to detect nesting.

Depends. Cached WordPress installation JS/CSS may remain in user browser after WP is updated, and break user experience. Unless JS/CSS query argument (version) is not ignored by caching.

@yogeshbeniwal > @ddur Configuration quoted at #396 is related to caching in Nginx FastCGI cache. Pull request above is for browser caching on client side, which as per Google recommendation...

@tersor Thanks for [the article link](https://docs.wordops.net/how-to/bypass-fastcgi-cache-on-specific-urls/). ### Method 1) Solution is hard-coded. Unmanageable by WordPress (admin) user and requires root administrator intervention. Exactly the problem we would like to avoid...

Actually, sending Cache-Control: (no-store or any other), either from WordOps/Nginx or from PHP should be handled by any CDN and any remote proxy or local reverse-proxy server. I guess that...

Actually, WordPress built-in automatic update does work for me. But. Enable/Disable auto-update link (on Plugins page) does not appear (after first install or until first successful get-metadata, not sure now)...

Activating (forcing) automatic updates is as simple as adding your plugin to array of automatic update basenames. ```php $auto_updates = (array) get_site_option( 'auto_update_plugins', array() ); if ( ! in_array( $plugin->get_basename(),...

@YahnisElsts Hi, I'm working on WP plugin using your update server. When update server and plugin (with update checker) are on same WP site, cannot get ?action=download working (503 Service...

Thanks #489

@YahnisElsts **What are you using to issue licenses, if anything?** WordPress built-in Application Passwords **What are you using to provide updates, if anything?** https://github.com/YahnisElsts/wp-update-server **Does it know how to check...