Since the Core developers decided to make this stuff part of the Core instead of a plugin (which is what should be done), the quickest solution (and to avoid changing core files) is to add this plugin which removes the newly added GDPR features. This way, I can find a GDPR plugin which will allow me to more easily customize what I want to do.
Because I do like the idea of being able to easily export user data, however, the built in tools are not easily customized or advanced enough.
Sure, I could have left the built in tools in place and added a GDPR plugin on top of that, but then there is too much clutter in the backend.
Also, the beauty of this solution is if WordPress’ GDPR/Privacy solutions get a lot better, then I can deactivate both plugins that I’m adding and voila, I’m back to whatever WordPress recommends.
Hello !
I know it’s been a while but I faced the same issue and I did a trick which worked for me.
Change the bad string in your url, in your functions.php :
function redirect_to_good_link() {
// GET THE ACTUAL URL
$actual_link = “http://$_SERVER[HTTP_HOST]$_SERVER[REQUEST_URI]”;
// IF THERE’S SOME PART OF THE GDPR LINK
if (strpos($actual_link, ‘?action=confirmaction&request_id=’) == true) {
// REPLACE YOUR CUSTOM STRING BY THE GOOD ONE
$new_url = str_replace(‘unique-login-page/’, ‘wp-login.php’, $actual_link);
// AND REDIRECT TO IT
wp_redirect($new_url);
exit();
}
}
add_action(‘template_redirect’, ‘redirect_to_good_link’);
Hope it works for you 🙂