I have bricksforge, ACF and Admin Columns Pro installed. I have a CPT with a custom field “date_of_donation” that is of the type “date” with the format “d-m-Y”. When brf creates a new post and saves the date to that field, it shows on the backend properly, but it’s unfilterable and unexportable by Admin Columns. The posts that are made on backend using vanilla acf are filterable and exportable by Admin Columns. I have checked everything and everything is how it should be.
Steps to recreate:
1: Create a CPT and assign a “date” field with “d-m-Y” format in ACF to that CPT
2: Create a frontend pro form with a “date picker” field with the format “d-m-Y” with action “Create new post” and save the date to the acf field with the format “d-m-Y”
3: On the backend try to filter or export that post to csv using the date field that acf created using admin columns.
I know it a brf issue because posts created using vanilla acf on the backend work perfectly and are filterable and exportable using admin columns.
As we do not have access to Admin Columns Pro, we cannot reproduce this. I assume that this is more of a compatibility feature request than a real bug. Please send us access (via ticket) to a page where you have set up the configuration. Then we can take a look at it.
This isn’t a compatibility issue I think. I have a feeling that bricksforge pro forms isn’t saving the data to the acf “date” field properly. Admin columns doesn’t have any issues when the post is created or updated using vanilla acf on the backend. It’s only the posts created using brf pro forms that have these issues. Maybe pro forms isn’t saving the date like how acf saves it. Acf has documentation supporting my claim.
Check the notes section.
Maybe pro forms isn’t saving the date as"Ymd" which is the format which both acf and wordpress use to saves dates in the database.
This applies to the “date - time” too which has its own format which wordpress uses to save date-time in the database. Again check the notes section in ACF | Date Time Picker
If you need direct and official help, a ticket would be the right place, as we also need to check your license first. Also, to be able to debug, we would need access to yor site.
