Welcome to our Support Portal › Forums › WooCommerce Personalized Product Options Manager (PPOM) › Order search in Woocommerce not working
Tagged: cropper ppom pro
- This topic has 4 replies, 2 voices, and was last updated 1 year ago by nmedia.
March 7, 2022 at 6:27 am #133371
we use ppom pro to collect image (cropper) and data (fields) for creating access cards to our swimming pool.
two errors are occurring that seem to be related to the cropper/collected images
- this year in WooCommerce if we search orders we are getting errors that too much memory is used and search cannot be performed
- on products with multiple cropper fields, all buttons disapear when one image is loaded, so only one image can be set and the other cropper buttons disappear
That results in that our customers are having a very hard time uploading images and when they have the images placed and press the place order button, the order takes a while and then the page is reset and no order is placed in the cart.
The php memory is 1024 so that should not be the issue.
Is there something we need to do in order to get this fixed or will these be fixed with the next update?March 7, 2022 at 6:48 am #133372
ps the search error only happens when ppom pro is active. Which the ppom pro plugin deactivated (and the ppom plugin active) there is no issue.March 10, 2022 at 6:53 pm #133879
I did a bit research and it appears that the images of the ppom pro field ‘cropper’ are also added in the ppom add-on field in the database. That increases the size of the database enormously.
image of PPOM PRO meta field
Looks like the images is saved in the dbase as BASE64 format.
Is there a way to not have this data added in the dbase or erase that information from the database after the order is completed?March 11, 2022 at 8:18 pm #133936
cleared 1043 database cells from the table: wp_woocommerce_order_itemmeta
cells: _ppom_fields (with every order there is one of these cells filled with a huge amount of data of all the ppom fields for that order, included the images)
today one order came in and the summary _ppom_fields of that order was again filled and that single cell took up more than 5MB!
The question is:
Is there a way to exclude the BASE64 format of the images being saved in that database?
For now I will empty that single cell with every order that comes in but of course that cannot be the way it should be.
Please reply to this topic so I can repair this insanity.March 12, 2022 at 1:34 pm #133952nmediaKeymaster
we have noted it down and working on this and will be back with fix.
- You must be logged in to reply to this topic.