Were you able to figure this out? One thing that can cause problems like this is page caching, you should exempt the page from page caching if the data is dynamic.
Did not have a caching problem before. Whenever I added a record, it immediately showed up when the pdb_list was run. But, I flushed site cache & flushed browser, then ran the list page…no joy. Just to verify, I deleted one of the old records, then ran the pdb_list, the deleted record was immediately missing. But, none of the records entered on 4/23 show up. Still see them in the PDb Admin List by running by Type Designation (pdmrdb_type) set to Log (the record type) and having Date Recorded in the list. Opened every record recorded on 4/23 and verified that each of the 5 fields had data in them.
If the record is indeed getting added to the database, and seems complete then really the only thing left is to look at the configuration of the list shortcode to see if those records are excluded for some reason.
Another possibility is that the new records are on a second page of the list (which is usually paginated according the the “Records per Page” configuration or in the shortcode).
If you want to get the details, I suggest you turn plugin debugging on, clear the log then display the list. In the log you will see the query that was used to build the list. That will tell you why the records are not appearing.
I will do what you suggest, but all records use same 5 fields. No changes in the page structure. Output is sorted descending on ride_date. 4/23 data has the latest dates, so should be at top of list. Still in test phase, amount of data does not scroll the list to another page.
OMG, I found the problem. When I entered that data, I had just come from hours of working with a spreadsheet where I entered dates for 2023 as 23. No problem in the spreadsheet. I found out the hard way that it doesn’t work with your database and WordPress. The dates were being recorded as 0023. When I looked at the recorded fields I didn’t notice the zero in place of the 2.
My sincere apologies for this. It was just doing what the stupid operator told it to do.
