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

Question

Question

WebLink "Object moved to here" Error

asked on June 20, 2014

I receive an 'Object moved to here' error when trying to access a doc on WebLink through an iPad to the following url: 

 

http://records.atascadero.org/weblink8/DocView.aspx?dbid=0&id=65605&openfile=true

 

Any ideas?

 

Thanks.

 

 

 

0 0

Replies

replied on June 23, 2014

Hi Luke,

 

This is a bug and an SCR was filed for such issue. You can remove "&openfile=true" to open the file from LF Document Viewer as a workaround.

 

Regards

0 0
replied on June 23, 2014

Thanks Xiaoxiao,

 

I was hoping to be able to open pdfs directly.  I also receive errors for:

 

/weblink8/ElectronicFile.aspx?docid=65605&dbid=0

  • Error executing child request for /weblink8/ElectronicFile.aspx

/WebLink8/0/doc/65605/Electronic.aspx

  • Cannot use a leading .. to exit above the top directory.

 

Any idea when that bug might be worked out?

 

Thanks again.

 

Luke

0 0
replied on June 23, 2014

Luke,

 

For this other issue, it's still something that only occurs in the Safari browser on an iPad? If you mean that these additional issues are something users are facing even when using a web browser on a standard PC, then please upgrade WebLink to 8.2.2 as we've addressed some of these URL related issues.

 

Regards

0 0
replied on June 23, 2014

Alexander,

 

I upgraded to 8.2.2 last week and have not noticed these errors on a PC since then.  They come up on the iPad with Safari or Chrome.

 

Thanks.
 

0 0
replied on June 23, 2014

Thanks for the clarification. When I visit http://records.atascadero.org/weblink8/ the page indicates WebLink 8.2.0 still so I was curious about the version that you're running.

0 0
replied on June 23, 2014

Luke,

 

Are you saying that you also received error when you removed "&openfile=true" to open the file? I was able to open the file from LF Document Viewer after removing "&openfile=true".

 

What if you try http://records.atascadero.org/weblink8/DocView.aspx?dbid=0&id=65605&fullui=true&openfile=true? I can open the PDF document in both Safari and Chrome browsers.

 

Regards

0 0
replied on June 24, 2014

No, no error with removing "&openfile=true", but not what I need.  Adding in "&fullui=true" still gives me an error on the iPad.  I need to be able to open the document in its native pdf form.  The pdf is an agenda packet that has internal links from the agenda to the staff reports.  Generating a pdf from the Laserfiche pages of the pdf removes those links.

 

Thank you.

0 0
replied on June 24, 2014

The first question is how did you obtain this URL as I am not able to produce that type of URL? I get the same error if I change my user agent to iPhone or iPad or Safari and even IE 6.0. However if I manipulate the URL to http://records.atascadero.org/WebLink8/0/doc/65605/Page1.aspx then it opens directly in the document viewer with no issues.

 

If you are creating this type of URL to send out then maybe recreating it using the above URL might help.

0 0
replied on June 24, 2014

The URL is from Laserfiche documentation on how to link directly to an electronic file.  Page1.aspx only works with Laserfiche docs, not pdfs.

 

Thank you.

0 0
replied on June 24, 2014 Show version history

Did you open the link on your iPad? It's the same document that you put in your first post. It will open the PDF in the  WebLink Document viewer.

 

However, reading over your request again you really need this PDF to open directly into a compatible PDF viewer like Adobe Acrobat because of the links that are in the PDF document.

 

Let me do some more testing on this.

0 0
replied on June 24, 2014

Using an iPad 6.02.00 with 7.1.1 installed with Safari I am unable to produce the error wth "/WebLink8/0/doc/65605/Electronic.aspx".

0 0
replied on June 25, 2014

Unfortunately, the error is not consistent.  With Chrome, as well as Safari, the error comes and goes.  I would like to find a link that works consistently.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.