I believe the xml file was put there by a predecessor of mine.
That option is indeed set to “The language is set from the content”. There’s also the option “remove /language/ in readable Permalinks” set though, and if I change to “The language is set from the directory name”, the English URLs all get an /en/ added, which is not wanted in this case. Can that be amended?
In any case, I did find a different solution in the meantime, with some code in the functions.php, using get_theme_mod() to get the actual strings, pll_register_string() them and then add_filter('[registered_string]', 'spacious_translate_slider_string', 10, 1); function spacious_translate_slider_string($value) { if (function_exists('pll__') && !empty($value)) { return pll__($value); } return $value; }
Ok, had a chat with the German Market people. In case anyone else encounters this: There is an option at “Einstellungen -> Allgemein -> Bestellvorgang -> Checkout Template / Theme Optionen” to disable “German Market Hooks”.
Disabling those Hooks solved the issue. Apparently they rearrange the Checkout page, which somehow interfered with the Advanced Card Processing gateway.
Well, since this was sort of a pre-sale (or -install) question, I don’t have an Events Calendar account and your answer is “no”, I won’t get involved just yet 🙂
For anyone else reading: In this instance the problem was most probably that I had added the “cf7ic_generate” action to the actions to look out for under the “scope” tab.
Ok, just tested with the new update – the issue prevails. In the meantime, I also had the same problem on another page with a wholly different setup (different Server, different theme, and without the WP Image Captcha Plugin) – Trying to login, I get “Ihre Nachricht wurde als Spam eingestuft! Wenn Sie ein Mensch sind, entschuldigen wir uns dafür. Bitte schreiben Sie uns eine E-mail mit einem Hinweis.”
I also don’t think there is any IP forwarding happening, but I didn’t check that yet. Will apply the update and reactivate the plugin next week, then I’ll also check the logs.
Ok, in case anyone comes across this and, like me, does not think of the obvious, here’s what Complianz’ wonderful support helped me realize:
This was caused by a widget present on every page that included the Complianz Consent Area shortcode with the cache_redirect-attribute active, like so:
[cmplz-consent-area cache_redirect="true" ...]
Removing the cache_redirect-attribute solved the problem.
Huh, that finally pointed me in the right direction, thanks!
Theme is “X” (Child) by Themeco: https://theme.co/x There was a code active in the child theme’s functions.php, that came from their forum and used to help with Complianz breaking Cornerstone.
Here’s the code:
function cmplz_my_filter_site_needs_cookiewarning( $cookiewarning_required) { if ( function_exists('CS') ) { return false; } } add_filter( 'cmplz_site_needs_cookiewarning', 'cmplz_my_filter_site_needs_cookiewarning' );
