Title: Scriptrunner (Doug Sparling)'s Replies - page 6 | WordPress.org --- # Scriptrunner (Doug Sparling) [ ](https://wordpress.org/support/users/scriptrunner/) * [Profile](https://wordpress.org/support/users/scriptrunner/) * [Topics Started](https://wordpress.org/support/users/scriptrunner/topics/) * [Replies Created](https://wordpress.org/support/users/scriptrunner/replies/) * [Reviews Written](https://wordpress.org/support/users/scriptrunner/reviews/) * [Topics Replied To](https://wordpress.org/support/users/scriptrunner/replied-to/) * [Engagements](https://wordpress.org/support/users/scriptrunner/engagements/) * [Favorites](https://wordpress.org/support/users/scriptrunner/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 76 through 90 (of 520 total) [←](https://wordpress.org/support/users/scriptrunner/replies/page/5/?output_format=md) [1](https://wordpress.org/support/users/scriptrunner/replies/?output_format=md) [2](https://wordpress.org/support/users/scriptrunner/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/scriptrunner/replies/page/3/?output_format=md)… [5](https://wordpress.org/support/users/scriptrunner/replies/page/5/?output_format=md) 6 [7](https://wordpress.org/support/users/scriptrunner/replies/page/7/?output_format=md)… [33](https://wordpress.org/support/users/scriptrunner/replies/page/33/?output_format=md) [34](https://wordpress.org/support/users/scriptrunner/replies/page/34/?output_format=md) [35](https://wordpress.org/support/users/scriptrunner/replies/page/35/?output_format=md) [→](https://wordpress.org/support/users/scriptrunner/replies/page/7/?output_format=md) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/5/#post-4307376) * I have been able to verify that if WordPress is running behind Varnish, then it is quite possible that non-admin/login cookies will be deleted (depending on Varnish configuration): * [My website is now super-fast with Varnish](http://kovshenin.com/2011/my-website-is-now-super-fast-with-varnish/) * And here’s a Varnish 3.0 WordPress configuration template: [wordpress.vcl * The Varnish template includes: * ``` # Drop any cookies sent to WordPress. if (!(req.url ~ "wp-(login|admin)")) { unset req.http.cookie; } ``` * But I’ve seen examples where this part is commented out and it’s set to delete all WordPress cookies… * I’d really like to test this, but I just don’t have the time to set up Varnish at the moment. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307374) * More than likely. (if wp-login.php is updated) * The other thread is here: [Cookie Error when Logging In](http://wordpress.org/support/topic/cookie-error-when-logging-in?replies=117) * Someone had something for their functions.php (I know [@willem](https://wordpress.org/support/users/willem/). deboer saw it), but apparently it didn’t work. * So for now, it looks like for those effected, it’s hack a core file, revert to WordPress 3.7, or upload wp-login.php from WordPress 3.7. (it should work with WordPress 3.7.1) * I’m not on the core team, just a plugin developer and someone with clients running on WordPress. I haven’t been effected by this, but this is the kind of odd ball things that popup that I try to keep up with. * I’m curious and don’t know how it’ll be treated a sit seems to be an issue with the environment WordPress is running in. (a proxy server blocking or deleting certain cookies if that report is true) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307372) * Well, it does appear under certain scenarios this is an issue – I’ve heard everything from admin not allowing cookies (seems less likely) to proxy servers (Varnish) removing testcookie. * The suggested fix in another thread…Comment out lines 744-746 in wp-login.php: * ``` // if ( isset($_POST['testcookie']) && empty($_COOKIE[TEST_COOKIE]) ) // $user = new WP_Error('test_cookie', __("ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.")); // else $user = wp_signon('', $secure_cookie); ``` * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307370) * Also, it’s up to theme and plugin authors to keep their software, which is separate from core, up-to-date and compatible with the latest releases of WordPress and different versions of PHP. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307369) * Actually, no, that wouldn’t be a precise paraphrase. It’s possible with any install or upgrade (of WordPress or any other software) for files to become corrupted for a multitude of reasons (often due to a server timeout in the case of web- based installs), nothing to do with WordPress at all. I’ve not seen any reports other than this thread that there’s been any problems. All my installs went from 3.7 to 3.7.1 just fine. There are so many variables – severs, versions of OS, PHP, MySQL, etc, and http connections, which aren’t always reliable. Generally( I’d almost say always) point release versions upgrades of WordPress are seamless. * Vanilla install – sorry, I mean just a plain, basic install. Default themes and no plugins. (other than what comes with WordPress itself) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307365) * OK, I wouldn’t worry about upgrade-functions.php at the moment. It won’t be in WordPress 3.7.1, so what you have is fine. * The only thing I’ve seen in this thread (and the previous one) that makes any sense is the “headers already sent” error, as that would prevent the test cookies from being written. * As far as the cause of that error (headers already sent), it’s not necessarily wp-config.php, but often is. But it could be any php file with extra white space after the closing php tag at the end of the file. (which is why the closing php tag at the end of a file is often not used) * Once again, if it were me, I’d either delete and re-upload core files or I would just back everything up (I’d do that anyway) and do a complete fresh install ( using your current wp-config.php file or copying the content over to the new one so you can use your existing database) and then bring over theme and plugins( from your old wp-content directory) over an item at a time. I’d probably go with deleting and re-uploading core files first, making sure FTP is set to automatic. If that didn’t work, then doing the complete re-install (WordPress only, not the database) might be the only way. Get a vanilla install working and then bring back in your theme and plugins. It looks like over the course of the last two or three days, you’ve made a lot of changes trying to fix things. Sometimes it might be best to start at square one and go from there. * You definitely need to eliminate the “headers already sent” error. As far as a corrupt file from the upgrade, I just meant originally. That happens sometimes. Anyway, I’m not sure I can offer much more advice, but I don’t mind answering( or trying to 🙂 any other questions. I don’t think WordPress itself is the problem, but more likely something to do with the install or a theme/plugin compatibility issue. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307360) * Did you get the “browser doesn’t support cookies” error right after doing the ugprade through the admin, or did you upload anything before seeing that error? It’s also possible the upgrade via the admin timed out or corrupted some files. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307359) * First, check this codex page: [How do I solve the Headers already sent warning problem?](http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F) * You mentioned you FTP’d your files in binary mode but I can’t tell from our conversation if you only uploaded wp-login.php with automatic mode, or everything. As the link above suggests, wp-config.php is often the culprit for the headers already sent error message. * Also, as there’s an notice about deprecate file wp-admin/includes/upgrade-functions. php tells me that old files weren’t deleted first when you uploaded the new ones. WordPress 3.7.1 does not include upgrade-functions.php, but I have a fresh install. However, without the deprecated upgrade-functions.php, the ss-downloads plugin will probably break. However, this shouldn’t be causing the problem, I really think that it’s related to the ‘headers already sent’ error and I’d follow that codex page. Uploading in binary very well could have caused the problem. The headers already being sent is preventing the test cookie from being set. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/4/#post-4307357) * If php setcookie function returns false, that means (according to docs): * > If output exists prior to calling this function, setcookie() will fail and > return FALSE . * Setting WP_DEBUG to true should show you any errors, though I think you already did that and you probably should have seen an “headers already sent” error. Did you look in the apache error log itself? * Also, after setting WP_DEBUG to true, try changing the code I gave you to: * ``` if (setcookie(TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN)) { error_log("TEST_COOKIE/COOKIE_PATH - SET"); } else { error_log("TEST_COOKIE/COOKIE_PATH - NOT SET"); } ``` * When you say both sites, do you mean with www and without, or do you have another site that’s working? * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307354) * At this point, if it were me, I’d add a simple echo statement to check that 1) the test cookie code is being called and 2) if so, check if setcookie was successful. * In `wp-login.php`, right before this code (which should be line 420): * ``` //Set a cookie now to see if they are supported by the browser. setcookie(TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN); if ( SITECOOKIEPATH != COOKIEPATH ) setcookie(TEST_COOKIE, 'WP Cookie check', 0, SITECOOKIEPATH, COOKIE_DOMAIN); ``` * I’d add: * ``` if (setcookie(TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN)) { echo "TEST_COOKIE/COOKIE_PATH - SET"; } else { echo "TEST_COOKIE/COOKIE_PATH - NOT SET"; } ``` * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307352) * I had considered that. * You might want add (or add to) .htaccess in the wp-admin directory with this in it: * ``` Order allow,deny Allow from all Satisfy any ``` * as `wp-admin/admin-ajax.php` is used by the front-end (see [Codex: Hardening WordPress – securing wp-admin](http://codex.wordpress.org/Hardening_WordPress#Securing_wp-admin)) * Also, you might want to protect wp-login.php, as it’s in top-level directory, not under wp-admin. (though locking down wp-admin will prevent anyone who does successfully brute force a login to get anywhere) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307350) * Actually, no, not for directories. Directories need be “executable.” Generally for WordPress, directories are 755 (drwxr-xr-x)and files are 644 (rw-r–r–). * These codex pages may help: * [Changing File Permissions](http://codex.wordpress.org/Changing_File_Permissions) [Hardening WordPress](http://codex.wordpress.org/Hardening_WordPress) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307348) * Not sure if it’s related but check permissions on the wp-admin directory. I get permission errors on anything in that directory, including things that should be publicly accessible like [http://www.communsense.nl/wp-admin/css/colors-fresh.css](http://www.communsense.nl/wp-admin/css/colors-fresh.css) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307345) * I know you’ve already tried default theme/disabling plugins (and you’ve deleted and reinstalled WordPress core files), but you might do that again with DEBUG set to true. * The first Notice I’ve seen happen from plugins using a deprecated function and also when file are FTP’d up in binary instead of ASCII. * The second notice is from a plugin, and I wouldn’t think would cause issues. * Also, you might try reuploading wp-login.php. It should set a test cookie, and from your report some cookies are getting set. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: ["Cookies are blocked or not supported" since update to 3.7.1](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/) * [Scriptrunner (Doug Sparling)](https://wordpress.org/support/users/scriptrunner/) * (@scriptrunner) * [12 years, 6 months ago](https://wordpress.org/support/topic/cookies-are-blocked-or-not-supported-since-update-to-371/page/3/#post-4307341) * You might try deleting all the cookies associated with your domain and hit wp- login.php and see what you get… Viewing 15 replies - 76 through 90 (of 520 total) [←](https://wordpress.org/support/users/scriptrunner/replies/page/5/?output_format=md) [1](https://wordpress.org/support/users/scriptrunner/replies/?output_format=md) [2](https://wordpress.org/support/users/scriptrunner/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/scriptrunner/replies/page/3/?output_format=md)… [5](https://wordpress.org/support/users/scriptrunner/replies/page/5/?output_format=md) 6 [7](https://wordpress.org/support/users/scriptrunner/replies/page/7/?output_format=md)… [33](https://wordpress.org/support/users/scriptrunner/replies/page/33/?output_format=md) [34](https://wordpress.org/support/users/scriptrunner/replies/page/34/?output_format=md) [35](https://wordpress.org/support/users/scriptrunner/replies/page/35/?output_format=md) [→](https://wordpress.org/support/users/scriptrunner/replies/page/7/?output_format=md)