Is it fraught with something to slip the enveloped upload / iblock?

Question

1C-Bitrix

Created a copy of uploud/iblock.
Randomly converted all images in it, preserving all file names.
Removed resize_cache. Slipped this updated upload / iblock. Everything is generally normal. Images are given to the browser new.
I noticed one drawback so far: In the admin panel in the product card, information is displayed from old files (before conversion), namely, information about the volume and file name (not a link to iblock, but the name that the file had on the manager’s computer, at the moment when he uploaded this photo through the admin panel).
The question arose, but will some other more significant problem come up? As I understand it, when uploading images through the admin panel, the scripts work out and add information to the database, in contrast to the direct replacement of photos using OS tools.

Answer 1

Not much from my experience with pictures in Bitrix.
1. Don't remove resize_cache as you can get a bunch of 404 errors from search engines. Pictures are indexed, and will be created only when there is a hit where there is a resize. Plus, if you change the size of the resize, some will not be created when.
2. Pictures in resize_cache can be "tormented" as you like. For Bitrix, only the presence or absence of files is important. If the file does not exist, it will create it again.
3. If you have your own vps or server, then it is very easy to optimize images in resize_cache with a couple of commands in the console.
4. All pictures for infoblocks are registered in the b_file table, where the resolution and size on the disk are saved.
5. Accordingly, if they are resized or run through jpegoptim or optipng, then it is better to do it with a script that will update the new sizes in the database.

Answer 2

better go back and use modules for optimization