Try setting a path and domain, setcookie(‘style’, ‘style2’, time()+31536000, “https://wordpress.stackexchange.com/”, ‘.example.com’); Replace .example.com with your sites hostname. Further reading: http://php.net/manual/en/function.setcookie.php
There is no best practice here, and to be really honest, cookies are your best (and probably only) option here. The issue with visitors are that they are only visitors. If they were first time signup members and you would want to show something to them only once when they are done registering, the best … Read more
The check is handled by post_password_required(), which seems to be incredibly inconvenient to override. The only way I can think of is early during load: Check if there is a valid WP cookie (if there we are done). Check if there is valid external cookie (if not we are done). If there is then generate … Read more
You will need to use the authenticate filter: https://codex.wordpress.org/Plugin_API/Filter_Reference/authenticate add_filter( ‘authenticate’, ‘myplugin_auth_signon’, 30, 3 ); function myplugin_auth_signon( $user, $username, $password ) { return $user; } Return a WP_Error object to indicate failure or an issue, or a WP_User object on success. There are also 2 core functions hooked into that filter that will need removing … Read more
Try hooking on the get_header action hook. That’s the last action hook before headers are output.
You could hook into the template redirect function. function my_page_template_redirect() { if ( isset( $_COOKIE[“myCookie”] ) ) { if( $_COOKIE[“myCookie”] == “en” ) { wp_redirect( ‘you path’ ); exit; } } } add_action( ‘template_redirect’, ‘my_page_template_redirect’ ); And you could better use wp_redirect() function to redirect inside WordPress.
The cookie is stored on the user’s computer. The page is generated on the server. Somehow, you must make sure the cookie is transported back to the server when the user clicks on a link to fetch a second page. The instrument for this is javascript. You must send a script with the page that … Read more
No it won’t. If the domain name is still the same then cookies issued by WP will still be passed back and forth between browser and server.
@font-face does not require cookies (unless you choose to cache fonts to avoid server hits), and having a subdomain will make no difference either. You may therefore have an issue with your URLs. Your paths in the first (multiple-line) example are relative to your css file; is your ‘fonts’ directory in the same directory as … Read more
You use setcookie() like any other function, with parameters as described in the Codex. How you would use it in a form would usually depend on how and when the $_COOKIE variable needs to be made accessible. One common method, if you want a change in the DOM both to register immediately and to persist, … Read more