Uploaded image for project: 'LAMS Development'
  1. LAMS Development
  2. LDEV-1875

When moving a folder, backend shouldn't allow a folder to become its own parent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.4, 2.3.3
    • Component/s: Author, General
    • Labels:
      None

      Description

      I found an inconsistency in the database of a lams2.1 server - in lams_workspace_folder, one row whose id=47 had parent_folder_id=47 (ie it was its own parent). This appeared to happen due to this call from flash:

      sysadmin [22/Jul/2008:11:42:58 +1000] "GET /lams/workspace.do?method=moveResource&resourceID=47&resourceType=Folder&targetFolderID=47&userID=1 HTTP/1.1" 200 296

      I've tried to do this manually but couldn't - in any case we can amend the backend to not allow this type of move where a folder ends up being its own parent. When this happens it stops all the other folders (whether they are private, or group folders) from appearing.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            jundirl Jun-Dir Liew
            Reporter:
            jundirl Jun-Dir Liew
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development