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

Question

Question

Cookies are not enabled for this website. Cookies must be enabled in order to sign in to Weblink 10

asked on May 25, 2022

We just deployed our Weblink 11 server and we have users who've been using it since, but periodically report, "Tonight's Laserfiche error is 'Cookies are not enabled for this website. Cookies must be enabled in order to sign in to Weblink 10". Have a good evening!'"

I know the problem is the "&cr=1" that gets appended to the url automatically. When the user makes their shortcut or saves it as a favorite it includes that, and will probably include the "&cr=1". We have a public weblink and every link to it on our website does NOT include that, but because of it being automatically added to the link, all of the external entities that use it probably save it with that, so just telling the users to remove that is difficult.

Is there a way to alleviate this? Can I do some sort of redirect in IIS? I found this question which seems relevant but at the bottom it says it's been incorporated into Weblink 10.  https://answers.laserfiche.com/questions/69116/Preventing-False-License-Usage-in-WebLink 

It also looks like people have been complaining about this for at least two previous versions.

Weblink 9: https://answers.laserfiche.com/questions/77039/Weblink-displaying-Cookies-are-not-enabled-for-this-website-Cookies-must-be-enabled-in-order-to-sign-in-to-Weblink-9-error-message#158552

Weblink 9 and 10: https://answers.laserfiche.com/questions/164945/Cookies-are-not-enabled-for-this-website-Cookies-must-be-enabled-in-order-to-sign-in-to-Weblink-9#188315

I don't know how to mitigate this. It's frustrating.

Steve

5 0

Replies

replied on August 15, 2023

Hi Steve,

Did you ever find a resolution to this?

0 0
replied on August 16, 2023

Unfortunately, I don't remember if I did anything specific to resolve the issue. 

Fortunately, I can't duplicate it currently. 

Looking back through my emails, one thing we did do after I reported this problem is to apply a hotfix (through our VAR) that was released on or about 5/27/2022. It was for a different problem, but it may have helped - or may have had no influence whatsoever.

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

Sign in to reply to this post.