A pop-up appears but cannot be edited. about redmine_issue_dynamic_edit HOT 5 OPEN

At the first install, it works, but now it doesn't. Even after reinstalling, the error is the same.

from redmine_issue_dynamic_edit.

From the logs, it seems that the problem is that the ID is changed from admin to anonymous (I logged in as admin).

from redmine_issue_dynamic_edit.

Hello,

I have the same problem on redmine with the following environment:
Environment:
Redmine version 5.0.4.stable
Ruby version 2.7.4-p191 (2021-07-07) [x86_64-linux-gnu]
Rails version 6.1.7
Production environment
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp

Redmine settings:
Redmine theme Redmine-theme-purplemine2 (includes JavaScript)

SCM:
Git 2.30.2
Filesystem

Redmine plugins:
iotbzh 1.0.0
iotbzh_menu_links 0.0.1
redmine_impersonate 2.0.0
redmine_indicator 0.2.16
redmine_issue_dynamic_edit 0.9.1
redmine_lock_out 0.0.1
redmine_openid_connect 0.9.4

The database was imported from a redmine 4.

And I have the impression that it is related to LDAP whose configuration was also imported, during my tests with a clean DB, no problem to modify dynamically, but with the imported DB it does not work, and indeed I see an anonymous user in the logs.

I also have a server identification popup, and when I log on, the plugin is working again.
<----------------------------------------------------->
After removing the LDAP connector, the problem is still there

I continue to investigate ...

from redmine_issue_dynamic_edit.

Ilogeek and team,
Thanks so much for making this very important plugin. I've given you a star :). Let me know if anything else would help. We use this plugin in a healthcare application and it saves a lot of headache.

I have the same issue. I'm on redmine 5.0.5 and dynamic edit 0.9.1
To reproduce, try:

• create custom fields that have text/number types
• make several custom fields, and delete a few and/or change their order in the custom fields list, e.g., have field IDs [1,2,5,4] where 3 was deleted, and 5 was moved above 4.
• The PATCH call is sent with no field code, from production.log

I, [2023-03-31T22:55:47.425520 #306]  INFO -- : [XXXXX] Started PATCH "/issues/962" for XXXXX at 2023-03-31 22:55:47 -0400
I, [2023-03-31T22:55:47.426202 #306]  INFO -- : [XXXXX] Processing by IssuesController#update as */*
I, [2023-03-31T23:23:25.696092 #308]  INFO -- : [XXXXX]   Parameters: {"authenticity_token"=>"XXXXX", "id"=>"962"}
I, [2023-03-31T23:23:25.699237 #308]  INFO -- : [XXXXX]   Current user: admin (id=1)

Note Parameters have no field. For different custom field of a list type, a dynamic edit calls correctly

I, [2023-03-31T22:41:05.530059 #308]  INFO -- : [XXXXX]   Parameters: {"issue"=>{"custom_field_values"=>{"13"=>"Male"}}, "authenticity_token"=>"XXXXX", "id"=>"962"}

• I also saw what @gousekid reported regarding a 403 error, but I logged out of all browsers and cleared passwords, and the 403 errors went away, but the Parameter problem remained

from redmine_issue_dynamic_edit.

Hello

Have same issue after migrating base from redmine 3.5 to 5.0.
Using PostgreSQL on latest Ubuntu with latest Ruby, Rails and other staf.

from redmine_issue_dynamic_edit.