Short answer: You can’t. That’s not hookable for the settings cookies. You can adjust the cookie paths and such via defines, so as to make the settings apply across multiple installations across a domain. The most common use of this is to make logins work across a domain, so when you log into one, you … Read more
Just check if the variable is set, using the code from your link: add_action( ‘init’, ‘set_agent_cookie’ ); function set_agent_cookie() { if (isset($_GET[‘code’])) { $name=”agent”; $id = $_GET[‘code’]; setcookie( $name, $id, time() + 3600, “https://wordpress.stackexchange.com/”, COOKIE_DOMAIN ); } }
The second parameter in add_filter is a function with accepted arguments, not returned values. This is an example how I pass my custom array $args to change an existing array $filter_args: add_filter( ‘woocommerce_dropdown_variation_attribute_options_args’, function( $filter_args ) use ( $args ) { return eswc_var_dropdown_args( $filter_args, $args ); } ); function eswc_var_dropdown_args( $filter_args, $args ) { $filter_args[‘show_option_none’] … Read more
When you log in to the admin WordPress sets cookies (in PHP) to keep you logged in while you navigate around your site. If this fails, you get the error message, “Cookies are blocked or not supported by your browser.” This could fail in a couple different ways, but before we dig into those situations, … Read more
According to the WP_Session_Tokens class documentation, this token is used to validate the user’s session. It does this by checking the provided token against the existing session tokens stored in the user meta table for that user. Session tokens are generated using the wp_generate_password function, and are 43 characters long. So no, it should not … Read more
For a truly full solution you need to have all the users to have an account (or create one when marking as read) and you associate in the DB the user with the posts that he read and then style each link appropriately. To implement this you can look for inspiration in plugins that add … Read more
It looks like you’re missing the nonce part, as explained in the Authentication chapter, in the REST API Handbook: Cookie authentication is the basic authentication method included with WordPress. When you log in to your dashboard, this sets up the cookies correctly for you, so plugin and theme developers need only to have a logged-in … Read more
I add one function wp_set_current_user for setting up current user. add_action( ‘wp_ajax_facebook_login’, ‘facebook_ajax_login_or_register’ ); add_action( ‘wp_ajax_nopriv_facebook_login’, ‘facebook_ajax_login_or_register’ ); function facebook_ajax_login_or_register(){ $uid = sanitize_text_field( $_POST[‘uid’] ); $args = array( ‘meta_key’ => ‘fbuid’, ‘meta_value’ => $uid, ‘meta_compare’ => ‘=’, ); $fb_user = get_users($args); $current_user_id = $fb_user[0]; wp_set_current_user($current_user_id);//Set current user wp_set_auth_cookie( $current_user_id, true ); $response[success] = true; echo … Read more
Here (with some trepidation) is a sketch of a use-once link solution that might be safeish enough if one can depend on the ip being fairly constant (at least in the short-term) to the phone, using a query var and a transient based on $_SERVER[‘REMOTE_ADDR’], though as @Wyck and @G. M. say, any such backdoor … Read more
The problem #1 & #2: Don’t know why you need to add and validate extra cookies, but for me, it’s simple and quite straight forward: This is what I have tried on vagrant boxes and with default WordPress structure: 1. Prepare 6 separate servers 111.111.1.10 – MySQL server 111.111.1.11 – HAProxy server 111.111.1.12 & 111.111.1.13 … Read more