Julsfels
Member
Hello,
I tried the optimization for attachments yesterday evening on my test database. As a result, the overall attachment size went from 650 MB up to 732 MB, which is not my intended result.
I don't mind the test system, but on the productive system we have 15 GB attachments. Maybe it`s because we are forcing our users to upload medium size jpgs, and then the conversion to webp results in larger sizes, I don't know.
My question is: would it be possible to save the attachments folder and the table content of xf_attachment_data, and, if the size increases, just replace the attachment folder with the old one and replace the table content with the old one, or does the rebuild attachment optimization process changes even more that I have to track and save?
Thanks!
I tried the optimization for attachments yesterday evening on my test database. As a result, the overall attachment size went from 650 MB up to 732 MB, which is not my intended result.
I don't mind the test system, but on the productive system we have 15 GB attachments. Maybe it`s because we are forcing our users to upload medium size jpgs, and then the conversion to webp results in larger sizes, I don't know.
My question is: would it be possible to save the attachments folder and the table content of xf_attachment_data, and, if the size increases, just replace the attachment folder with the old one and replace the table content with the old one, or does the rebuild attachment optimization process changes even more that I have to track and save?
Thanks!
