-
Notifications
You must be signed in to change notification settings - Fork 2k
Dashboard v2: Implement Settings -> Caching #103826
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
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~80268 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~3142 bytes removed 📉 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~8210 bytes removed 📉 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
It's just disabled; not busy. It seems to be the behavior in v1. |
? createInterpolateElement( | ||
__( 'Manage your site’s server-side caching. <learnMoreLink />.' ), | ||
{ | ||
learnMoreLink: <a href="#learn-more">{ __( 'Learn more' ) }</a>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this is waiting for the help center to land?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, we have this placeholder all over the place, we should clean this up when help center is ready.
It would be nice to sort that out. It's a bit distracting for that to change states. It's also a tad confusing as to why the "Clear all" button would be disabled and not the other cache (although I can understand the underlying technical reason). |
Yeah, I agree. Updated to not disable the Clear all button when clearing individual caches. |
learnMoreLink: <a href="#learn-more">{ __( 'Learn more' ) }</a>, | ||
} | ||
) | ||
: ''; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description in this upsell situation is not accurate when the site is Business but not Atomic-transferrred yet. I talked more this in DOTCOM-13376. Let's solve it separately
@fushar sorry if I missed this, but is the use case where non-public sites cannot enable Global edge cache implemented? We can follow-up in a later PR if it's not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There's a scenario that we might have missed which was mentioned in #103826 (comment). We can follow up in a separate PR.
fields: [ 'active' ], | ||
}; | ||
|
||
export function canUpdateCaching( site: Site ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can now move this to https://github.com/Automattic/wp-calypso/blob/trunk/client/dashboard/utils/site-features.ts 😀
Oops I totally missed it 🤦 will follow up later! |
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17534577 Some locales (Hebrew) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday. Thank you @fushar for including a screenshot in the description! This is really helpful for our translators. |
Fixes DOTCOM-13257
Proposed Changes
This PR implements the Settings -> Caching as follows:
Out of scope
I've scoped out these features for future follow-ups:
Pre-merge Checklist