Kyle Charlton

I have released an update to fix the issue, please update to version 3.3.1.

Hello,
Thank you for bringing this to me attention, I have released an update to fix the issue, please update to version 3.3.1.

Interesting, those errors never appeared in the validation tests I performed.
It looks to be an issue primary between “http” vs “https”.
I will correct this in the next update.

Hello,
I have re-added the language files, please update to version 3.3 and let me know if that resolved your issues.
Thanks!

Hello,
I have re-added the language files, please update to version 3.3 and let me know if that resolved your issues.
Thanks!

Hello,
I have re-added the language files, please update to version 3.3 and let me know if that resolved your issues.
Thanks!

Hello,
I have re-added the language files, please update to version 3.3 and let me know if that resolved your issues.
Thanks!

Hello,
After looking into the issue I found that the SVG formatting passes the W3 validator.
When I passed the SVG code into the validator by itself I get two warnings (not errors), those warnings go away when the SVG is used within the HTML document.

While reading the SVG documentation you suggested, I found that the current SVG structure used in the plugin is correct, so long as its used as HTML which is how the plugin is using it.

I apologize for the delay in the update release.
I will work on getting the update released this week.

Hello,
The Contact Form 7 Image CAPTCHA is fully compatible with WordPress 6.1.
I have not updated that note in the documentation yet as I am in the middle of updating the plugin with some non-related improvements.

Update: I am currently working on version 3.3, I have completed the jQuery conversion to JavaScript and am now performing additional plugin updates. Please be on the lookout for version 3.3 which I hope to release soon.

Hi,
Thank you for bringing this to my attention.
The SVGs used in the plugin have been minified to reduce file size, I have not seen validation errors in the past using the compression tool.
I am currently working on version 3.3, I will look into the validation errors.

Hi, I will go ahead and revert the previous changes to the plugin and add the language files back into the plugin.
Hopefully that will resolve all of these issues.

Hello,
I completely agree about jQuery, and I must apologize as I have long ago removed jQuery dependency from the pro version of the plugin, but have neglected to do so on the free version.
I will add that to the road map for my next update.

Hi,
It could be an issue with the WordPress language files not being installed.
The installation and updates of language files usually occurs during plugin activation or updates. You could try to de-activate and then re-activate the plugin to see if that resolves the issue.

If that does not, please provide me with the exact language you are trying to use so I can take a look at the files on translate.www.remarpro.com to see if there is any issues there.