You could check for this cookie wp-settings-1 it lasts for 1 day and then also check if wordpress_test_cookie is available. Or you could just write a simple plugin that checks if the user is logged in and adds a longer term cookie to check against.
Using “cookieless” domain for serving static assets is common recommendation performance tools give. The reasoning being that cookies do nothing at all for such files, but still consume resources. It is, however, not something WP can handle for following reasons: WordPress does not control domain. DNS points domain to specific server’s IP address, where WP … Read more
That is actually dead simple. Cookies are set by wp_set_comment_cookies() and this function is hooked into ‘set_comment_cookies’. Just remove the function from the action: <?php # -*- coding: utf-8 -*- /* Plugin Name: No Comment Cookies */ remove_action( ‘set_comment_cookies’, ‘wp_set_comment_cookies’ ); Download on GitHub.
I’ve worked out a solution. There may be a more elegant way to achieve this, but I had trouble getting anything else to work. I’ve placed the following code at the beginning of the header.php file for all pages. The objective is to funnel site visitors through an event registration page, prior to accessing the … Read more
get_currentuserinfo() is a pluggable function, it is not available during plugins load stage. That aside you shouldn’t be adding filter conditionally, but use data provided by the filter. If you take a look at filter calls: apply_filters( ‘auth_cookie_expiration’, 14 * DAY_IN_SECONDS, $user_id, $remember ) $user_id is provided as second argument. You just have your filter … Read more
I like this question so had a look at it myself. The best way I could think to go about it would be to use localstorage and jQuery to store the current URL and scroll position of the user. Then you could either run a check when they come back to that page or have … Read more
Depends on whether or not you need to check against WordPress’ user authentication. If you need to know whether they’re a logged in user, hook onto ‘init’. Otherwise, the sooner the better. If it’s something that should fire on every page load, and only checks for existence of the cookie and doesn’t need to tap … Read more
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