I checked and the allow for the pdf extension is set in dispatcher.any.  Also I can view the PDF directly on the published website using the full path.  It's just not getting embedded to the page.  To clarify, the div appears on the page on the published site, it's just an empty div.<div class="pdfv...

I am trying to use the PDF Viewer for the first time on one of our sites.  I've followed the steps from https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/pdf-viewer.html?lang=en.  I also configured the sling:configs nodes under /conf on author and publish us...

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!

It looks like the Day CQ Link Externalizer is just the default settings.  I checked our old server (AEM 6.0) where the links worked and it appears that nothing was setup before there either.There are no config or config.author nodes under the projects themselves.  Here are the config nodes under sys...

This is a new server.  It also happens across all three tiers (dev, qa, and prod).

It looks like the Apache Felix settings are just the default settings.  I'm beginning to wonder if the ssl cert was maybe setup and configured wrong.  Could that cause the issue that we're having?PID = org.apache.felix.http  BundleLocation = launchpad:resources/install/5/org.apache.felix.http.jetty-...

It doesn't look like I'm able to upload the zip file.  Are there any particular portions that I can just copy and paste for you?

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

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

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 pa...