• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 1.2
    • 1.1.2
    • None
    • Version: 1.1.2 Build:#57 Jun 21, 2004
      jira standalone default installation
      Camel Case linking turned on

      page anchors are not rendered properly when Camel Case linking is enabled in admin screen.

      I tried using and then point to it in another section of the document using myanchor1

      when page id displayed is rendered as partially garbled text in the page, and myanchor1 page does not take you anywhere (because the html anchor is not created properly).

      I left the page as is but then turned Camel Case linking in Admin screen OFF. The anchor was then rendered properly (in html view source of the wiki page) and subsequently the link myanchor1 worked properly.

            [CONFSERVER-1519] page anchor links break

            This is fixed, but at the expense that some camel-case links (such as those enclosed in quotes) will no longer work.

            Charles Miller (Inactive) added a comment - This is fixed, but at the expense that some camel-case links (such as those enclosed in quotes) will no longer work.

            In your JIRA user profile, you can choose not to be notified of your own actions.

            Charles Miller (Inactive) added a comment - In your JIRA user profile, you can choose not to be notified of your own actions.

            EXTERNAL MESSAGE:
            SUBJECT: RE: [JIRA] Commented: (CONF-1519) page anchor links break
            why do I get updates about my own comments to a bug? This is redundant, and
            if I am a manager or whatever, who needs to comment on lots of bugs it can
            get ugly - spamming my inbox.
            is this a bug or a notification scheme set up?

            ----Original Message----
            From: jira@atlassian.com jira@atlassian.com
            Sent: Friday, July 09, 2004 3:52 PM
            To: Ilya.Pogorelsky@gfigroup.com
            Subject: [JIRA] Commented: (CONF-1519) page anchor links break

            The following comment has been added to this issue:

            Author: Ilya Pogorelsky
            Created: Fri, 9 Jul 2004 2:49 PM
            Body:
            this is not the first bug tied to Camel Case linking being turned ON in
            Admin screen. There was another one CONF-1340 which is now fixed (as of
            1.1.2)

            Using Camel Case is pretty critical to many people migrating from existing
            wiki's. So please, please pay special attention to doing good regression
            testing whith Camel Case linking ON.
            ---------------------------------------------------------------------
            View this comment:
            http://jira.atlassian.com/browse/CONF-1519?page=comments#action_23319

            ---------------------------------------------------------------------
            View the issue:
            http://jira.atlassian.com/browse/CONF-1519

            Here is an overview of the issue:
            ---------------------------------------------------------------------
            Key: CONF-1519
            Summary: page anchor links break
            Type: Bug

            Status: Unassigned
            Priority: Critical

            Original Estimate: Unknown
            Time Spent: Unknown
            Remaining: Unknown

            Project: Confluence
            Components:
            Linking
            Versions:
            1.1.2

            Assignee:
            Reporter: Ilya Pogorelsky

            Created: Fri, 9 Jul 2004 2:46 PM
            Updated: Fri, 9 Jul 2004 2:49 PM
            Environment: Version: 1.1.2 Build:#57 Jun 21, 2004
            jira standalone default installation
            Camel Case linking turned on

            Description:
            page anchors are not rendered properly when Camel Case linking is enabled in
            admin screen.

            I tried using and then point to it in another section of
            the document using myanchor1

            when page id displayed is rendered as partially garbled
            text in the page, and myanchor1 page does not take you anywhere (because
            the html anchor is not created properly).

            I left the page as is but then turned Camel Case linking in Admin screen
            OFF. The anchor was then rendered properly (in html view source of the wiki
            page) and subsequently the link myanchor1 worked properly.

            ---------------------------------------------------------------------
            JIRA INFORMATION:
            This message is automatically generated by JIRA.

            If you think it was sent incorrectly contact one of the administrators:
            http://jira.atlassian.com/secure/Administrators.jspa

            If you want more information on JIRA, or have a bug to report see:
            http://www.atlassian.com/software/jira

            ***************************************************************
            Confidentiality note: This e-mail contains information from the
            GFI Group Inc. and/or its affiliates, including GFInet inc.,
            that is confidential and/or legally privileged. This
            information is intended only for the use of the individual or
            entity named on this e-mail. This e-mail and its content may
            not be reproduced or retransmitted without the express written
            permission of The GFI Group.
            ***************************************************************

            Ilya Pogorelsky added a comment - EXTERNAL MESSAGE: SUBJECT: RE: [JIRA] Commented: ( CONF-1519 ) page anchor links break why do I get updates about my own comments to a bug? This is redundant, and if I am a manager or whatever, who needs to comment on lots of bugs it can get ugly - spamming my inbox. is this a bug or a notification scheme set up? ---- Original Message ---- From: jira@atlassian.com jira@atlassian.com Sent: Friday, July 09, 2004 3:52 PM To: Ilya.Pogorelsky@gfigroup.com Subject: [JIRA] Commented: ( CONF-1519 ) page anchor links break The following comment has been added to this issue: Author: Ilya Pogorelsky Created: Fri, 9 Jul 2004 2:49 PM Body: this is not the first bug tied to Camel Case linking being turned ON in Admin screen. There was another one CONF-1340 which is now fixed (as of 1.1.2) Using Camel Case is pretty critical to many people migrating from existing wiki's. So please, please pay special attention to doing good regression testing whith Camel Case linking ON. --------------------------------------------------------------------- View this comment: http://jira.atlassian.com/browse/CONF-1519?page=comments#action_23319 --------------------------------------------------------------------- View the issue: http://jira.atlassian.com/browse/CONF-1519 Here is an overview of the issue: --------------------------------------------------------------------- Key: CONF-1519 Summary: page anchor links break Type: Bug Status: Unassigned Priority: Critical Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Confluence Components: Linking Versions: 1.1.2 Assignee: Reporter: Ilya Pogorelsky Created: Fri, 9 Jul 2004 2:46 PM Updated: Fri, 9 Jul 2004 2:49 PM Environment: Version: 1.1.2 Build:#57 Jun 21, 2004 jira standalone default installation Camel Case linking turned on Description: page anchors are not rendered properly when Camel Case linking is enabled in admin screen. I tried using and then point to it in another section of the document using myanchor1 when page id displayed is rendered as partially garbled text in the page, and myanchor1 page does not take you anywhere (because the html anchor is not created properly). I left the page as is but then turned Camel Case linking in Admin screen OFF. The anchor was then rendered properly (in html view source of the wiki page) and subsequently the link myanchor1 worked properly. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.atlassian.com/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira *************************************************************** Confidentiality note: This e-mail contains information from the GFI Group Inc. and/or its affiliates, including GFInet inc., that is confidential and/or legally privileged. This information is intended only for the use of the individual or entity named on this e-mail. This e-mail and its content may not be reproduced or retransmitted without the express written permission of The GFI Group. ***************************************************************

            this is not the first bug tied to Camel Case linking being turned ON in Admin screen. There was another one CONF-1340 which is now fixed (as of 1.1.2)

            Using Camel Case is pretty critical to many people migrating from existing wiki's. So please, please pay special attention to doing good regression testing whith Camel Case linking ON.

            Ilya Pogorelsky added a comment - this is not the first bug tied to Camel Case linking being turned ON in Admin screen. There was another one CONF-1340 which is now fixed (as of 1.1.2) Using Camel Case is pretty critical to many people migrating from existing wiki's. So please, please pay special attention to doing good regression testing whith Camel Case linking ON.

              Unassigned Unassigned
              655be4c5b8b0 Ilya Pogorelsky
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: