hoodvisions

Thanks, guess I’ll be doing that for now. I am very confused by the current lawsuit, trying to identify the party that’s less “evil” ??

@ktc_88 can also confirm this works.

So, a form needs to be created from scratch with an account set to the language the form is supposed to be in.

When importing wordpress themes the forms that come with it – as well as the default contact form 7 forms – are usually in english, so duplicating them won’t work.

@ktc_88 I will test this out asap and report back here, thanks a lot! ??

I’d like to “hijack” this thread to add that I’m having the same issue. German website, english recaptcha. WP is in german, contact forms seem to be german too (Error message defaults are all german), but the image recaptcha is in english. Funny enough, when using elementor and while in elementor’s editing interface the recaptchas are shown in german. Weird.

I’m using the BeTheme theme, but when switching to TwentyTwenty the captcha language remains in english.

Best regards.

P.S. Lately there’s quite a lot of spam coming through, though.

@scottpaterson Thanks a bunch, I also couldn’t think of any malicious scenario regarding the functionality of the plugin, to be honest. We’re still using it at the moment. It was just weird that deactivating it via plugin settings causes a fatal error. Best regards

Same here, “There has been a critical error on this website.?” when deactivating the plugin. Admin says it’s probably malware??

We’re running PHP 8.1, latest WP.

• This reply was modified 1 year, 10 months ago by hoodvisions.

Big thanks for the support! Unfortunately I’m not really keen with PHP and I cannot really identify the hooks responsible. It seems, however, it’s all related to some kind of cronjob issue specifically on one.com – I am keeping the logs relatively clean right now with the Action Scheduler – Disable Default Queue Runner plugin. The one.com support isn’t helping and is pointing at a xmlrpc.php issue, though xmlrpc.php is restricted via htaccess and plugin.

I don’t think this is a WooCommerce related issue, so I guess the thread can be closed. Thanks a lot though ??

Thanks so much for your help! I tried both SQL commands, but unfortunately it didn’t help. The version numbers seem to be set already in the www_options table.

Right now I regularly truncate the actionscheduler_logs via

TRUNCATE www_actionscheduler_logs

By the way, said logs are exclusively filled with (action_id 64)

There was a failure fetching this action: Action [64] has invalid arguments. It cannot be JSON decoded to an array. $args = array (
)

and (action_id 58)

action ignored via WP Cron

I am quite certain this has something to do with the cronjobs not working properly on one.com or some restrictions, but I have no clue how approach this. Their support claims it’s not their “fault” and there’s no way to adjust any of the server settings, but moving to another provider is currently not an option for us either.

It only works on localhost, so I guess the plugin or the combinatioon of WP with this plugin is just not really running well on most of the german webservers/providers, at least not on Strato, Domainfactory or 1&1.

Thanks a lot for looking into this, though! ??

Umm, yes it is – I only turned it on to see what errors the page produces…and my assumption is that this error is caused by backwpup rather than any other plugin as there is no other plugin installed ?? It’s a fresh WP installation.

But thanks anyway, will look for a working alternative.

Unfortunately this error happens on all my client’s webservers. This includes domainfactory, Strato, Evanzo, ProSales, GoDaddy and a few more I just don’t remember. Now, the script DOES store archives above 100MB on my server, so I assume the filesize is not really the issue, right? Haven’t tested if these baackups are actually *working*…would be a pity if not.

Okay I found the “bug” which obviously is caused by me ??
When I update an existing post the custom_field gets passed along to the tweet. Which apparently means I have to somehow *save* the custom_field’s content before I update/publish the post…

I’m gonna donate now or even consider buying the WP to Twitter Plugin.

Thanks for the reply! I’m gonna try again on a fresh WP instance today. The weird thing is that it works with any of the regular custom fields which I can create during editing a post/page, but not the ones created by the Types plugin. Regarding the identification the plugin gives a list with the names of all custom fields (here wpcf-mylink). I would assume this is the actual name…and I think I don’t have any typos going on here.

(But hey, Your plugin rocks, too, btw! ?? )