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

Question

Question

WebLink - Cookies enabled issue

asked on April 6, 2017

Here is the basic problem that one of our Clients is encountering. When calling/creating a link to a Weblink doc via their integration, the parameter “CR=1” is added to the Weblink URL. Since the user does not go to the main page to get a cookie created and CR=1 is a check for a cookie, the page will not show.

We’d like to know if there is a way to eliminate this CR=1 parameter from being added to the URL.

 

From our understanding, this is only a problem on the initial load when the cookie is being created. But the issue for our Client is that Public users will be accessing this link through the Integration to look at their  documents.  For most this will be there one and only time they will ever access the link.  If they hit this on the 1st try, they will think their documents are not there.

 

Any ideas on how to resolve this issue will be highly appreciated.

0 0

Replies

replied on April 6, 2017

Karim,

Do you mean that their integration is constructing the URL with "cr=1" at the end? As long as the link they click on doesn't have "cr=1" then there shouldn't be an issue. Can they alter how their integration is creating the links to WebLink?

Regards

1 0
replied on May 29, 2020

Any update on this issue?

1 0
replied on April 11, 2017

Alex,

 

The Integration is creating this link: http://MyServer/weblink/DocView.aspx?id=44455

Once this link is opened in a browser, it becomes http://MyServer/weblink/DocView.aspx?id=44455&cr=1

 

It seems Weblink adds the parameter 'CR=1'. This was replicated in the VARkit.

 

 

 

0 0
replied on April 11, 2017

That's by design. You can see the difference by going to

http://webdemo.laserfiche.com/weblink/docview.aspx?id=532994

vs

http://webdemo.laserfiche.com/weblink/docview.aspx?id=532994&cr=1

The first link will work whereas the second link will give you the message about cookies not being enabled.

1 1
replied on October 5, 2018

Alex,

 

We are looking to avoid the public users having to see this screen at all. As mentioned above, they will only be connecting once to get a document.  They won't be saving any personal site settings, nor browsing for any length of time.

 

Is there a way to disable this behavior, altogether?

0 0
replied on January 28, 2019

I have the same issue , can any one provide me how to resolve that .

0 0
replied on February 1, 2019

Hi Mohammed,

 

The link should exclude the 'cr=1'. The 'cr=1' is what typically triggers the cookies.

0 0
replied on February 2, 2019

can you let me know how to exclude cr=1 from the link 

1 0
replied on October 15, 2024

We are interested in this as well!

Christine

0 0
replied on October 21, 2024 Show version history

For anyone interested, I found a 'workaround' to this issue.  I simply put '&cr=0' at the end of the string and this seems to make it work properly.  It still appends  '&cr=1' again to the end (or sometimes '/&cr=1'), but that doesn't seem to mess it up.

Hope this helps.

0 0
replied on October 22, 2024

As a workaround you can just remove the '&cr=1' altogether.

0 0
replied on October 22, 2024

Hey Blake, unfortunately that isn't a solution because the system keeps automatically adding '&cr=1' to the end of the URL every time, which is the complaint of pretty much everyone on this thread.   Apparently this is 'by design' for some reason, so my workaround is the only way I've found to deal with it so far by adding &cr=0 to the URL that the user clicks on.

0 0
replied on October 22, 2024

We always just have our users remove it and it has been working for them.

0 0
replied on October 22, 2024

When you say 'users', are you talking about the end user?   This is a public URL, so we can't just post on the website, "Please click on this link and then remove 'cr=1' from the URL to fix the problem'.  We needed this to work the first time they click on it.    Not having 'cr=1' in the URL just makes it append 'cr=1' to the end automatically, so my workaround is essentially forcing it to use a different value for 'cr' the first time.

0 0
replied on October 22, 2024

Yes, we have employees use WebLink at our organization, so in our case it works. I can see how in your case it would not.

0 0
replied on April 8, 2019

I seem to be running into this issue as well. 

We get this

And then we check our cookies on another tab and we get this

It is conflicting information

 

0 0
replied on December 15, 2020

This is also affecting us. Any update? Firefox for some reason is not affected.

0 0
replied on September 8, 2021

I also have new users that receive this message when using Chrome or Edge.

0 0
replied on August 26, 2022

I am seeing this in our v11 environment still too. internal and external weblinks

 

0 0
replied on January 24, 2023

We are also experiencing this issue. Has anyone found a solution? 

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

Sign in to reply to this post.