Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-325

Section renaming using "Section Properties" button causes one more section to be created

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.1
    • Fix Version/s: 5.2.0-B1
    • Component/s: Data Management
    • Labels:
      None
    • Additional information:
      Hide

      I've attached extended version of CategoryEventHandler class, where such problem is fixed (the one with opener stack), see code, that includes "opener" or "filename" words in it.

      Show
      I've attached extended version of CategoryEventHandler class, where such problem is fixed (the one with opener stack), see code, that includes "opener" or "filename" words in it.
    • Story Points:
      2
    • External issue ID:
      392
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      1. Go to Front-End in "Content Mode" and use "Section Properties" button (on top).
      2. Change section name, so filename will be change too.
      3. You end up on newly created page inside page you edited and named as old page name and created by "Guest" user.

      This all happens because old page url is stored in opener_stack and when page url is changed, then opener_stack is not updated.

      New page is created by Guest user (current user on Front-End) in case, when administrator visits url of page, that doesn't exist. I doubt, that such functionality is required at all.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                alex Alex
                Reporter:
                alex Alex
                Developer:
                Alex
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: