kaggdesign

The 4.9.0 with Tutor support is released. You may leave a review?on?www.remarpro.com. Thank you!

The bug exists in any PHP version, starting from 5.1+, when it became possible to declare a parameter with type array.

В Ninja были значимые изменения, я несколько раз подправлял hCaptcha. Возможно, проблема из-за этого.

Помогает ли удаление/добавление поля hCaptcha?

I have added Tutor LMS support to v4.9.0, to be released in January. Now hCaptcha is supported on Login, Registration, Lost Password and Checkout pages of the Tutor LMS.

Я не могу воспроизвести проблему. Попробуйте удалить поле hCaptcha и добавить его снова.

I see that Tutor LMS exists also in free version; I have found it on wp.org. So no need to send zip file to me.

I have reproduced and fixed the problem on our end. The fix will be included into next v4.9.0 and released in the beginning of January. Problem is created by Tutor LMS. In templates/login-form.php:70 they do the following:

apply_filters( 'login_form_middle', '', '' );

This is the pure bug. The second argument must be an array, not ''. I will report in their repo.

Also, we will try to make an integrations with Tutor LMS. so you can add hCaptcha to their forms.

Hi @mirrorofzen,

Thank you for reporting. This is the bug in the TutorLMS. In the WordPress core (wp-includes/general-template.php:571), the definition of the filter is provided

/**
 * Filters content to display in the middle of the login form.
 *
 * The filter evaluates just following the location where the 'login-password'
 * field is displayed.
 *
 * @since 3.0.0
 *
 * @param string $content Content to display. Default empty.
 * @param array $args Array of login form arguments.
 */
$login_form_middle = apply_filters( 'login_form_middle', '', $args );

The second argument $args must be an array, but TutorLMS in wp-content/plugins/tutor/templates/login-form.php(70) executes apply_filters with wrong $args, sending a string instead of an array.

I can fix it on our end but again – it is not our bug.

Also, I do not think that hCaptcha can work with TutorLMS – we do not have integration with this premium plugin. We can consider integration with TutorLMS, if you can provide its zip file for testing on my email [email protected].

Many thanks,

I have installed WooPayments and configured it. No such problem on my test site. Could you provide a link to the page with the problem?

Also, please read the answer to the similar issue, it may help.

Many thanks.

Спасибо за ролик, но из него мало что понятно. В чем конкретно проблема?

Трудно сказать, что у вас в коде и в какой момент происходит сохранение поста. Cyr2lat работает на хуке sanitize_title, срабатывающем при сохранении или обновлении.

Плагин не всегда подключает свои хуки, но вы можете это исправить через фильтр ctl_allow. Пример тут.

Ваш фильтр ctl_allow должен быть добавлен на самом раннем этапе загрузки вашего плагина или на хуке plugin_loaded (не путайте с plugins_loaded).

Closed as not answered in 2 weeks.

Closed as having no response in 2 weeks.

Hi @mjezegou,

When you do not see the checkmark, it indicates that the hCaptcha API script was not loaded or loaded too late. Some page caching plugins change script order improperly and can cause such issues.

Please provide the page you need help with (your link does not work).

P.S. We do not need async + defer in script, as it is the same as async. Please see the documentation.

After investigations, I see that the PayPal form is a third-party form provided by PayPal. It is loaded from PayPal.com and is sent there. This creates an inability to verify hCaptcha. We can add hCaptcha to this form, but any CAPTCHA must be verified on the backend.

So, any form with a CAPTCHA must be sent to your website for verification. When a form is sent directly to a 2rd-party site, adding any CAPTCHA does not work.

You can disable Express Checkout on the Checkout page WooCommerce->Settings->Payments page in the “PayPal Smart Buttons” section. Then, you can add hCaptcha to the Checkout page on the Integrations page of the hCaptcha plugin. This prevents bots from clicking on payment buttons.

Our plugin does not support WooPayments so far. We will try to add it in the next release.

Please keep in mind, that if you use Stripe, you do not need to add hCaptcha to the payment form. Every Stripe payment form already contains invisible, 99.9% passive hCaptcha of Enterprise level. It is provided by Stripe system by itself.