Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-39701

Unable to save changes to Space Permissions for a group containing a whitespace

XMLWordPrintable

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Whenever a user tries to edit the Space Permission and update its information, Confluence fails to do so and report the following error:

      [Error] Error: Syntax error, unrecognized expression: [name=confluence_initial_viewspace_group_<instance_group>]

      It happens if the space has given a permission to a group which has a white space in the group name (i.e test group).

      Steps to reproduce

      1. Create a Space and create a group with a similar name.
        For example:
        • Space: Space test
        • Group: Space test
      1. Try to update the Space Permission by adding the Space test group.
      2. Hit Save All.

      Expected behaviour

      1. The permissions should be updated.

      Actual
      Nothing happens and all buttons are greyed out.
      The following error appears on the console:

      [Error] Error: Syntax error, unrecognized expression: [name=confluence_initial_viewspace_group_<instance_group>]

      Additional info
      Confirmed with Google Chrome and Safari.
      It doesn't happen when browsing with Firefox or Internet Explorer.

      Workaround
      Use other browsers, like Mozilla Firefox or Internet Explorer.

            [CONFSERVER-39701] Unable to save changes to Space Permissions for a group containing a whitespace

            Daniel Köck added a comment -

            We also have this problem in 7.4.11, not sure why it's marked as resolved.

            Daniel Köck added a comment - We also have this problem in 7.4.11, not sure why it's marked as resolved.
            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2897684 ] New: CONFSERVER Bug Workflow v4 [ 2992192 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2789556 ] New: JAC Bug Workflow v3 [ 2897684 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2736121 ] New: JAC Bug Workflow v2 [ 2789556 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391349 ] New: JAC Bug Workflow [ 2736121 ]
            Alex Yakovlev (Inactive) made changes -
            Labels Original: affects-cloud affects-server bugfix loyalty warranty New: affects-cloud affects-server loyalty warranty
            Alex Yakovlev (Inactive) made changes -
            Labels Original: affects-cloud affects-server bugfix warranty New: affects-cloud affects-server bugfix loyalty warranty

            IST Account added a comment -

            This issue is still occurring in Confluence 6.2.0 (Server) with Chrome (Version 60.0.3112.90) so not sure why it is marked as "resolved".

            It appears that CONFSERVER-39701 and CONFCLOUD-39701 share the exact same comments so it's unclear if "resolved" would apply to both.

            All recent issues created referencing this problem have been marked as duplicate and redirected to this to track progress but there is not much public facing communication around the progress just a workaround and an incorrect status of "resolved".

            Given Chrome's prolific usage and our fairly recent version of both Chrome and Confluence, it's quite shocking to see this has been around for so long.

            IST Account added a comment - This issue is still occurring in Confluence 6.2.0 (Server) with Chrome (Version 60.0.3112.90) so not sure why it is marked as "resolved". It appears that CONFSERVER-39701 and CONFCLOUD-39701 share the exact same comments so it's unclear if "resolved" would apply to both. All recent issues created referencing this problem have been marked as duplicate and redirected to this to track progress but there is not much public facing communication around the progress just a workaround and an incorrect status of "resolved". Given Chrome's prolific usage and our fairly recent version of both Chrome and Confluence, it's quite shocking to see this has been around for so long.
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 [ 2271281 ] New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391349 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2221496 ] New: Confluence Workflow - Public Facing - Restricted v5 [ 2271281 ]

              lho@atlassian.com Le Ho (Inactive)
              pjunior Paulo Junior (Inactive)
              Affected customers:
              8 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: