Greg Ross

You can find the enqueue code here: https://github.com/toolstack/just-likes-and-dislikes/blob/f46a60ea968a50a60604c02421de704258f40d43/inc/classes/class-jlad-enqueue.php#L19

And the css load here: https://github.com/toolstack/just-likes-and-dislikes/blob/f46a60ea968a50a60604c02421de704258f40d43/inc/classes/class-jlad-enqueue.php#L31

The plugin doesn’t support doing that, and it wouldn’t be a good idea to block it. It doesn’t change often, but it does change with some updates, so you’d have to manually “fix” your style.css each time.

If you really wanted to do it you could probably write a plugin that hooks into the css loading routines in WP and removes it from the list, but that’s an ugly hack.

Modern websites use lots of small css files, they all get cached in the browser anyway, so no real harm in having them.

As well as any other mouse over works on mobile… aka not very well ??

Unfortunately the only other solution would be to do a popup/alert of some kind which seems very intrusive overall so I decided against it.

I’ve added a “login required” to the hover text when the user is not logged in and the registration requirement is set.

Alternatively, since this text is definable in the settings, you could add this yourself until the new release is out.

Makes sense to have an alt-text or js popup for this, will look at adding it.

The option has been added in version 2.7.

I haven’t tracked the upstream lately but will take a look, seems like it would be easy to add.

Fix will be included in next release.

Also, once you save the settings for the first time, this warning should disappear.

You should disable PHP error/warning output in your PHP config to avoid these kinds of messages. PHP generates all kinds of warnings, even some from WordPress itself depending on the usage.

Having said that, I’ll track down this specific one and fix it.

GP Integration was designed to be used with GlotPress before it became a WordPress plugin, so no surprise that it doesn’t work anymore.

With GP now fully a plugin, this plugin is no longer required and I’ve only left it on the plugin directory for historical reasons.

Thanks, I’ve updated it for the next release.

I’ll take a look, the language code matching is done by hand in one of the source files so there might just be a mistake in it. The file is in the root of the plug called deepl.locales.php if you want to take a look yourself.

Yep, as I said, there is not direct translation API, just the chat API, which can return strange results that are hard to parse.

I took a look into ChatGPT but it doesn’t seem to have a translation API that I can use, just a more general chat API which might produce some strange results that would be hard to parse.

At this time, I’m going to close this as not a workable solution, but if things change (an API become available or something) I won’t rule it out.