In my case it was a plugin which I installed yesterday night. In the next day I got this error. SOLUTION : Deleted the plugin from wp-content/plugins and every thing was OK after that.
This error is generated in wp-login.php , it happens if server is unable to set cookies, this can happen due to several reasons, one of the common issue is: output being sent before setting up of cookies. Try out following options: Update WordPress core, if it is not up to date change theme, if you … Read more
Try using secure method to prevent session hijacking Attack. Session Id should change/get refreshed evert time user get login and log out. WordPress doesn’t use PHP sessions, and doesn’t have a static session ID. You must be using a plugin or theme that is. login credentials should be encrypted at code level. WordPress’ login credentials … Read more
If you want the ID of the current post outside of the loop, you can use get_queried_object_id(). Just make sure to check is_singular() first, or you could end up storing IDs of things other than posts. This could cause problems if there’s overlap with post IDs. I’d share the amended code with those changes, but … Read more
Sound like some configuration in your browser that keeps cookies only for a session specifically for you site. To make sure the problem is not on Wordress side, deactivate all your plugins and try again.
Nevermind, I found the solution. I included pluggable.php in the plugin which is a no-no to start with. And then I used wp_get_current_user() incorrectly.
Use COOKIEPATH and COOKIE_DOMAIN constants. setcookie( ‘welcomeback’, ucfirst( $_POST[‘firstname’] ), strtotime( ’27 Feb 2017′ ), COOKIEPATH, COOKIE_DOMAIN );
The problem was with domain. I should have set the cookie domain globally. /
You can try like this code: After installation, open the wp-config.php file in Site B’s installation root, and add (or replace) the following lines shortly after the database configuration, modifying them as needed to fit your configuration: $cookiehash = md5(“http://www.example.com/”); // Use Site A’s URL define(CUSTOM_USER_TABLE,’wp_users’); //Change ‘wp’ to match the prefix set during define(CUSTOM_USER_META_TABLE,’wp_usermeta’); … Read more
Transients seem to be appropriate storage. Just note that if you will generate a lot of this and they will be disposable then you will need to cleanup old transients. As for your cURL/filename issue – it is bad practice to use cURL directly in WordPress. WP provides HTTP API that abstracts remote requests. Unfortunately … Read more