i saw another thread where some devs were testing locally and saying it wasn’t working, but they just said they ended up resolving it and no exactly how or what the problem was.

so this is more of a general info post than a request for a fix, but basically if the database isn’t being modified on your local install, it’s (probably/likely/possibly) because relevanssi_light_launch_ajax_action uses wp_remote_post and you likely have a self-signed certificate.

you can verify if self-signed certs are the issue by adding this somewhere, like in your functions.php:

add_action('admin_init', function() {
$remote = wp_remote_post( admin_url( 'admin-post.php' ), [] );
var_dump($remote);
return $remote;
});

you should see this printed out on your admin dashboard:

object(WP_Error)#1695 (3) { ["errors"]=> array(1) { ["http_request_failed"]=> array(1) { [0]=> string(63) "cURL error 60: SSL certificate problem: self signed certificate" } } ["error_data"]=> array(0) { } ["additional_data":protected]=> array(0) { } }

if you do, then, well…

you can directly modify the plugin file relevanssi-light.php:342(because you’re testing locally so anything goes) and set the $args array to also have 'sslverify' => false.

• This topic was modified 11 months, 1 week ago by brumack.