Bug 46666 - Portal: saving entry order may save false ordering
Portal: saving entry order may save false ordering
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Portal
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-14 16:26 CET by Johannes Keiser
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
keiser: Patch_Available+


Attachments
Patch (526 bytes, patch)
2018-05-11 19:52 CEST, Johannes Keiser
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Keiser univentionstaff 2018-03-14 16:26:04 CET
Reproduce on portal site:

Drag an entry into a different category and Cancel the Drag and Drop mode.
Enter the Drag and Drop mode again and click "Save entry order" without changing anything. The previously dragged entry will be in the new category.

Reason:
The category in which an portal entry is shown is saved on the entry object.
When an entry is dragged to a different category it is noted internally that that entry needs to be updated with the new category when saved. This note is not cleared when canceling the Drag and Drop mode so when entering the Drag and Drop again and just saving the portal entry gets updated even though nothing was changed.
Comment 1 Johannes Keiser univentionstaff 2018-05-11 19:52:38 CEST
Created attachment 9529 [details]
Patch
Comment 2 Ingo Steuwer univentionstaff 2021-05-14 15:41:52 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.