Closed nathanclevenger closed 4 days ago
Currently Payload does not allow for custom IDs that look like this. You will need to run sanitization on the ID's before the document gets created.
@JarrodMFlesch I just confirmed that this syntax in id
works fine in Payload 2.0, that we are running into as we are upgrading our production systems from Payload 2 to Payload 3.
Since this is a regression with Payload 3.0, and is a show stopper for our upgrade as many documents are no longer accessible after the upgrade, and simply return 404 when it worked fine in Payload 2.0, will you reconsider and re-open this issue?
PR to fix this regression.
🚀 This is included in version v3.1.0
This issue has been automatically locked. Please open a new issue if this issue persists with any additional detail.
Describe the Bug
In a collection with a
id
of typetext
, theid
is not URI decoded before lookup, so it's impossible to view/edit the item as attempts to navigate result in a 404Link to the code that reproduces this issue
https://github.com/nathanclevenger/payload-repro
Reproduction Steps
Create a document with an ID that would be URL Encoded (space/symbol/emoji,etc)
On save, it redirects to a 404:
In the collection, all items are displayed, but links are invalid:
Which area(s) are affected? (Select all that apply)
area: ui
Environment Info