DataAssist Search Wizard Next button not working

Hi. I'm trying to create a search page using an existing form on another page. When I specify the page and the form the Next button doesn't work. Any ideas? I should mention that this is on an old site still using MySQL and PHP 5.6.

Can I get a copy of the page? Better yet, can I get FTP access to the site and steps to reproduce? It probably has something to do with the page, but I'll have to debug it to find the cause and solution.

I'm running a test site under MAMP and linking to the live database so ftp isn't possible, but I've attached the page. The file searchresults.php is the original which still works as it did when first created, but modified to only return 8 results. I added paging and the links all return an odd set of results that don't match the query, even though the original set of results is correct. When I double-click the DataAssist Search button to edit the panel is blank. The other two are new pages to replace the first one, as the panel didn't work, and this time the panel appears, but when the Existing search page is set to nusearch.php and the form set to searcher, the next button in the panel does not advance to allow me to set the search criteria.

Can you send me an export of your database for the tables: gal,shop,size

I'll need that to set up a test environment to reproduce the issue... Either that or send the connection file as a private attachment and I can link to the live database as well.

I don't understand which of the two results pages I should be using to reproduce the problem. Are you updating these to MySQLi or did you want to keep them MySQL?

Please provide steps to reproduce any issues you are running into. I think there are two:

1) Search results are incorrect
2) Blank database search window

Steps should be something like:
Open this page in dreamweaver, or open this page in your browser, click this button or that, this is what I expect to see... this is what I actually see..

That is what I will need to reproduce the issue, and then I can fix it.

Here are the files. I'll post again with details.

It has to stay as MySQL for now and I need to get the paging sorted ASAP as the number of records and images being returned is too many for my service provider's reasonable use policy. Paging works fine on other pages (boys shoes, girls shoes etc.) it's just the search results page where it's an issue, presumably because of the complex search query.

Forget the "nu" pages. I'll just work with the existing search and search results pages. I thought I could resolve this by starting fresh, but just had the same issues.

The images are named to show what stage they happen.

When I use the Wizard I can't progress using the "Next" button and when I access from the Server Behaviours Panel I get a blank window.

Any help much appreciated.

I just did an update to the extension to fix this problem. Please reinstall and let me know if you run into any problems.

Everything was going fine, but suddenly the interface crashes, sometimes on edit, sometimes on new and when it does work it places a number in place of the column name both when editing and adding a new rule.

I'm able to reproduce the issue with numbers showing instead of column names. I'll work on it and get an update to you as soon as possible.

The issue is that you have a form element named "size" on your search page. That is a reserved word in javascript and html and causes issues in dreamweaver.

If you just rename it to "sizes", or anything else that isn't a reserved word, then it will fix your issue.

You should be careful using reserved words. I see you also have a column in your database named "range", which is a reserved word in MySQL. It could come back to haunt you. Anytime you name something like a form element, database column, or database table, using a function name that exists in the language that will refer to it, you can run into difficulty.

HTML reserved words are javascript reserved words, and the attributes of tags. Size is already an attribute of an input element. That is why it can't also be its name:
https://www.w3schools.com/tags/att_input_size.asp

Javascript reserved words:
https://www.w3schools.com/js/js_reserved.asp

MySQL reserved words can be found here:
https://dev.mysql.com/doc/refman/8.0/en/keywords.html#keywords-8-0-detailed-R

It can be difficult to keep track of all of the reserved words, so I usually don't use actual words for form elements or column names. I use compound words, which will never be reserved like : "ProductSize" and "DataRange". If you always use two words, you never have to worry they might be reserved. You can also separate them with underscores.