fix: complete frontend customer account and site management

DESIGN.md

@@ -52,3 +52,36 @@ Keep the existing stacked widget layout on desktop and mobile. List nameservers
 on separate lines and allow long hostnames to wrap without truncation. Hide the
 summary during loading or lookup errors; preserve the existing record table and
 provider-managed editing controls.
+
+## Frontend customer accounts
+
+Keep account-wide membership, billing and invoices separate from site-specific
+summary and limits. Account Summary must offer a sign-in link when logged out,
+an owner-scoped site chooser before site selection, and a neutral no-sites state
+instead of silently rendering nothing. Do not silently select the first site:
+customers may own several. Once a site is selected, omit self-referential
+"See More" links and show remaining trial days from the actual membership date.
+Use the existing stacked widget styles on desktop and mobile, with native links
+and wrapping site names; do not add fixed-width panels or a second design system.
+Frontend account pages belong on the main site; customer-site admin Account
+screens remain an alternative interface to the same membership.
+
+On combined pages, Manage must visibly land on the selected site's controls,
+using a keyboard-focusable native fragment target (Account Summary is the
+fallback). Your Sites clears selected-site context and returns to the page
+permalink. Successful frontend deletion returns to the account landing page,
+unless an explicit destination is configured; never retain a deleted-site URL.
+Sites without a template initialize the selector to numeric zero so their first
+selection exposes the same destructive-action confirmation as template changes.
+
+Payment-method changes must return from Stripe Billing Portal to the originating
+account page, using a validated local destination. Show the subscription's card
+override when present; otherwise show the customer's default payment method,
+including after the portal clears an override while replacing the default card.
+
+Native account blocks share shortcode renderers, settings and ownership checks.
+Load widget preview styles inside the block editor canvas, including iframe
+editors. Numeric controls save integers and toggle defaults use booleans. Group
+and Columns layouts must preserve nested element attributes during early setup,
+especially the Checkout form slug. Editor previews use sample data; verify real
+customer actions on the published page rather than treating a preview as proof.

inc/admin-pages/class-payment-edit-admin-page.php

@@ -1186,10 +1186,10 @@ public function register_widgets(): void {
 					'confirm_membership'       => [
 						'type'              => 'toggle',
 						'title'             => __('Activate Membership?', 'ultimate-multisite'),
-						'desc'              => __('This payment belongs to a pending membership. If you toggle this option, this change in status will also apply to the membership. If any sites are pending, they are also going to be published automatically.', 'ultimate-multisite'),
+						'desc'              => __('This payment belongs to a pending or on-hold membership. Enable this option to activate or renew the membership when confirming the payment. Any pending sites will also be published automatically.', 'ultimate-multisite'),
 						'value'             => 0,
 						'wrapper_html_attr' => [
-							'v-if'    => 'status !== original_status && status === "completed" && membership_status === "pending"',
+							'v-if'    => 'status !== original_status && status === "completed" && (membership_status === "pending" || membership_status === "on-hold")',
 							'v-cloak' => '1',
 						],
 					],

inc/builders/block-editor/assets/js/blocks.js

@@ -109,7 +109,8 @@
 
 						const obj = {};
 
-						obj[ field_slug ] = value;
+						// NumberControl emits strings; the block REST schema requires integers.
+						obj[ field_slug ] = field.type === 'number' ? Math.trunc(Number(value)) : value;
 
 						props.setAttributes(obj);
 

inc/builders/block-editor/class-block-editor-widget-manager.php

@@ -125,6 +125,7 @@ public function register_block($element): void {
 			[
 				'attributes'      => $attributes,
 				'editor_script'   => 'wu-blocks',
+				'editor_style'    => 'wu-admin',
 				'render_callback' => \Closure::fromCallable([$element, 'get_content']),
 			]
 		);
@@ -236,9 +237,21 @@ public function get_attributes_from_fields($element) {
 			}
 
 			$default_value = wu_get_isset($defaults, $field_id, '');
+			$value         = wu_get_isset($field, 'value', $default_value);
+
+			// Block defaults must have the same types as their REST schema.
+			if ( ! is_callable($value)) {
+				if ('boolean' === $type) {
+					$value = (bool) $value;
+				} elseif ('integer' === $type) {
+					$value = (int) $value;
+				} else {
+					$value = (string) $value;
+				}
+			}
 
 			$_fields[ $field_id ] = [
-				'default' => wu_get_isset($field, 'value', $default_value),
+				'default' => $value,
 				'type'    => $type,
 			];
 		}