You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, once an HTML file is cached via the file caching mechanism, the only way the item gets purged is if a WordPress event occurs that triggers a purge or a user manually purges. Otherwise, the content is cached indefinitely. Our cache settings promise that HTML files will only be cached for a specific timeframe. While that is more specifically referencing the browser cache, we should respect that same timeframe with our static file caching.
The text was updated successfully, but these errors were encountered:
…RL_PATH is always set, which prevents the str_replace() call from outputting "Deprecated: str_replace(): Passing null to parameter #1 ($search) of type array|string is deprecated"
* main:
Ensure that the URL has a trailing slash. This ensures that the PHP_URL_PATH is always set, which prevents the str_replace() call from outputting "Deprecated: str_replace(): Passing null to parameter #1 ($search) of type array|string is deprecated"
add brand plugin test workflow
add brand plugin test workflow
fix autofixable lint issues in test file
add .nvmrc as v16
At the moment, once an HTML file is cached via the file caching mechanism, the only way the item gets purged is if a WordPress event occurs that triggers a purge or a user manually purges. Otherwise, the content is cached indefinitely. Our cache settings promise that HTML files will only be cached for a specific timeframe. While that is more specifically referencing the browser cache, we should respect that same timeframe with our static file caching.
The text was updated successfully, but these errors were encountered: