Fix multiple custom file upload fields#2929
Merged
Armanul46 merged 1 commit intoJul 23, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Type
What kind of change does this PR introduce?
Description
How to reproduce the issue or how to test the changes
This fixes custom File Upload fields after the first field failing with an "Invalid upload request!" response on new listing submission forms.
Each custom File Upload field generates a separate security token tied to its directory and field key. However, the Plupload initializer reads the first global
atbdp_plupload_paramsconfiguration for every uploader. The second and subsequent uploaders therefore submitted the first field's token with their ownimgid, causing the server-side field/token validation to reject the request.This change exposes each field's token on its own uploader container and assigns that token to the corresponding Plupload request during the existing initialization loop. The original base configuration remains as a fallback for backward compatibility. No additional requests, database queries, or event listeners are introduced.
Directorist -> Directory Builderand add at least three separateFile Uploadfields to a submission form.action=atbdp_post_attachment_uploadimgidupload_tokenAny linked issues
Screenshot
Checklist