Rich Text Links to Author Environment | Community
Skip to main content
robertt3523754
robertt3523754
Level 2
February 22, 2019
Solved

Rich Text Links to Author Environment

  • February 22, 2019
  • 20 replies
  • 6162 views

We recently upgraded from AEM 6.0 to AEM 6.3.  We've run into a situation with links in rich text boxes.  Whenever we create a link to an asset (such as a PDF), and publish the page, the published site links to the asset on the author server.  I checked the jcr node and the link that is populated in the text property contains the full path rather than the relative path.  I'm sure that there's a configuration setting that I'm missing somewhere, but I can't find any documentation on what that is.  Any help is appreciated.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by robertt3523754

    We have solved the issue!!!  Apparently we did not have all the latest patches installed.  Our system administrator just installed the latest service pack (6.3.3 I believe) and the problem is now resolved.  Thank you all for your help and advice!

    20 replies

    Gaurav-Behl
    Gaurav-Behl
    Level 10
    February 22, 2019

    How do you author the urls - relative or absolute?

    Are you talking about 'Day CQ Link Externalizer' configuration under /system/console/configMgr ?

      robertt3523754
      robertt3523754Author
      Level 2
      February 22, 2019

      The problem that we're having is that we want the links to be relative, but the rich text component is making those links absolute.  As for the Web Console configurations, our sys admin normally handles that.  Could if be something she forgot to configure?

        Gaurav-Behl
        Gaurav-Behl
        Level 10
        February 22, 2019

        Per my knowledge, OOB rich text won't convert the relative links to absolute on its own. Either the content author provided the absolute links or there is a site level configuration in-place to achieve that.

        Could you check the /content/<root_page>/jcr:content for any such configurations? In addition to that, could you share screenshots/gif/video of what you configure and what you expect it to be in author & publish server after authoring and activation?

          robertt3523754
          robertt3523754Author
          Level 2
          February 22, 2019
          • I add a rich text component to the page (on author), highlight some text and use the link icon and navigate to a pdf in assets.
          • The path that show in the box, is a relative path (/content/dam/...) which looks correct.  However, when you check the jcr node, the full path was populated (which is the path to our author server).
          • Therefore, when you publish the page, the full path is published and the link is wrong.

          I did just find out though that it seems if you go back in a second time into the same component and link to another pdf, the second link is correct.

            Gaurav-Behl
            Gaurav-Behl
            Level 10
            February 22, 2019

            this behavior shouldn't happen with this hyperlink feature.

            Do you mean to say it just happens for one pdf only and not the other one?

              robertt3523754
              robertt3523754Author
              Level 2
              February 22, 2019

              No.  It happens on all pdfs.  It also doing the same thing across out dev, qa, and prod tiers.

                antoniom5495929
                antoniom5495929
                Level 7
                February 22, 2019

                Hi,

                can you share:

                - a package with the component that you are using

                - the zip extraction of http://localhost:4502/system/console/status-Configurations

                Just if it's possible; it seems an interesting behaviour.

                Thanks,
                Antonio

                  Gaurav-Behl
                  Gaurav-Behl
                  Level 10
                  February 22, 2019

                  Its probably some kind of customization (Link Checker/Path Rewriter Transformers/Externalizer) that is responsible for the behavior. You would definitely find clues in the source code.

                    robertt3523754
                    robertt3523754Author
                    Level 2
                    February 22, 2019

                    The problem occurs when using the standard foundation text component at /libs/foundation/components/text.

                      smacdonald2008
                      smacdonald2008
                      Level 10
                      February 22, 2019

                      I will try with the CORE TEXT COMPONENT.

                      Show more replies
                      Terms & ConditionsAccessibility statement

                      Loading footer...