By default, the plugin generates alt text in the site’s language. In the Media Library there is a quick action for simple, one‑click generation.
If you need more control, you can use the bulk generator (also for a single image). It allows you to provide a custom prompt, for example to generate alt text in a different language or with specific requirements.
It doesn’t seem to be an issue with my plugin’s implementation – the extend() is done correctly and works fine when Smush is not active. From what I see, Smush overrides wp.media.view.Attachment.Details in a way that bypasses any previously-extended render() methods. This means my code never runs even though it’s added properly.
While Smush is popular, popularity doesn’t always guarantee compatibility. In this case, their override approach might be the cause of the conflict. I’d suggest reporting this to the Smush developers so they can ensure their extension preserves previous modifications. For reference, here’s my code that hooks into the media modal:https://github.com/android-com-pl/wp-ai-alt-generator/blob/main/src/media/media-modal.ts
This reply was modified 8 months, 3 weeks ago by Rafał Całka.
Yes, my site works, but I’m seeing over 100 warnings in Query Monitor and Sentry that weren’t there before updating to version 7.0. The key issue appears to be that the plugin is using is_file() on URLs like https://eeeee.aaaaaa.com/… and CSS content, which will naturally fail with open_basedir restrictions since they aren’t valid server file paths.
@litetim I think there’s a misunderstanding about the problem. The issue isn’t that open_basedir is too restrictive – it’s that the plugin is trying to use file contents as file paths, which is incorrect behavior. This is a bug in how the plugin is handling file references in version 7.0. Disabling open_basedir would just hide the symptoms without fixing the actual problem. Could you please fix how the plugin processes CSS file references rather than asking users to disable important security features?
We plan to implement this functionality in a future update.
In the meantime, if you’re comfortable with some basic coding, there’s a workaround you can use. You can add the following code to your theme’s functions.php file or another file that you control:
Same problem. After upgrading to 2.7.8, when a user does not have a local avatar but uses Gravatar, the default Gravatar avatar is displayed instead of the user’s avatar, as if the user had no avatar set. The ‘Local Avatars Only ’ option is disabled.
After rollback to 2.7.7 this works correctly.
This reply was modified 1 year, 11 months ago by Rafał Całka.
@qtwrk Sorry for the late response. Clearing the Cloudflare cache helped previously. I’m now on version 5.7.0.1, but the optimization issue persists and hasn’t improved much. Currently, only 34% (22% was 3 month ago – see first post) of the images have been optimized over these three months. At this rate, it will take years to optimize them all. Something still seems off. Is there a way to fix this? Before version 5.4, I had 100% of my images optimized. It would be ideal to somehow restore the optimization data that was reset, rather than re-optimizing everything from scratch
I’ve noticed a problem in the database table wp_litespeed_img_optm. There are numerous empty records with post_id 0 and empty src:
There are about 15,241,411 of these on a total of 15,246,335 correct ones. Should I delete them?
There are also images that have src set but the post_id is 0:
Additionally, in the wp_litespeed_img_optming table, I see records with empty server_info. Should these be removed as well?
Report number: UJGRYHQP
This reply was modified 2 years, 5 months ago by Rafał Całka.
I have installed version 5.5.1 and now I have thousands of such errors:
Failed to download original images Images have changed since the original optimization request in node 81.31.156.245. 6 images in total, sample URLs: https://static.**************
This reply was modified 2 years, 9 months ago by Rafał Całka.
