#7805552 BBE: Save website content to server

Sent to vendor

Created on February 10, 2023 , translate by Sunday, February 12, 2023 (431 days ago)

Translate 2 originals (13 words) to Swahili Glossary

Prio	Original string	Translation	—
	Changes saved successfully!	You have to log in to add a translation.	Details
Changes saved successfully! Changes saved successfully! You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: untranslated Priority: normal More links: Permalink to this original All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (sw) Show all deliverables with this original (overview) View deliverable: BBE: Save website content to server
	Failed to save your content. Please check your internet connection.	You have to log in to add a translation.	Details
Failed to save your content. Please check your internet connection. Failed to save your content. Please check your internet connection. You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: untranslated Priority: normal More links: Permalink to this original All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (sw) Show all deliverables with this original (overview) View deliverable: BBE: Save website content to server

Legend:

Current

Waiting

Fuzzy

Old

With warnings

Export strings as

UI Changes:

Adds a new button on the website content form to save website content to the server. Clicking on the button will make a network request that saves all form data to the server.

The “Save Changes” button is enabled only if there are unsaved changes.
The “Next” button also saves content first and then opens the next section.
Clicking on any of the section titles opens the relevant section and saves content in the background.
For the above two actions, the network request to save changes is only sent if there are unsaved changes.
Refreshing the page or opening the page in a different browser/tab/device should pre-populate the form with the saved data.

Code changes:

While the quantity of changes seems to be large, they are mostly due to refactors, considering that the source of truth for this data is the server and not browser-based storage. I have left inline comments to explain major changes.

Go to /start/do-it-for-me, proceed through the flow steps and complete the purchase.
Once you reach the website content form, type in any text content and click on the “Save Changes” button.
Confirm that the button has a loading state and form interaction is blocked during this time.
Reload the page and confirm that the typed data is prepopulated.
Repeat the above three steps with the site logo section and the feedback section.
Open the form link in an incognito window or in a different browser and confirm that the form is prepopulated with saved data.

Has the general commit checklist been followed? (PCYsg-hS-p2)
Have you written new tests for your changes?
Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
Have you checked for TypeScript, React or other console errors?
Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

Unfortunately, no screenshots were provided by the developer.