HI - Newbie here. I'm trying to determine how to resolve a problem, as well as planning for upgrade / future.
First a little background - i inherited DNN support which provides content to our customer's clients... in general it has been working well and has required little support.
I think our system is using DNN version 7.0.05 and obvious-to-me needs to be updated, so part of my problem solution may be in updating DNN to current release, and understanding what i need to do to any DNN updates (feel free to point me towards training videos or such).
DNN is currently running on Windows 2012 R2 server OS and connects to SQL Server 2014 and Report Server 2016 which we are moving towards standing up Server 2022 with SQL Server 2019. Reason mentioned is whether i need to plan for any DNN behavior change because of OS / SQL Server upgrades.
Problem description:
When a user requests a document that is stored as FILESTREAM in SQL Server, that document's URL is only available to anyone during the active session, but if the document is stored as a file on an external server on a different network, that URL is good to use anytime, whether user is in a session or not. Currently the requested PDF document is displayed in a browser window that has the URL in the titlebar, and of course the URL is also displayed in any document's hyperlink in the user's document selection window. I could use some ideas / pointers on how to change this behavior. I saw one suggestion about using something like https://.... but i'm not clear where to use this since all of my document server references are in I"m sure by now you are wondering if I'm looking for someone that offers DNN support as a service... ans: Yes.
I"m sure by now you are wondering if I'm looking for someone that offers DNN support as a service... ans: Yes.
Thanks for the pointers Daniel.
I haven't found any evidence that LinkClick.aspx exists in our envioronment, but even if it did I don't know where the "reader wrappers" are assigned / assembled but i do see where the filestream reader is located in the URL for getting documents from SQL Server.
To retreive documents from the external server it is currently calling JavascriptCE function which uses the assembled "add key" URL and the document path.
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.