Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?
SaaS
What are the exact steps to reproduce this issue?
Hi everyone,
I’m running into an issue with prefilled form URLs that used to work but now seem to be broken, possibly due to a recent update.
What I had set up:
I have two ways of accessing the same form:
A prefilled form using a URL parameter (/category/page/{ID})
(In practice, the link would look like: /category/page/?={NUMERIC ID HERE})
A non-prefilled (blank) form by leaving the ID parameter empty
Previously, this worked fine:
If an ID was provided → the form loaded prefilled
If no ID was provided → the form still loaded as a blank form
What’s happening now:
If the ID is empty, the URL ends with a trailing slash like this:
/category/page/
This now returns a “Page not found” (404) error.
What I expected:
The form should still load as a blank form when no ID is provided, as it did before.
My question:
Did Baserow recently change how trailing slashes or empty parameters are handled?
Or is this a bug?