This topic is locked

Bug in simple search

6/20/2009 11:44:46 AM
PHPRunner General questions
J
Jepsen author

There is a bug in simple search which has been giving me grey hairs. I am now absolutely confident it is a bug and not me doing something wrong
In my tavle, I have included all fields in the simple search on the search page.
If I am searching for in specific fielf for i.e. my first name, PHPR generate a search string like this:
First name contains "morten"
/_medlemsregister_list.php?a=search&value=1&SearchFor=morten&SearchOption=Contains&SearchField=fornavn
It works perfectly and my name also also pups up in ajax.
However,
When I try to find my name in "Any Field" contains "Morten", Ajax finds nothing and the result returned is the entire database. Here is the search string returned from PHPR:
/_medlemsregister_list.php?a=search&value=1&SearchFor=morten&SearchOption=Contains&SearchField=Alle+felter
As you can see, PHPR hare giving this parameter: "....... &SearchField=Alle+felter" but this is incorrect. "Alle+Felter" is the danish menu point for All Fields.
The correct string should be looking like this:
/_medlemsregister_list.php?a=search&value=1&SearchFor=morten&SearchOption=Contains&SearchField=
I hope you could fix this asap as I cannot upgrade my databases to loose simple search.

J
Jepsen author 6/22/2009

Dear admin,
have you overlooked this report, or am I completely mistaken?

Sergey Kornilov admin 6/22/2009

I recommend to post your application to Demo Account (use 'Demo Account' button on the last screen in program). Then open a ticket at http://support.xlinesoft.com sending your Demo Account URL for investigation.

J
Jepsen author 6/25/2009

I have found the problem.
I have made a brand new application in PHPR 5.1 and now the simple search works
The sites where I have the problem are all old sites made in PHPR 5.0 or one of the 5.1 betas. It appears that you have to delete the old output files before you re-build. If not some of the files are not updated and I experience search problems.
So it is not enougt to run 5.1 on tour old application, apparently, you also have to delete the old output prior to building your PHPR 5.1 application.

It is not supposed to be easy <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=42143&image=1&table=forumreplies' class='bbc_emoticon' alt=';)' />

Z
zico 7/21/2009

I'm seeing the same problem, exactly the way you describe it. Using PHPRunner 5.1 b2503.

Wiping out the build directory did not solve the problem for me... The search "any field" + "contains" always returns the full list of records. works fine with new projects created on the same version, but not on applications migrated from an older version.

J
Jane 7/21/2009

It's difficult to tell you what's happening without seeing actual files.
Please publish your project on Demo Account and open a ticket at http://support.xlinesoft.com sending a URL to your pages along with instructions on reproducing this error.

Z
zico 7/21/2009

Unfortunately I can't publish the project due to non-disclosure (confidentiality) demands by my client..

Is there any additional information I can send you without disclosing the entire project that will help you troubleshoot?
The problem is with the basic search function:

  • When I use the basic search but look in a specific field the function works great.
  • When searching for "any field" + "contains" + any string, the function returns the full list. and also when I search "any field" and use "equals" or "contains" or "starts with" or any of the other options on the drop-down list, I always get the full list of records, so I suppose this is where the problem lies...
    I appreciate any effort you can make to try and help!

Sergey Kornilov admin 7/21/2009

We don't need your confidential data.
You can send us project directory zipped, script that creates database tables and some sample data so we can troubleshoot it.

Z
zico 7/22/2009

An update - after wiping out the entire work directory (except for the *.phpr file) the search function is indeed working again. Of course it also means that I lost all the previous page designs and additional code I added on the html itself and it now has to be re-written, but at least it's working...