I have implemented a simple custom reaction, and the reaction form contains managed file field. When a file is selected in the field and Upload button is clicked, the AJAX request is sent to context.reaction_add route (which is correct since this route returned the original form), which returns 403 (since the reaction of this type already exists).

Comments

Alex Bukach created an issue. See original summary.

alex.bukach’s picture

Assigned: alex.bukach » Unassigned
Status: Active » Needs review
StatusFileSize
new1.01 KB

For AJAX requests it should just rebuild the form instead.

icurk’s picture

Status: Needs review » Postponed (maintainer needs more info)

I also created a simple custom reaction with a managed_file field, but I don't get any errors. Do you still have problems with it?

alex.bukach’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new1.01 KB

@icurk yes, I get 403 response when auto uploading starts, and debugging shows it arises right from the place changed by the patch. Here's the re-rolled patch for the latest dev version.

I also created a simple custom reaction with a managed_file field, but I don't get any errors.

May I ask you to share the code of that reaction with me? Maybe actual issue is in my custom reaction.

maaty388’s picture

@Alex Bukach I created context reaction with file upload field and I didn't get any errors.

boshtian’s picture

Status: Needs review » Postponed (maintainer needs more info)

Alex Bukach, can you maybe share the code you created? I want to know if this is still a problem or should we close this issue.

deaom’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

No activity so closing as outdated.