Summary
When a pad is created with a forward slash (/) in its name, the Admin Dashboard → Pads list displays the pad correctly, but the Open button generates a URL that treats the slash literally instead of encoding it as %2F. As a result, the link attempts to navigate into a nested path rather than opening the pad.
The pad can be opened manually if the slash is replaced with %2F in the URL.
Steps to Reproduce
Log in as an admin.
Create a new pad with a name containing a slash, e.g. "Test/123"
Go to admin/pads.
Click the Open button for that pad.
Actual Behavior
The generated link is something like:
/p/Test/123
Etherpad interprets this as a nested path (Test → 123) and fails to open the pad.
Expected Behavior
The pad name should be URL‑encoded when generating the link.
The Open button should point to:
/p/Test%2F123
Environment
Etherpad version: 3.2.0
Browser: Any
Admin Dashboard page: /admin/pads
Additional Notes
The pad is stored and listed correctly; the issue is only with the link generation.
This appears to be a missing encodeURIComponent() (or equivalent) when building the URL for the Open button.
Summary
When a pad is created with a forward slash (/) in its name, the Admin Dashboard → Pads list displays the pad correctly, but the Open button generates a URL that treats the slash literally instead of encoding it as %2F. As a result, the link attempts to navigate into a nested path rather than opening the pad.
The pad can be opened manually if the slash is replaced with %2F in the URL.
Steps to Reproduce
Log in as an admin.
Create a new pad with a name containing a slash, e.g. "Test/123"
Go to admin/pads.
Click the Open button for that pad.
Actual Behavior
The generated link is something like:
/p/Test/123
Etherpad interprets this as a nested path (Test → 123) and fails to open the pad.
Expected Behavior
The pad name should be URL‑encoded when generating the link.
The Open button should point to:
/p/Test%2F123
Environment
Etherpad version: 3.2.0
Browser: Any
Admin Dashboard page: /admin/pads
Additional Notes
The pad is stored and listed correctly; the issue is only with the link generation.
This appears to be a missing encodeURIComponent() (or equivalent) when building the URL for the Open button.