umbraco-validation-checks

A 400 payload error in Umbraco backoffice extensions often stems from incorrect API payloads, wrong enum formats, or GUID formatting issues. Validate your DevTools network payloads and headers against expected DTO formats and auth/CORS constraints to identify the mismatch.

To troubleshoot missing Umbraco sections or menu items, check configuration and user-group permissions first. Then diagnose navigation and tree visibility for alias or manifest issues, and verify hidden workspace actions that might prevent proper UI rendering.

To fix empty uui-select combobox options causing null values in Umbraco, verify correct property and event bindings. Ensure option formatting is correct to prevent null or undefined values from triggering failed API requests.

Non-functional workspace save and submit flows in Umbraco backoffice extensions are caused by missing workspace actions, empty workspace data loads, or submit persistence failures. Verify workspace action registration and inspect DevTools for API failures.

Yes, Chrome DevTools is required for diagnosing Umbraco backoffice API and network failures. You inspect network payloads, verify headers, and check auth/CORS constraints to pinpoint incorrect structures causing failing API requests.

The best way to validate Umbraco backoffice extension behavior is a symptom-to-category triage workflow. Open Chrome DevTools, load the matching check category for permissions, navigation, API, forms, or workspace, and verify payload and header formats.