Jump to content

Invalid Query after upgrade to Pro 1.8.2


Recommended Posts

Hi,

 

We are using Pro to run some keywork searches, and now trying to run a query, and now it tells me "Invalid query: *@xxxx*, where as this used to work before in 1.8.1. Why does this query not work anymore? Is there a syntax I can use to correct this. My keyword, which is part of a keyword list, wants to look for all email addresses at domain xxxx.

 

Link to comment
Share on other sites

Hi,

 

In the past, we received numerous complains about confusing results caused by incorrect syntax of queries from real-world keyword lists files. So, in the new release, we added a preemptive sanity check which validates every single query read from a keyword list.

 

Unfortunately, it turns out that this validation procedure misses the case of queries with wildcard characters in leading position. This will be fixed in the next Intella release which is just a couple of weeks away.

 

We are sorry for inconvenience.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...