DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

URL not bound to session

 5 Replies
 2 Subscribed to this topic
 37 Subscribed to this forum
Sort:
Author
Messages
New Around Here
Posts: 2
New Around Here

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.

New Around Here
Posts: 2
New Around Here
apparently got trimmed from the message..

...all of my document server references are in "
Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
The click handler (LinkClik.aspx) could be checking file permissions and they might not be set to allow visitors to download that file. Or there is some bug in that version where it fails if it can't figure it out. I would certainly start by upgrading. Moving to the new server should be no problem other than configuring stuff right.

For upgrading DNN itself 7.0.5 is pretty old and I would recommend starting there, even if it does not fix the issue at hand, it will increase security a lot and should there be a bug to fix, nobody will backport the fix, so being on latest would help.

We have upgrade documentation here https://docs.dnncommunity.../upgrades/index.html and we also have a recommended upgrade path (version steps that received more testing) here https://docs.dnncommunity...rade-path/index.html

If you run into any troubles, we are here to help and if you need more hands on support, you can take a look at agencies here https://dnncommunity.org/community/agencies
Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Oh also, not sure if it is in the upgrade docs, but you may have a few or many 3rd party extensions installed. my flow for each version on these upgrade steps is usually something like this.
1. Check and remove any unused extension.
2. Update all 3rd party extensions to the latest version know to work on DNN of the currently installed version.
3. Update one step of DNN

Rince and repeat.
New Around Here
Posts: 2
New Around Here

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. 

Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
LinkClick.aspx is not a file but a virtual path defined in the web configuration file and handled by a request handler to figure out what to do with the request.

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:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved