This topic is locked
[SOLVED]

Paging Found Records - URL Construction Error

3/6/2026 17:34:51
PHPRunner General questions
S
salus2 author

When I search databases for records the first page of results will have a URL like "https://customdataservices.net/bicycleshop/customers_list.php?qs=mo&criteria=or".

When I click the pagination buttons to go to the next record, the URL shows "https://customdataservices.net/bicycleshop/customers_list.php?goto=2" instead of the correct "https://customdataservices.net/bicycleshop/customers_list.php?qs=mo&criteria=or&goto=2" which gives the next page of found records.

It seems to work correctly on some databases but fails on others. Any idea what causes this problem?

ChatGPT 3/6/2026

The issue you're encountering with pagination in PHPRunner appears to be related to how the query string parameters are being managed during pagination. Here are a few potential reasons and solutions to consider:

  1. Session Management: Ensure that the session is correctly maintaining the search criteria across different pages. If the search parameters are not being stored in a session or passed correctly, the pagination may not have the necessary context to append the query string parameters.


  2. URL Rewriting: If your application is using URL rewriting or if there are any custom URL settings, it might affect how parameters are appended. Make sure there are no conflicting rules or settings in your .htaccess file or in the PHPRunner configuration.


  3. Pagination Settings: Check the pagination settings in your PHPRunner project. There might be an option that controls how pagination behaves when there are additional query parameters. Ensure that the setting to retain search parameters during pagination is enabled.


  4. Custom Code: If you have added any custom code or scripts, ensure that they do not interfere with the default behavior of PHPRunner. Look for any JavaScript or PHP code that manipulates the pagination links.


  5. Template/Skin Differences: If you are using different templates or skins for different databases, ensure that they are configured consistently. Sometimes, templates may have different settings or behaviors regarding query parameters.


  6. Database Configuration: Since you mentioned that it works correctly on some databases but not others, check the configuration of the databases where it fails. There might be differences in how the search fields are set up or how the results are being handled.


  7. Debugging: Use browser developer tools to monitor the network requests when you perform the search and navigate through the pagination. This may help you identify where the parameters are getting lost.



Suggested Solutions:

  • Update PHPRunner: Make sure you are using the latest version of PHPRunner, as updates often fix bugs and improve functionality.


  • Check Documentation: Refer to the PHPRunner documentation for any specific configuration options related to search and pagination.


  • Contact Support: If the problem persists, consider reaching out to PHPRunner support. They may have more insights into the specific behavior of your version and setup.



By systematically checking these areas, you should be able to identify the cause of the issue and implement a solution.

S
salus2 author 3/6/2026

The databases are all on the same server, using the same .htaccess, all configured to utf8mb4_unicode_ci. You can see the problem if you perform searches using the links below...

This works correctly...
https://calculationforms.com/ContactsList/customers_list.php

This demonstrates the problem...
https://customdataservices.net/classicmodels/customers_list.php

Attached is the .htaccess file stored in the public_html directory that contains the ContactsList and classicmodels directories...

I'm using PHPRunner 11.2 Enterprise build 44147

.htaccess
S
salus2 author 3/6/2026

My bad, it was the .htaccess file. I deleted it completely and all databases work correctly now on this server.