johans
Forum Replies Created
-
Thank you for the help! Creating a view and using it in a Data Table app solved the problem, so I don’t need to use the Chart.
Thanks, I guess modal forms is enough at this point, but it would be handy if it would be possible to somehow jump to the edit page in a form. Anyway, thanks for now.
Thanks Peter, I built a fully operational database with different relationships between tables with the new App builder, and it works really well!
But for the front-end it seems some features are not fully implemented or at least not documented. For example, I found out I can use filters on the wpda_app shortcode, which is great. If I create an app for the table projects, is there any way I can use a wpda_app shortcode for the app to jump directly to the edit page of a specific row in the table, instead of listing all the rows?
Or could I use hooks in one table to navigate and filter another table on the same page?
Thank you. I’m learning hooks and it seems like an easier option than to use the old legacy builder, but I’m running into some problems of how to implement it for a specific case.
What I’m trying to do involves breaking up the user interface a bit, with a WordPress front-end with a single “Project edit” page containing a simple sidebar listing the names from a table projects, and next to it a data administration app for a row in the table projects + below a chart table with a list of all costs for the project. When clicking on a row in the sidebar, the data administration app jumps to edit that project and lists the costs of the project. So, basically I want to connect three apps on the same page with each other.
My idea is to set up the sidebar as an app that uses a hook to link projects.name to the “Edit project” page with a PHP query containing projects.id. Possibly I could get the query with the Code Manager app, but how do I then pass projects.id to the shortcodes of the apps? Or are there simpler solutions?
Hi Kim,
Thank you for the reply. I must have done something wrong specifying the many-to-many relationship, because when I defined it again, everything worked as expected.