Hi Fokion,

1. Unfortunately, we don't have a built-in way to keep the editing modal open after you press the "OK" button to finish editing of that specific row.
   That is because when we use the modal for editing and we choose one row - it closes by default when we finish editing the chosen row.
   
   
   The only way to technically keep an editing modal open is if you use our 'duplicate row' feature. It can allow you to duplicate a row - if you need to make a new row with similar data and perhaps only change a part of the data, etc ,as explained per this Documentation.
   
   
   So for example, during the row duplication - if you hit 'apply and add new', then it edits the current row and duplicates it, to allow you to keep editing like that - but then again, when you hit 'submit', that ends the editing and closes the modal.
   
   

   

   So we don't have an ideal solution for your desired use-case from the native options.
   You can suggest it to our developers, though - they will do their best to make a solution in the future.

   Please feel free to search on our suggestions page, 

    to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

   You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

   and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

    

   If you have coding skills and wish to try to make a custom solution now,

   you can check out our available hooks for Developers on this documentation and see if you can find any hook that might help.

   We also added this new developer's handbook, which can allow users with coding skills to make custom add-ons.

   Our developers will keep adding more custom hooks/examples there over time.

    

   Please be advised that custom solutions with hooks are not included in our support.

   You can also research resources such as Stack Overflow to see if any other user perhaps found a workaround.

   ( We do like to give examples for certain solutions, but for this use-case, we, unfortunately, don't have anything yet)

   
   
   
   

Hi Fokion,
Apologies, I did not comment on your second question :

2. Alternatively, is there any way to call the save function using AJAX or some other way?

It probably can be done with some custom work, but our developers are very busy at the moment, working on some priority tasks and fixing bugs and issues with our plugins, so they won't have the time for custom work in the near future.

If you have coding skills, you can refer to the available hooks from our Documentation sections for developers and see if any of the available hooks could help for a custom solution.

I hope that helps.

Hi Fokion,

I will ask our developers if they can provide further advice on this ticket - they will go through everything we discussed so far.

We will do our best, but can't promise anything.

As soon as they find the time to check this out, I will report back.

Thank you for your patience.