You are viewing limited content. For full access, please sign in.

Question

Question

Weblink 10 exportedcontent.zip

asked on January 26, 2018 Show version history

We would like users to download the pdf directly in the browser instead of weblink zipping the file for download.  How do we do we enable direct pdf download?  In version 9 of the product, the browser would open the pdf directly.  

4 0

Answer

SELECTED ANSWER
replied on February 16, 2018

Hello Cliff,

 

Being able to download from the folder browser along with its context menu is a new feature we added in WL10. Opening the browser directly is still there and was never taken out as Drew has noted and mentioned. We will however improve this behavior for our coming WL patch slated for late Q1 to early Q2. Would you be able to open it using the weblink document viewer for now?  We apologize for the inconvenience. 

2 0
replied on May 2, 2018

Hi @████████I see that weblink 10.1 has been released.  I see that you can adjust how PDF are viewed using the "My Weblink" configuration page.  How do we make this change globally so each user does not have to make this change or in the case that My Weblink is disabled?

 

Thanks

replied on May 4, 2018

Got it figured out.... thanks again for the updated version!

1 0

Replies

replied on January 29, 2018

Does anyone have an update on this?

replied on February 16, 2018

Was this a feature that was removed? I thought version 9 allowed you to view a pdf in the browser.

0 0
replied on February 20, 2018

this functionality was removed.  weblink 10 now forces you to use the document browser.  The document browser also only displays the generated laserfiche pages for PDF documents.

0 0
replied on March 23, 2018

@████████ do you know why the functionality was removed? For .pdfs, my users now just see the generated text and when they download the copy, they get the generated text pages! This will not work for us.

1 0
replied on March 24, 2018 Show version history

They removed the functionality most likely due to a rewrite of the code.  for pdfs you must generate laserfiche pages so they are visible in the new document viewer.  There may be new functionality coming that mimics version 9.  I agree, the functionality also does not work for us either.

0 0
replied on March 26, 2018

Hello Robyn and Cliff,

 

My sincere apologies for this inconvenience for you and your users. We are aware of this issue, and it is being addressed. We will be bringing out a patch very soon, looking to address this issue. Once again, we apologize for the convenience and appreciate your feedback. 

 

Regards,

0 0
replied on March 26, 2018

Thanks, Andrew! I was concerned this would be an ongoing feature. We can generate pages for our more active documents for now (and delete them later, once a patch is out).

0 0
replied on March 26, 2018

Hello Robyn,

Fortunately it is not an ongoing feature. Though unfortunately it was a bug. But I am aware how problematic this bug is, so I just wished to extend my sincere apologies again and thank you for coping with the workaround as we get the patch wrapped up and ready to ship to our users.

1 0
replied on April 17, 2018

Andrew, we are having the same issue in our weblink server could you please help us if there is already a patch or configuration to solve it¿?.

 

Thanks.

0 0
replied on February 20, 2018

the document browser does not work on mobility devices and that is why the functionality in version 9 worked so well.  we will have to use alternative methods until this functionality returns.

0 0
replied on April 17, 2018

Hi Cliff, could you please tell us if you solved this issue...¿?

 

Thanks.

0 0
replied on April 20, 2018

Laserfiche has still not provided an updated version of weblink so this issue is still outstanding.

0 0
replied on March 9, 2018

Anyone find a solution to get Web Link 10 to download/open a PDF from the browse page?

All I get is Document Viewer or ExportedContent.zip.

Anyone find the v9 aspx needed to do this?

You are not allowed to follow up in this post.

Sign in to reply to this post.