Require Check-In: Edit Form Looping Bug

Forums Classic DFFS Require Check-In: Edit Form Looping Bug

Viewing 3 reply threads
  • Author
    • #33554

      Hi Alexander,

      Would you be able to take a look at a potential bug when the Require Checkout feature is enabled.


      When a user edits and item that is not currently checked out they are unable to cancel the form and close the dialog.

      The window checkin/out prompts loop without closing the dialog.


      1. Navigate to /sites/dffs/Lists/CheckInOutBug/AllItems.aspx
      2. Ensure the item is currently not checked out.
      3. Edit the item
      4. Click “OK” to checkout the item.
      5. Click “Cancel”
      6. Click “OK”
      7. “Repeat steps 4-5” and the form can never be cancelled.


      SharePoint 2010
      Browser (Chrome, Edge, IE Doc Mode 10)

      Version information

      DFFS Loader: v1
      DFFS frontend: – May 17, 2021
      DFFS frontend CSS: 4.64
      Autocomplete: – April 25, 2021
      Cascading dropdowns: 3.7.46 – March 21, 2021
      jQuery: 1.12.4
      Lookup: 1.1.20 – March 10, 2020
      Resource management: not loaded
      SPJS-Utility: 1.350 – February 21, 2021
      vLookup: 2.2.161 – March 21, 2021

      If you open an item that is already checked out. Clicking save correctly closes the dialog.

      • This topic was modified 3 years ago by Ross.
      • This topic was modified 3 years ago by Ross.
      • This topic was modified 3 years ago by Ross.
    • #33570
      Alexander Bautz

      I’ll check it later tonight.


    • #33592
      Alexander Bautz

      I didn’t manage to replicate the issue, but made one change in the code to hopefully fix the issue. Ensure it shows as v4.4.5.26 and try again to see how it performs.


    • #33596

      The change seems to have fixed the issue.

      The steps I did to replicate it on /sites/dffs no longer cause the loop/bug.

      Will deploy the changes tonight.

      Thanks again.

      • #33602
        Alexander Bautz

        Great! – I’ll include this fix in the next release.


Viewing 3 reply threads
  • You must be logged in to reply to this topic.