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

Question

Question

Search Results in Weblink

asked on February 15, 2019

Happy Friday -

I have been attempting to create a URL to return a specific set of search results for our website visitors. At first I received a "Cookies are not enabled" error and looked it up on LF Answers and found that the pesky "cr=1" was my problem. 

Now I'm having an issue where users follow the link and received the error "No results have been returned yet." . I'm kind of desperate to make this work - I'm filtering content based on a tag using the URL below. Could someone advise either on fixing this problem or an alternative method? 

https://records.athabascacounty.com/WebLink/search.aspx?searchcommand=%28%7BLF%3ATags%3D"Frequently%20Requested"%7D%29

Thanks

Allan

0 0

Answer

SELECTED ANSWER
replied on February 15, 2019

Does the following URL work for you?

https://records.athabascacounty.com/WebLink/search.aspx?searchcommand=({LF:Tags="Frequently Requested"})
It's possible that mixing encoding might be confusing the browser/WebLink combination.

Is WebLink configured for Windows Integrated authentication, or does it use a specific account to allow access to anybody who visits the site? If it uses a specific account, then check the access rights for that account.

When I was asking about the client, I meant either the desktop client application, or the web client. Meaning, if you do a custom search and something like the following, does it work?

 

Sorry for so many questions, just trying to walk through the possibilities.

1 0

Replies

replied on February 15, 2019

Does the user that WebLink is using to access the repository have access to the documents that you expect to find? Is the tag a regular tag, or a security tag? If you run that search query in one of the other clients as that user, do you get any results?

0 0
replied on February 15, 2019

They do have access. The tag is a regular tag and we only have the one client. However I tried the link with two external devices from out network and it worked fine. 

0 0
replied on February 15, 2019

No apologies necessary. I'm eager to learn and grateful for the assistance. The URL doesn't work for me, and I'm not clear about the setup for Weblink. I'm pretty sure it's a single account given it's the same access for internal and external users. 

I managed to get the search syntax to work within the Windows Client. 

0 0
replied on February 15, 2019

As Devin noted, your search syntax is only partially encoded. Try the following URL?

https://records.athabascacounty.com/WebLink/search.aspx?searchcommand%28%7BLF%3ATags%3D%22Frequently%20Requested%22%7D%29  

I have encoded the quotation marks around the tag name.

0 0
replied on February 15, 2019 Show version history

Thank you, however I was using the formatting given in the Laserfiche Help documentation. The link doesn't provide results, I will try troubleshooting it. 

0 0
replied on February 15, 2019

I'm also wondering if you could clarify about which portion is partially encoded. Should I be using a different type of reference to describe the tag? 

0 0
replied on February 15, 2019 Show version history

It was the quotation marks. You need to have everything encoded. That's why I suggested trying it with nothing encoded, because that's what works for us. It's all or nothing.

If you do a web search for "url encode" you can find tools that let you paste in an unencoded string, and get back the properly encoded version. That way you don't have to worry about missing something while doing it by hand.

1 0
replied on February 15, 2019

For comparison, your original URL, which has quotes around the tag name:

https://records.athabascacounty.com/WebLink/search.aspx?searchcommand=%28%7BLF%3ATags%3D"Frequently%20Requested"%7D%29

 

The URL I provided, which has replaced each " with %22:

https://records.athabascacounty.com/WebLink/search.aspx?searchcommand=%28%7BLF%3ATags%3D%22Frequently%20Requested%22%7D%29  

I recommend using an online tool when you need to encode syntax (and you don't have Web Access/the web client to generate the encoded syntax for you). Trying to manually replace it is tricky and tedious

Search for "URL encoder" and you should find tools; then, run it on the whole search syntax term.

1 0
replied on April 28, 2020

I'm running into a similar issue with Weblink version 10.2.0.264.  After encoding the quotes to %22, and pasting the url into Chrome and other browsers, it's reverting back to the quotes " - is there a fix for that? 

0 0
replied on April 29, 2020 Show version history

The conversion to " in the URL appears to be a display-only change that Chrome is making to the URL. 

Viewing the actual network traffic shows that the URL encoding is properly displayed, and I have verified that several searches still work as expected since Chrome isn't changing what is sent to WebLink.

Since the browser is making the display change as soon as you paste in the URL, before it is ever sent to WebLink, there is nothing Laserfiche can do --- but as far as I can tell, it is not causing issues with search.

If you are experiencing problems with searches, it is likely unrelated to the display change Chrome has released. To troubleshoot, we'd need more details on the specific search --- and I recommend opening a new post for that problem so it doesn't get lost here.

0 0
replied on May 1, 2020

That makes sense Brianna.  It ended up being a case-sensitive issue.  In the URL we had SearchCommand instead of searchcommand, that apparently needs to be lowercase.

1 0
replied on February 15, 2019

It seems to be working, thanks. 

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

Sign in to reply to this post.