warning, translatepress will duplicate your entire image gallery!

Hello,

We will stick to the existing way of just adding the image size all the time.
There is no real concern about performance because the image size we register is really small so it doesn’t occupy a lot of space on servers.
The additional image size will be used in srcset for all images (non-TP too) but that does not increase the site’s page loading time.

However, you can achieve the restriction through a custom code:
1. Create an empty plugin like this: https://gist.github.com/sareiodata/76f701e01db6685829db

2. Add the following code to the end of it:

add_action('after_setup_theme', 'trpc_remove_trp_image_size');
function trpc_remove_trp_image_size(){
remove_image_size( 'trp-custom-language-flag' );

3. Install this plugin via FTP (copy it inside wp-content/plugins) or create a zip archive with it and install it via the WordPress plugin upload functionality

Kind regards,

Anca

Hello,

Congratulations! It is admirable how you have avoided answering the questions posed. Instead, you talk about things that have nothing to do with the issue raised ??

I loved how, despite the fact that no one here has talked about “performance” or “loading speed”, you put all your answer around this fact.

The additional image size will be used in srcset for all images (non-TP too) but that does not increase the site’s page loading time.

Oh, and thank you very much for thinking that maybe there are people who do not know that stored images (that are not loaded), do not affect the loading speed! It seems obvious to everyone… but of course, you never know!

There is no real concern about performance because the image size we register is really small so it doesn’t occupy a lot of space on servers.

Exactly the same with the size of the images… Thanks for explaining that an image of 18px x 18px occupies little!

And finally, thank you very much for giving us the code to avoid the generation of thumbnails… Although there are several plugins and ways to do it (just ask Google or chat gpt for it) you have bothered to put a code. An admirable job. Again, thanks for everything.

Well, now that we all know that thumbnails are indeed very small, and that the files stored on the server don’t affect loading speed, and we also know there are codes and plugins to prevent thumbnail generation in WordPress… let’s try to get back to the original topic:

Is this behavior necessary and user-friendly?

You mentioned, “We will stick to the existing way of just adding the image size all the time.” But this is not accurate. There are other ways to handle this, according to www.remarpro.com. The issue here is not “how to create thumbnails” but rather whether it is necessary to “create thumbnails for the entire gallery,” “without notifying the user,” and “without offering an option to avoid it,” especially if no one is ever going to use a thumbnail-sized flag!

For example, here are a few alternatives, all of which are consistent with www.remarpro.com standards:

1. Simply making it optional. Let the user decide whether they want to generate 20,000 thumbnail images for their entire gallery.
2. At the very least, notifying the user that your plugin will create thumbnails for their entire gallery, so they can choose not to install it.
3. Or asking the user to upload custom flags in the required size (or resize with css..)

But, as another user who previously complained about this issue already said:

You are the boss. Do how you want. It was just a feedback and tried to understand what makes it indispensable. I just mentioned that this non-vital feature is nonsense.

@birtakimseyler says 1 year, 10 months ago

I had hoped they would abandon this nonsense. However, it seems that the issue is still being defended with the same stock phrases even after a year: “We will stick to the existing way of just adding the image size all the time.”

The database of my website, which has tens of thousands of media assets, was turned into garbage because of this. We were using a service that sends media assets to a CDN and charges based on the number of files, and these unnecessary files caused us a financial loss. Even if you cancel the plugin, the garbage will still remain there.

When I reported this issue with all good intentions, I was given the same response as you did. A much more elegant and simple solution could have been found, yet I’m still asking: Why is this insistence so crucial, and why is it irreplaceable? And please, whoever is responding on behalf of TranslatePress, kindly show this message to your manager.

Anyway, there are aspects of TranslatePress that I like. However, this situation always drives me to want to get rid of the product at the first opportunity. The moment I find something better, I will say goodbye to it.

I’m interested in hearing more from Translatepress about this issue, since I use it on many sites and hadn’t realized the problem.