You're encountering the 'Password cannot be submitted' error when trying to test a password-protected page on your Webflow staging site, which prevents client access. This is usually caused by how the staging site is published or due to browser/caching issues.
1. Check That the Staging Site Is Properly Published
- Go to your Webflow Designer, then click Publish.
- Make sure your
webflow.io
staging domain (e.g., yourproject.webflow.io
) is checked/selected in the publish settings. - Confirm that the staging domain has the latest version of the site published.
2. Verify Password Protection Is Enabled on the Correct Version
- Go to Project Settings > Memberships & Access (or Pages if using individual page protection).
- Ensure password protection is enabled only where needed — either on a single page, folder, or the whole site.
- Double-check that you’re assigning the password to the staging version (if you're using separate domains for staging and production).
3. Use an Incognito or Private Browsing Window
- Browser cache or cookies may cause issues with submitting the password form.
- Open a private/incognito window, then go to your
webflow.io
URL. - Try to enter the password again.
4. Avoid Custom Code Conflicts
- If you've embedded any custom scripts or form-altering JavaScript, those might interfere with the password form.
- Temporarily remove or disable custom code in the Site Settings > Custom Code to test if the issue persists.
5. Confirm the Correct Directory Is Password-Protected
- If you’ve protected a folder, but you’re sending your client to a specific page, ensure that page resides within that folder.
- Mismatched paths may result in unexpected behavior.
6. Re-Publish the Staging Site to Clear Errors
- After making any updates or disabling custom code, do a full re-publish:
- Click the Publish dropdown in Designer.
- Select the
webflow.io
domain. - Click Publish to selected domains again.
Summary
The 'Password cannot be submitted' error on staging is often caused by staging-specific publish issues, custom code conflicts, or cached browser data. Use a private browser to test, ensure Webflow is publishing to the staging domain properly, and re-check password configuration under Project Settings. Re-publishing the staging domain usually resolves the problem.