zakoops

Hello,

Last link provided by yoga1103 is now outdated and a bit of a jumble in the words of WPyogi, and has been closed.

I have exactly the same problem as tanveer.rahat (first post here), on XAMPP, and this is driving me mad.

I have launched the HTTPS Tester as well as the Background Update Tester plugins. In essence, cURL and OpenSSL are working OK, and httpd.conf, php.ini, httpd-ssl.conf, and hosts have been tweaked a zillion of times. After all those tweakings, my localhost system still works OK. Everything is OK in fact.

With the exception of lines 123, 303, and 467 of file wp-includes/update.php, where WordPress could not establish a secure connection to WordPress.org.

Is there anything obvious that I didn’t think yet?

My website is on OSX 10.11.2 (El Capitan) and WordPress at 4.4.1.

To Futtta and Franck160,

ThreadStackSize is definitely solving the problem!

It’s wow again 🙂

Now, default theme (twentyfourteen) is now working perfectly on my localhost with everything minified (including the css file) !

As Include conf/extra/httpd-mpm.conf was already uncommented in the httpd.conf file, the change as been inserted as follows in httpd-mpm.conf instead:

# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxConnectionsPerChild: maximum number of connections a server process serves
# Adding ThreadStackSize on 2014-01-04
<IfModule mpm_winnt_module>
    ThreadStackSize    8388608
    ThreadsPerChild        150
    MaxConnectionsPerChild   0
</IfModule>

8388608 being equivalent to 8*1024*1024… (see How do I increase the stack size for Apache running under Windows 7?).

Admittedly, the contribution of Franck160 was a nice (and a dirty) one, but changing the ThreadStackSize is more elegant.

Now going back to my ongoing project with a smile…

Thanks to both of you and have a nice day!

Thanks for looking into this matter!

Versions used on XAMPP/Windows 7:

• XAMPP 1.8.3
• Apache 2.4.7
• PHP 5.5.6
• MySQL 5.6.14

After a fresh reboot this morning and making sure that no other plugins are running, I’m still getting the same problem…

I continue my investigation because this issue challenges me and will inform you of anything that might be interesting.

Hi futtta,

I’m having exactly the same behavior as onetrev here with CSS optimization being the problem:

• Connection reset in all browsers tested.
• A redirect under Firefox (but not under Chrome): “http://localhost/eng/” becomes “http://www.localhost.com/eng/”
• After some 7 or 8 seconds (that feels long…), I get:

• With Firefox: Server not found — Firefox can’t find the server at http://www.localhost.com.
• With Chrome: Inaccessible Web Page (however, the url remains “http://localhost/eng/”).

The above behavior is obtained with these settings:

• Optimize HTML Code? Box checked.
• Optimize JavaScript Code? Box checked.
• Optimize CSS Code? Box checked (any other variants of css settings do not eliminate the problem).
• All other Autoptimize settings are off (unchecked).
• In last resort, I inserted in wp-config.php the “define(“AUTOPTIMIZE_LEGACY_MINIFIERS”, “true”);” but without any success.

My test is done with the following:

• WordPress 3.8
• xampp/localhost (Windows 7)
• TwentyFourteen theme.

This test is made with a child theme where the [near] empty style.css is:

/*
Theme Name:     Twenty Fourteen Blues
Theme URI:      http://example.com/twenty-fourteen-child/
Description:    Twenty Fourteen Child Theme
Author:         dharma blues
Author URI:     http://example.com
Template:       twentyfourteen
Version:        1.0.0
*/
@import url("../twentyfourteen/style.css");

/* =Theme customization starts here
-------------------------------------------------------------- */

If I do the same test but in the parent theme (no more child), the same problem persists. So, child theme is not the culprit here.

Most notably: as soon as I uncheck the “Optimize CSS Code” setting, then everything runs fine (and HTML and javascript are indeed minified).

So, legacy minifiers do not appear to help here!