Adding a tag element to document fetch <a> tags...

Message from Sean M. Alderman via eLinkGreetings, I'm looking for some advice on adding a TARGET element to the tagswhich are used for fetching documents. Since upgrading to v9.1, withmostly Win2k desktops using IE6, Acrobat Reader 5.0 and Office 2k2, ourusers are finding that they have to click the back button twice toreturn to where they fetched a PDF document. The fetch/open actioncauses the document to be launched in IE 6 via plugin integrationbetween Acrobat and IE, and there seems to be a redirect to the fetchaction. As a result, if the back button is clicked once, the browsergoes back to the redirect and thus opens the document again. Thiscauses a lot of confusion, so I'm hoping to add a TARGET="blank" to the tag which will make the fetched document open in a new browserwindow. Granted people will end up having to close an empty window whenthey do a fetch/save, but at least that's not confusing.The tags that show up for the view (of a pdf, which is forcefetched), the fetch links from the Mac view, and the Fetch menu item inthe functions menu would all need to be changed. I assume there's notcentral place to do this, but I was hoping someone might be able topoint me in the right direction, since I haven't had much luck trackingthese down.--Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795A mathematician is a device for turning coffee into theorems. -- P.Erdos

Find more posts tagged with

Comments

Birger_Jacobsen_(danskadmin_-_(deleted))

Hello SeanDid you solved this problem, I'm interrested in a solution where customer can open 2 or 3 different document in new windows for comparison.

Donna Nalls

Hi Sean,I had a similar situation where I had to open a new window for document fetches and downloads.If you notice in the /support/functionmenu.js file - popup_callback function - it actually expects a target as the second arg in. Unfortunately, I have never been able to find an easy way to pass that argument in, so here is a little bit of hack that i used to resolve my problem.If you orphan the Fetch WebNodeCmd from $WEBDOC into your custom ospace. You can modify the _SubclassIsEnabled() method. check for the mimetype of your document - if it is a pdf, then modify the .fQueryString feature:.fQueryString = 'func=%1&nodeid=%2&newTarget=true'Then, in the functionmenu.js file popup_callback method, check for that argument passed in and set the target to blank. (This example includes download - you will have to take that out.)if ( ( (theURL.indexOf( 'objAction=download' ) > 0) || (theURL.indexOf( 'func=doc.Fetch' ) > 0) ) && (theURL.indexOf( 'newTarget=true' ) > 0) ){ theTarget = "blank" } -----You can test this quickly by just modifying the functionmenu.js file for all fetches - then go back and work with the webnode command methods to add a new window for pdf docs only.Remember, this is kind of a hack - someone else may have a more supported way to handle this.Good luck,Donna

Catherine_Aillas

Hi Donna, I came across your issue (2003) on the Knowledge Center, trying to find something that could help me.The fetch/open action on a pdf file causes the document to be open in Acrobat because of the option we took (pdf is not displayed in the browser). Then, when we close the Acrobat windows we get an empty windows and we have to click the back button once to return to where the document was fetched.When the pdf file was opened in the browser (before we changed the Web browser option), we had to click twice to return to where the document was fetched.We are using LL 9.5 SP1, IE6 and windows 2003.Did you find a "clean" solution to your problem and are you still running livelink 9.1 ?ThanksHave a nive dayCatherine