-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Make Site Settings available to duplicate views experiment users #98875
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
client/sites/components/site-preview-pane/dotcom-preview-pane.tsx
Outdated
Show resolved
Hide resolved
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~129 bytes removed 📉 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~8179 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. 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. |
4641a1b
to
8cbf951
Compare
9eed548
to
45ecba9
Compare
@@ -86,11 +86,12 @@ class SiteSettingsFormJetpackMonitor extends Component { | |||
|
|||
/* eslint-disable wpcalypso/jsx-classname-namespace */ | |||
return ( | |||
<PanelCard className="jetpack-monitor-settings"> | |||
<HostingCard |
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'm curious why we changed many PanelCard
back to HostingCard
in this PR?
The idea was to deprecate HostingCard
and start using PanelCard
in the new design.
I tried reverting the changes in this file (and the defensive mode card) and I didn't notice any broken visual.
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.
If we use PanelCard
, there will be inconsistent spacing because the other HostingCard
has an extra margin-bottom
.
![Screenshot 2025-01-30 at 12 22 46](https://private-user-images.githubusercontent.com/5287479/407983408-4fbad0db-06e8-4224-9b52-8aa58a18f698.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MTEzMTMsIm5iZiI6MTczOTUxMTAxMywicGF0aCI6Ii81Mjg3NDc5LzQwNzk4MzQwOC00ZmJhZDBkYi0wNmU4LTQyMjQtOWI1Mi04YWE1OGExOGY2OTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTRUMDUzMDEzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MjUwOWRlYzQ1MjMzM2ZmNjBkMGE2OWNmOTg5Njg3NjA2NmZlYmFkZjg0ZjkzM2Y5ZmI5MDFiOTZjMWRmODhhNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.mMQrJxiD5Ns8c4DWrGTmRoZyCkOl0BYbR2scHH7zrQg)
In production, this isn't an issue since we're using Masonry, but this PR removes it to align them vertically. https://github.com/Automattic/wp-calypso/pull/98875/files#diff-907edd6df95246780ac004e4382376a1337c383d5623336379d74a2e44707ab8R195
I reverted the change in 011e592, and I believe we can keep using PanelCard
for now, as we're exploring the layout design (card, one-column, two-column) TvapEJxLZ98RGWobNN1Xd1-fi-487_10437 and addressing it soon. CC: @matt-west
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.
Added a minor comment about making the width of the settings cards consistent across tabs.
Why do we display the Admin interface style
card here now?
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.
Mostly works great, I came across a couple of issues:
- This might be ok but I would expect the admin interface switcher not to redirect to wp-admin when modifying this option in SMP.
- Switching to a staging site while on settings results in errors,
2a. Clicking server settings subtab results in a broken back button - Switching to a simple site while on server settings takes you to hosting features instead of General settings (One could argue this is correct but I expected to stay in the settings tab)
Peek.2025-01-30.11-15.mp4
Revert "Add "Admin interface style" to General Settings" This reverts commit b0caa4b.
Thanks for the feedback!
After discussion, I removed the Admin Interface setting from SMP. Added the following context in the description: 👇
Slack convo: p1738198428731869/1738195548.078849-slack-CRWCHQGUB |
I checked our latest design, and the Hosting Features tab is separate from the Settings tab: So, I think I suggest keeping users within the Settings tab when switching to a simple site while on Settings > Server. That feels more intuitive. Thoughts? @matt-west @lsl |
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.
Tested both control and treatment behaviors. It works nicely 👍
Agreed. 👍 |
This reverts commit 2d5d325.
@@ -58,7 +61,7 @@ export function siteSettings( context, next ) { | |||
} | |||
recordPageView( basePath + '/:site', analyticsPageTitle ); | |||
|
|||
next(); | |||
redirectIfDuplicatedView( 'options-general.php' )( context, next ); |
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.
Needed to happen after the above redirect checks so running the extra middleware here instead of in the controller like all the others.
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
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.
Tested without the wp-admin redirects:
Treatment:
- Simple site Classic view
- Simple site Default view
- Atomic site Classic view
- Atomic site Default view
Control:
- Simple site Classic view
- Simple site Default view
- Atomic site Classic view
- Atomic site Default view
Everything looks good / makes sense.
Fixes #98185
Related to #98185, pfYzsZ-1uU-p2
Not strictly blocking but should be merged with Automattic/jetpack#40913 at a similar time.
Proposed Changes
This PR makes "Site Settings" available to duplicate views experiment users.
/sites/settings/site/:site
/hosting-config/:site
/hosting-features
:/sites/settings/site/:site/transfer-site
/sites/settings/site/:site/reset-site
/sites/settings/site/:site/delete-site
/settings/general/:site
/sites/settings/site/:site
on Classic, Redirect to options-general.php on Default with #98664/sites/settings/site/:site
on Classic, Redirect to options-general.php on Default with #98664/settings/start-over/:site
/sites/settings/site/:site/reset-site
/sites/settings/site/:site/reset-site
/settings/start-site-transfer/:site
/sites/settings/site/:site/transfer-site
/sites/settings/site/:site/transfer-site
/settings/delete-site/:site
/sites/settings/site/:site/delete-site
/sites/settings/site/:site/delete-site
This PR removes the Admin Interface setting from Server Settings, and we won't have the Admin Interface setting anywhere in SMP. i.e., the Admin Interface setting can only be found in
/wp-admin/options-general.php
.Redirection logic:
/settings/general
(Hosting > Site Settings) redirects to SMP since they are compatible feature-wise./settings/general
(Settings > General) redirects tooptions-general.php
/settings/reading
(Settings > General) redirects tooptions-reading.php
/settings/writing
(Settings > General) redirects tooptions-writing.php
/settings/discussion
(Settings > General) redirects tooptions-discussion.php
p1738292995924339/1738285330.573259-slack-CRWCHQGUB
Why are these changes being made?
See #98185 and pfYzsZ-1uU-p2.
This PR focuses on adopting the new design's structure. We will address styling details in later iterations soon:
pfYzsZ-1uU-p2#comment-1452.
Testing Instructions
Regression testing:
Pre-merge Checklist