We created the link the normal way by typing some text and then highlighting it.  We then clicked on the link icon.  It brought up the new link window.  We select 'a file on your site' and then after selecting a PDF, we clicked on finish.

The link in the text module used to be malformed when we upgraded from 3.3.3 to 3.3.4, but now it works okay after 3.3.5 was installed.  FYI, a week ago we upgraded the text/html module from that project's download page.  It may have something to do with the fact the links is still broken for you.

Bob

---

Actually, 3.3.5 fixed our problem but it introduced the file sync problem that led to even more problems.  Your 'do not have permission to view....' problem may just have to do with the permissions on each directory.  If your Intranet restricts access based on roles, you may have to give that role permissions to view that directory.  3.3.6 fixed all the file sync and directory problems.

Just another note, 3.3.6 introduced a major bug for us.  Since you are using it in an Intranet application, you may been creating your own modules.  If so, the 'Add new module' function on the 'host/module definitions' page is totally broke.  You can't manually create a module and then add definitions, etc.  We fixed ours by commenting out some erronous code in the .vb file and then recompiling DNN.  We replaced the dotnetnuke.dll with ours and everything is fine.  This will work until they patch 3.3.6 or until the next minor upgrade.  To read more about this, go to here

Have fun!

 

---

The rights are already set correctly. That was the first thing I checked when I found out there was an issue. It was working great with 3.2.2 and we didn't see a problem until we upgraded to 3.3.5. I've been on holidays the past week so I haven't had a chance to look at upgrading to 3.3.6 or 4.3.6.