suziq407

Thank you for your explanation … <3

Ok, ok, room34, now I understand the structure behind.
The result is: It works fine ?? ?? ?? Many thanks.

Unfortunately, I have not found such an example anywhere.

Aaahhh, Datenbank! Daran h?tte ich selbst denken k?nnen ??
Herzlichen Dank für rasche Hilfe … <3

Bad answer!

There is also no more information at https://www.domain.tld/wp-json/wp/v2/users/1. Why this hint?
Our pages do not contain names (even URL) like “root”, “subscriber”, “testing”, also not “user”, “admin”, “demo” or “laura”.

I have been watching your tool for many months, NEVER have there been names like above. NOW SUDDENLY there are. Very strange, isn’t it?

I found your tip about the issues of ../wp-json/wp/v2/users very valuable, honestly. But please keep it serious. You wrote in another thread that you can’t make attacks, the PRO sales intent that would be an insinuation. I agree with you about the attacks. But emails with all kinds of names you (your plugin) can send anytime.

I’m not saying your plugin doesn’t work. But PLEASE stay serious, then I’m sure more people will be very happy to buy your PRO version too, huh?

When I disable wp-json, the Gutenberg editor doesn’t work anymore and many other things don’t work either. Since only the display names are visible via wp-json, but not the login names, I hardened the login names. Our passwords are complex anyway.

The only thing I find interesting is that AFTER my entry here, login names that don’t appear in the output of wp-json are also used PLENTY, such as “root”, “subscriber”, “testing” and so on. This has NEVER been the case before!

Do you have an explanation for this “phenomenon”?

Ups … many thanks. I found a solution for the functions.php. I will give Limit Login Attempts Reloaded a second chance ??

Ok, this workaround now works for me:

function wpcf7cf_dismiss_notice() {

// WORKAROUND
$temp = sanitize_text_field($_POST[‘noticeId’]);
$notice_id = isset($temp) ? $temp : ”;
// END WORKAROUND

// $notice_id = sanitize_text_field($_POST[‘noticeId’] ?? ”);
$notice_suffix = $notice_id ? ‘_’.$notice_id : $notice_id;

$settings = wpcf7cf_get_settings();
$settings[‘notice_dismissed’.$notice_suffix] = true;
wpcf7cf_set_options($settings);
}

The problem is that the cron service at the provider cannot do its job because PHP stops parsing. Therefore, updates are not made automatically and also no backups and other tasks.

However, it would be very interesting to find out about this error.
Is it possible that a special PHP module is not loaded here by my provider?

https://www.akademie-bge.at/phpinf.php — without “o” ??

The provider will certainly not participate here … ??

My PHP version is 7.4.26.
Sorry, I could have thought of that too ??