My sincere apologies for the inconvenience caused.
We have recently received a similar report from another customer, even though this functionality was working correctly earlier. After reviewing the issue, we believe we understand the cause.
Reason for the issue:
To keep the plugin lightweight and performant, AIOVG loads its CSS and JavaScript files only when required. This approach works well on the vast majority of websites. However, we have noticed that certain themes or optimization plugins can interfere with this conditional loading, which may prevent our assets from being loaded correctly.
Permanent solution:
As a long-term fix, we are planning to introduce a new setting in an upcoming version of the plugin that will allow you to force AIOVG’s CSS and JS files to load globally, ensuring maximum compatibility across all themes and caching/optimization setups. Temporary workaround
As a quick solution, please add the following code to the bottom of your active theme’s functions.php file:
function aiovg_custom_register_styles() {
wp_enqueue_style(
AIOVG_PLUGIN_SLUG . '-public',
AIOVG_PLUGIN_URL . 'public/assets/css/public.min.css',
array(),
AIOVG_PLUGIN_VERSION,
'all'
);
}
add_action( 'wp_enqueue_scripts', 'aiovg_custom_register_styles' );
This will ensure that the required CSS file is always loaded on the front end.
We hope this resolves the issue.
Please let us know if the problem persists or if you need any further assistance—we’ll be happy to help.
Great, thanks it worked :).
