Hi Jay,
Thanks for your compliment! 😊
Is your question related to a project or a publication?
Admins can export full tables from the dashboard using the Data Explorer. This is documented here:
https://wpdataaccess.com/docs/documentation/data-explorer/actions/#export
Full table export is not supported for projects. You can add it if you’re familiar with WordPress hooks.
Publications do not contain a full table feature by default, but you can customize a publication and add your own export button (requires a premium license).
Custom buttons are documented here:
https://wpdataaccess.com/docs/documentation/data-publisher/custom-buttons/
Example code is available on the Code Manager website.
Does this help?
Best regards,
Peter
Peter, Thanks for your response.
I am kinda new with this product. So far, I have been creating templates and then applying templates to tables in data projects. Then I take the diehard shortcode and insert them into WP pages. Then add the pages to WP menu. This whole setup works great so far.
The export capability is available on the frontend when a user selects individual rows. However, they can’t export the entire table.
When you say “you can add it if you’re familiar with WordPress hooks” are you talking about frontend or backend? Can you give me some details on how I should create hooks for that?
If possible, I really wish you could improve the existing export feature. When rows are selected, the user can export the selected rows. But if no rows are selected, then export the entire table. To prevent users from exporting huge tables, you can add an option to enable and disable the full table export as part of the setting.
Thanks.
Jay
Hi Jay,
>>> When you say “you can add it if you’re familiar with WordPress hooks” are you talking about frontend or backend?
Both
>>> Can you give me some details on how I should create hooks for that?
Of course! 😊
Here is the documentation for hooks and filters:
https://wpdataaccess.com/code/
For your use case you might want to have a look at these hooks:
– wpda_before_list_table (add custom code before a list table)
– wpda_after_list_table (add custom code after a list table)
The wpda_before_list_table hook for example allows you to add your own code to the top of a list table (back-end + front-end). You could for example add a button “Export all rows” to call your own request that handles your export.
Is this enough information to add a custom export?
Best regards,
Peter
Thank you for your response. I viewed the link. Since I am not a coder, it’s a bit challenging to me. I think the reason most people love WP Data Access is that it’s a GUI-based, easy-to-use user interface. The coding option is certainly nice for people with coding experience, I will do my research, but I am not confident that I can do it. Thanks anyway.
