Multi Editor Bubble
Multi Editor Bubble
rpmccormick
Posts: 136Questions: 18Answers: 0
in Editor
I am wondering if it is possible to do Bubble edit with 2 fields from different editors?
Instead of clicking the top half for the Bookings editor, and the bottom half for the RoomStay editor... it would be better to popup both dropdowns in one bubble... but they edit different tables.
This question has an accepted answers - jump to answer
Answers
Different Editor instances and different tables, no sorry.
It can do multiple fields in a single Editor instance and table though. Example here.
Allan
Ok Allan, not surprised. Might be possible, but probably not worth the effort.
I use multi-fields in bubbles all over the place already, but this is once case where I want 2 fields from 2 different tables.
I'm thinking I could somehow launch 2 different bubbles, and then somehow merge them in to one bubble graphicly, and then submit them together to the 2 different apis. Might work on that some day. Not important, just would be slightly better for my particular case.
I suppose another way might be to create a new editor instance that is based on the VIEW already used on this table... and then have some crazy editor PHP code that doesn't update the VIEW (of course) but instead applies the edits to each of the tables that make up the VIEW (that would be really awesome all over my system actually... one editor instead of one per joined table... and then I could actually use table: on the editor instead of always doing everything in stand-alone mode so that I can edit so many joined tables.
...is something like that possible?
(I almost hope the answer is no... because if you can have an editor submission be broken up into multiple editors for multiple tables... then my whole system of using VIEWs M-Joins and StandAlone that I have been perfecting for years is worthless.)
Editor only allows one bubble editor to be visible at once. Even if you had multiple instances, it wouldn't be possible I'm afraid.
That said, you could use a single instance with all of the fields you need, and then use the API to set the values as required and on submit use some logic in the submit handler to split it out.
So visually it can be achieved. Is it worth the dev time? That's up to you
Allan
Ok... and there is no way (no prior art anyway) to create an editor that uses tons of fields from a VIEW for display, but then chops it up on submit to do multiple table UPDATEs?
PS: I get your approach, and that is a good idea... if I decide it is worth the dev time
No, sorry. The closest is this example but it is updating a single table.
The Editor server-side libraries can do multiple updates using joins, but I generally recommend against that, preferring a child editing approach.
Allan