Yes, Sitefinity used to resolve links for updated PDFs, but the links break now. Our PDFs are displayed as hard-coded links. We display the name of the PDF document and then use the Hyperlink Manager to create the link. So people just click on the PDF name to open the document. I looked at the other forum post that you mentioned, but didn't think that sounded like the same issue. Let me know if you have other thoughts.
Perhaps I used the wrong term. I just meant the the links are behind the scenes and people click on the name of the PDF file. The links are created within Sitefinity using the Document Manager. So they used to get dynamically resolved when we updated the links through the Documents & Files utility. We have not been doing anything different since updating Sitefinity versions.
Here is a video (screencast.com/.../5BKDKOfviH2) that shows how we have always updated PDFs and it has worked in the past. (I'm new to Jing, so let me know if you can't view. It also took me awhile to find the STOP button at the end!) Once the catalog was updated in the video, the link on our website no longer works. The HTML in the old, working link is: <a href="/docs/product-bulletins/t-tl---ceiling-and-cabinet-ventilators---catalog-4600.pdf?Status=Master"> </a><p>T-TL - Ceiling and Cabinet Ventilators - Catalog 4600</p>
and the HTML from the Embed Link to this File function is www.tcf.com/.../t-tl---ceiling-and-cabinet-ventilators---catalog-4600.pdf
Why is the /default-source/ being added to the HTML? The end of the code also changes. I would like to get this resolved as soon as possible, so we can make changes to our site.
I am the lead software developer at TCF and when I navigate to the UrlName Parameter in SiteFinity, there is not a Value. See the attached file. Should we delete the entire UrlName Parameter or just remove the Value?