Upgrading to WordPress 3.7.

Update information      Edit    Edit2(Nov.5)    Edit3(2014.Jun.22)

   Today, Japanese WordPress develop members announced they brought the new Japanese version WordPress for us, according to the Codex for Version 3.7, there are tons of changes.

   My WordPress is a multisite type and the parent site language is English. Probably for this reason, the WordPress Updates page does not show me the Japanese version update message.

   So, I downloaded manually and upgraded.

   In the wp-includes folder, I found a certificates folder which contained a ca-bundle.crt. The ca-bundle.crt is for the below.
  ## ca-bundle.crt — Bundle of CA Root Certificates
  ## Certificate data from Mozilla as of: Sat Dec 29 20:03:40 2012
  ## This is a bundle of X.509 certificates of public Certificate Authorities
  ## (CA). These were automatically extracted from Mozilla’s root certificates
  ## file (certdata.txt). This file can be found in the mozilla source tree:
  ## It contains the certificates in PEM format and therefore
  ## can be directly used with curl / libcurl / php_curl, or with
  ## an Apache+mod_ssl webserver for SSL client authentication.
  ## Just configure this file as the SSLCACertificateFile.

   I have no error about this upgrade, but I have a warning about the site “o6asan’s netradi” like the below.

  Warning! Problem updating https://MySiteName. Your server may not be able to connect
  to sites running on it. Error message: SSL certificate problem: self signed certificate in
  certificate chain

   But I can log in the site. About using “SSL certificate: self signed certificate in certificate chain”, my sites are all in the same condition. But, on the site, I use a streaming server. I think the warning happens due to this situation. As pointed out above, the new version of WordPress gives us “Bundle of CA Root Certificates”, so, should I make a new certificate by it? I don’t get it exactly. If someone knows about the warning, please tell me in detail.

   Anyway, I completed the upgrade.

   I slightly concern about one of the new features of version 3.7 that is automatic updates for maintenance and security updates. But I think it’s probably O.K. because the automatic updates are only for maintenance and security updates. There are no differences between JP version and global version about such minor update. Am I right?

   I wrote a new article about the ca-bundle.crt.

   By the way, if you have the “Warning! Problem updating https://SITENAME. Your server may not be able to connect to sites running on it. Error message: SSL certificate problem: self signed certificate in certificate chain.“, please try Oiram’s workaround (PDF version).

   I wrote an article The solution of “SSL3_READ_BYTES:sslv3 alert handshake failure” on WordPress.

6 replies on “Upgrading to WordPress 3.7.”

Came across the same issue. I’m using CAcert ( and their certs were not in the bundle. Simply appended to the bundle and I’m good. If that’s your case as well, and you are using some public CA you should follow above example.


Thanks for your comment, Oiram.

After reading your comment, I realized I misunderstood the ca-bundle.crt. I use a private CAcert. So, I cannot append it to the bundle, and I am unable to make a new cert for me by the ca-bundle.crt, am I right?
My WordPress gave me a warning, but I have no problem exactly. My streaming server URI is embedded to the warning site, but it works well still now. I continue to keep my old environment.

Anyway, you are so kind. Thanks again. (^^)

Oiram, thanks for letting me know about your test result.

I left a comment on your site twice with the same content, but the site did not display the comment nor give me a moderation message. I submitted the new one from a different PC, so your site might recognize it as a spam. I am extremely uncertain that my comment reached you, so I write this here.

I posted a new article about the ca-bundle.crt. Please take a look.

Yes, they both landed in spam, no idea why I can only suspect that it has happened because of URLs in them

> Yes, they both landed in spam

It was as I suspected.

> because of URLs in them

Oh, maybe. Now I can see the comment on your site. Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *