This topic is locked

May 2, 2025. Version 11 maintenance release. Build 43304.

5/2/2025 12:20:24 PM
ASPRunner/PHPRunner change log
Sergey Kornilov admin

May 2, 2025. Build 43304.

Version 11 update

This update applies to both single developer and multi-developer editions of the software. If you use MultiDev edition of PHPRunner or ASPRunner.NET, we recommend reinstalling both server and client parts.

Version 11 Frequently Asked Questions

Fixes:

  • fixed Inline Add feature
  • fixed Show/hide fields feature;

Customers who purchased less than twelve months ago can download this update via the control panel. Proceed to 'My purchases' and check 'Reg info' link next to your latest purchase.
Customers who purchased more than twelve months ago can renew their maintenance using links below:
PHPRunner maintenance
ASPRunner.NET maintenance
ASPRunnerPro maintenance

Davor GeciDevClub member 5/2/2025

Just to add for myself for the future a description of how initial_fields works now:

Since PHPRunner is ideal for database applications where we add a lot of new fields to existing tables, in previous versions ( before v11 Build: 43304) the "initial_fields" setting worked a little differently when we added new fields.
So when we added new fields, regardless if those fields were not marked to be displayed in "initial_fields", the web application displayed them in the list page.
This was a problem because we are constantly adding a lot of new fields to new versions of the app (both hidden and system fields, or if we initialy started the app with 5 fields, and with time added 50 new fields, we don't want to automaticaly displey them all), and if we didn't select them to show initially in "Initial fields", or the user didn't choose them, these fields should not appear by themselves.
Now with v11 and Build: 43304 that behavior is changed.

Now if we use "initial_fields" the web application applies it like this:

If we use Pages > List page > Settings > Allow show/hide fields on page > Initial fields
If the user does not touch the visibility of the fields in the list page, the application shows the fields selected by the developer in initial_fields. When adding new fields or when changing initial_fields, if the user did not touch visibility, the application still respects what the developer chose (it no longer adds new fields automatically, but only those fields that were selected in initial_fields).

However, if the user has adjusted the visibility of the fields in the list page, regardless of how the developer defines initial_fields, the application displays only those fields that the user has selected. If he wants the new fields added in the meantime with the new versions to be displayed, he must add them to the list page by selecting them in the dropdown.

If we want the user to be able to reset the visibility of the fields in the list page to the default value, we must create a section in our application settings and add a button that deletes the record in the table .... settings with Type = 5 and username = current username and Table = desired table
If we want to clear the column width settings in the list page, then Type = 2*