You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Images which afterward will be removed from the Builder Form, should be deleted from "ir.attachment" afterwards.
This prevents polution and orphanes in the "ir.attachment" table.
Current analysis:
Regarding Orbeon, there's no (HTTP)-request - to the Odoo persistence service - which handles the deletion of these images.
There's solely the (HTTP)-request /crud/orbeon/.../data.xml - Which for which images either exist or not in the data as URL-path.
A possible approach would be, to determine and delete the "ir.attachment" (images) for the Builder Form which don't exist in the (XML) data by URL mentoined above in bulletpoint 2.
It would also be a good idea to store the Orbeon control-/fieldname for the image on the "ir.attachment" model as well. Which could be implemented in the function handle_binary_data()
The text was updated successfully, but these errors were encountered:
Images which afterward will be removed from the Builder Form, should be deleted from "ir.attachment" afterwards.
This prevents polution and orphanes in the "ir.attachment" table.
Current analysis:
/crud/orbeon/.../data.xml
- Which for which images either exist or not in the data as URL-path.A possible approach would be, to determine and delete the "ir.attachment" (images) for the Builder Form which don't exist in the (XML) data by URL mentoined above in bulletpoint 2.
It would also be a good idea to store the Orbeon control-/fieldname for the image on the "ir.attachment" model as well. Which could be implemented in the function
handle_binary_data()
The text was updated successfully, but these errors were encountered: