About ability of an automatic translation site-#2.

   About two and a half years ago, I wrote “About ability of an automatic translation site-#1” in Japanese. Once again this subject.

   When I wrote the article, I translated “Sucuri SiteCheck is a free & remote scanner. Although we do our best to provide the best results, 100% accuracy is not realistic, and not guaranteed.” into “Sucuri SiteCheck は無料のリモートスキャナです。できる限り正確な情報をお届けできるように努めていますが,スキャン結果に間違いがないことを保証するものではありません。”. After posting it, I translated the sentences by Google Translate.

By Google Translate:

  • Sucuri SiteCheck is a free & remote scanner. Although we do our best to provide the best results, 100% accuracy is not realistic, and not guaranteed.
  • Sucuri SiteCheckは無料&リモートスキャナです。我々は最高の結果を提供するために最善を尽くしますが、100%の精度では現実的ではない、と保証されません。

   It is pretty good! It is not good at translating elliptical sentences, but I can get what this Japanese sentences means. If the original has an ‘is’ like ‘~ 100% accuracy is not realistic, and is not guaranteed.’, the translation is improved a little.
   Like this: (When an ‘is’ exists in the original.)
   Sucuri SiteCheckは無料&リモートスキャナです。我々は最高の結果を提供するために最善を尽くしますが、100%の精度では現実的ではない、と保証するものではありません。

   And then, I translated my sentences by Google Translate:

  • Sucuri SiteCheck は無料のリモートスキャナです。できる限り正確な情報をお届けできるように努めていますが,スキャン結果に間違いがないことを保証するものではありません。
  • Sucuri SiteCheck is a remote scanner free. And strive to be able to deliver accurate information as possible, but it does not guarantee that there is no mistake in the scan results.

   Hmmm. What do you think about it? Anyway, the translation has no ‘we’ / ‘our’ because my Japanese sentences have no ‘私たち’. I think this is one of the biggest differences between English and Japanese as I mentioned earlier.

A WordPress Plugin “BulletProof Security”.

Update information      Edit(Dec.2)~~Edit4(2014.Jul.14)    Edit5(Jul.16)

   I installed the Plugin “BulletProof Security” for my WordPress security. It’s easy to install. But there is something you should consider in activating if you also use it.

  1. Though it is Network / Multisite Compatible, you should NOT make it Network Activated. Network Deactivate BulletProof Security and then activate BulletProof Security on your Primary site ONLY.
  2. BulletProof Security uses .htaccess files, so you should back up the otiginal files in your WordPress Root and wp-admin folders before its activating.
  3. BulletProof Security uses .htaccess files, so it depends on your server configuration if you can use it or not. In my case, I had an error, so I added Options=Indexes to my AllowOverride Directive in the <Directory> section of the httpd.conf.

   By the way, I found BulletProof Security introduced Sucuri SiteCheck Scanner on one of its pages. So I tried to scan my WordPress sites. On the sites, no threats were found, though they say “Sucuri SiteCheck is a free & remote scanner. Although we do our best to provide the best results, 100% accuracy is not realistic, and not guaranteed”.

Edit(Dec.2):
   The plugin ‘Broken Link Checker’ gave me the message below:

   Broken Link Checker has detected 1 new broken link on your site.
   Here’s a list of the new broken links:
   Link text : Asus ,HCL X51C (T12C) Motherboard schematic
   Link URL : /blog-j/files/Asus_HCL_X51C_(T12C).pdf
   Source : ノートをWin8 Proにアップグレード。
   You can see all broken links here: http://My WP dashboard tool URL

   Why suddenly? This PDF file I uploaded on Oct.16 and have not made any changes to it. I got another message when I accessed the PDF by a browser. Like this:

   o6asan.com 403 Forbidden Error Page
   If you arrived here due to a search or clicking on a link click your Browser’s back button
   to return to the previous page. Thank you.

   I found out this message by the ‘BulletProof Security’ and also found ‘BulletProof Security’ not to allow accessing the file which has ( or ) in its filename. So, I changed from Asus_HCL_X51C_(T12C).pdf to Asus_HCL_X51C-T12C.pdf. Now I don’t have the errors. that’s.it.

Edit2(Dec.3):
   I got an update to version .49.7 today, and we can use “Network Activate” on Network / Multisite now, I just wrote that we were unable to use it though. Of course you can also use it by your old configuration.
   By the way, I’ll write an addition to Edit(Dec.2). BPS does not allow accessing the file which has a space in its file name, either.

Edit3(Dec.4):
   Lately, I edit this page everyday (^_^;). This time, Mr.’BulletProof Security’ blocked my flash movies. When I accessed 高住神社-video1, I got the you-know-message “Movie not loaded”. I directed a doubtful look at the Adobe Flash Player because this phenomenon is usually occurred by the player. But, it is not guilty this time-HaHa.
   I found out this as a solution. Flash swf 403 error – Flash slideshow blocked
   I added the next bold italic letters to the root .htaccess file. That’s it.
   RewriteRule .* index.php [F,L]
   RewriteCond %{REQUEST_URI} (flvplayer\.swf|timthumb\.php|~~|thumbs\.php) [NC]

Edit4(2014.Jul.14):
   Recently, I had a lot of 500 Internal Server Error errors on my server log. First, it looked like related to the font-face decoration. But, I finally found that the .htaccesses of BPS gave them when a URI has a ? at its end. I went to the WordPress Japanese forum and the BulletProof Security Free forum. I got the solution from them. Now, the errors have gone. Happy!!

   If you need more information, please see the following topics.
   IE11(Win8.1),IE10(Win7)で,アクセスしたとき,font.eotについてエラーがでる。
   font-face 500 Internal Server Errors

Edit5(Jul.16):
   I had a lot of 403 Forbidden Errors related to my own site on my http_error_log.txt because of the plugin Broken Link Checker uses Head Method. I’ve known the Broken Link Checker uses Head Method since 2012.Dec.29. But I want to use these two plugins, so, I’ve accepted the situation because I don’t know how I can fix it.

   However, when I checked the .htaccess up for this 500 Internal Server Error, I found the following sentences. Wow!!
# REQUEST METHODS FILTERED
# This filter is for blocking junk bots and spam bots from making a HEAD request, but may also
# block some HEAD request from bots that you want to allow in certain cases. This is not a
# security filter and is just a nuisance filter. This filter will not block any important bots
# like the google bot. If you want to allow all bots to make a HEAD request then remove HEAD
# from the Request Method filter.
# The TRACE, DELETE, TRACK and DEBUG request methods should never be allowed against
# your website.
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^(HEAD|TRACE|DELETE|TRACK|DEBUG) [NC]
RewriteRule ^(.*)$ - [F,L]

   This means I can remove HEAD from it? Immediately I removed HEAD from the .htaccess in my root folder. The .htaccess in my wp-admin folder I leave the default, because the Broken Link Checker doesn’t access to the wp-admin folder.

   It works very well as I expected (*´▽`*).

Akismet API outage.

   When I got home and checked my WordPress comments, the Akismet gave me an error message which surprised me very much. I had a fit and looked for solutions on the Internet, but shortly after the Akismet worked normally again before I did something. According to Akismet blog, it was API outage – November 28th. So, today’s error was not my fault but Akismet’s. What a relief! Hey, Akismet! Don’t scare me!!

   By the way, this late morning, we had our first snow in my town, though it let up soon. Wow.

The translation “Seijō no Ran (青条の蘭)”-#4.

   Thanks for your patience (^_^;). Today, I’ve posted the first part of chapter 2, “Seijō no Ran (青条の蘭)”. He-he.

   I have removed the kanjis from the translation “Seijō no Ran (青条の蘭)”, and about the explanations of them I wrote on my notes. Though the older translations still have kanjis in them, I promise I will change them gradually.

Updating to PHP5.5.6.

   At Nov-13 20:57:44UTC, they released PHP5.5.6.

   According to ( ChangeLog ), it fixes some bugs against PHP 5.5.5, and adds some performance improvements.

   I downloaded a Thread Safe version php-5.5.6-Win32-VC11-x86.zip for my server (Windows7HP+SP1(x86)). It requires VC11. If you don’t have VC11 on your Windows, you must install vcredist_x__.exe before the PHP configuration.

   The text in the file php.ini-production has a change as fixed bug #65939 (Space before “;” breaks php.ini parsing —> [; size of the optimized code.]). So, I also fixed the line in my php.ini though the bug had had no influence on my server.

   As the official PHP binary includes php5apache2_4.dll, I extract the zip archive and replace all PHP5.5.5 files with all PHP5.5.6 files except my php.ini. Then, I restart my Apache. That’s it.

   If you need how to configure PHP5.5, please see the post. It is for a mbstrings user, but the information gives some help for you.

Momijigari(紅葉狩-2013)

   This day was a very clear day following on yesterday, so I went to Momijigari(紅葉狩) at Takasumi jinja(高住神社) as usual. This year I took both pictures and videos. My camera is a Casio product EX-V7, which is a little bit old-fashioned. I am satisfied with its quality of pictures, but I’m not about videos. Of course, the quality of works depends on the creator’s skill, though, ha-ha. Anyway, I’ll show you today’s works. About videos, you maybe have popup windows.

高住神社-video1
高住神社-video1
帰り道-video2
帰り道-video2
Takasumi jinja(高住神社)-1
Takasumi jinja(高住神社)-1
Takasumi jinja(高住神社)-2
Takasumi jinja(高住神社)-2
Takasumi jinja(高住神社)-3
Takasumi jinja(高住神社)-3
Takasumi jinja(高住神社)-4
Takasumi jinja(高住神社)-4
Takasumi jinja(高住神社)-5
Takasumi jinja
(高住神社)-5
Takasumi jinja(高住神社)-6
Takasumi jinja
(高住神社)-6
Takasumi jinja(高住神社)-7
Takasumi jinja
(高住神社)-7

Mantises on Warm Window Screens.

Brown mantis
Brown mantis
Green mantis
Green mantis
   This morning, I found a mantis when I opened the window of the living room. After a while, I saw a mantis again when I plucked some Satsuma mandarins in the garden. This one was green. Uh-oh, I saw the mantis was brown just a while ago. So, I took pictures of both. Today is very comfortable clear day. For them, I think it’s a very comfortable day to hunt. (^o^)

   “Mantises on Warm Window Screens”. Who am I kidding? Someone, make comeback!! m(_”_)m

About the ca-bundle.crt of WordPress3.7.x.

Update information      Edit(2014.Jan.30)    Edit2(May.6)    Edit3(Jun.22)

   I wrote something about the ca-bundle.crt of WordPress3.7.x on the post.

   About it, Oiram gave me A useful information. If you get the same issue “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.“, read the article “Error upgrading WordPress (SSL)”, and do his workaround.

   Thinking back now, in my case, there were some differences from his case. Even now, I do not use his workaround. My SSL certificate system works well after updating to WordPress3.7.1. This time updating did not give me any warnings.

   My server environment is very unique, so, I might have got the issue was slightly different from his.

   Still now, I have two questions.

  1. Why did WordPress ver.3.7 give me the warning about one site only in spite of there were a parent and three child sites on the same WordPress multisite?
    About the setting of the ca-bundle.crt, I found out in the class-http.php. This should have the same effect on all of my sites. Why did one site only have the warning?
  2. Do I need to use Oiram’s workaround though my SSL system works well?

Edit(2014.Jan.30):
   Since January 3rd, I cannot access to the Oiram’s site. For a few people googling by the word “ca-bundle.crt” and reaching here, I uploaded the PDF version of Oiram’s workaround. 「Error upgrading WordPress (SSL)

Edit2(May.6):
   Today, I can access to the the Oiram’s site after a very long interval.

Edit3(Jun.22):
   I wrote an article The solution of “SSL3_READ_BYTES:sslv3 alert handshake failure” on WordPress.

Tried Windows8.1 Pro on the laptop PC (NJ2100), and failed.

   Yesterday, I changed my OS from Windows8 Pro to Windows8.1 Pro on NJ2100. By the way, NJ2100 is an Epson Direct product in Japan. But, I think an ASUS product X51C and this are the same in specs.

   First I backed up my Win8 Pro by AOMEI Backupper.

   Second, I accessed the Store from the Metro UI and tried to update.

Windows8.1 #3
Windows8.1 #3
Windows8.1 #2
Windows8.1 #2
Windows8.1 #1
Windows8.1 #1

   The downloading maybe takes several hours, of course, though it depends on the environment.

   When ending the downloading, it shows us the reboot message. So, reboot the PC.

   I had no problem until this point. However, even after several hours, the installation did not end, the monitor displayed nothing and the HDD indicator never lighted up. I gave it up, and turned off the PC. When I turned it on, the PC restored Windows8 Pro and gave me an error code “0xC1900101 – 0x30018”. According to information on the Internet, the error seems to happen the PC has driver(s) which is older than Windows8.1 Pro requires. As my six sense told me the driver was the driver for “SiS Mirage 3 Graphics” (^_^;), I removed it and tried again.

   This time, I reached the goal. I tried to use the Windows8.1 Pro. The monitor resolution was 1024×768, so I installed the driver for “SiS Mirage 3 Graphics” again. But after that, I had a lot of freezes. Besides, I felt the High Definition Audio driver version 6.0.1.5506 did not work well, either. These two drivers are very necessary for comfortable using NJ2100. I can still use my Windows8 Pro. So, I decided that I kept my Windows8 Pro until updating to Windows8.1 Pro was absolutely required.

   I backed up the new Windows8.1 Pro because I didn’t want to waste my time again, and restored the old Windows8 Pro to my NJ2100.

Apache: Use mod_deflate.

   Yesterday, I changed several settings in Apache conf file.

   Open the httpd.conf.

  1. Uncomment the line to use the module mod_deflate for HTTP compression.
          LoadModule deflate_module modules/mod_deflate.so
  2. Uncomment the line to use the directive AddOutputFilterByType
          LoadModule filter_module modules/mod_filter.so
  3. Uncomment the line to use the directive Header
          LoadModule headers_module modules/mod_headers.so
  4. Uncomment the line to use the module mod_expires.
          LoadModule expires_module modules/mod_expires.so

   Add the next lines to the httpd.conf. About this, I have something not to understand, though.
      # Enables generation of Expires headers
      ExpiresActive On
      # expire images and some applications after a month in the client’s cache
      ExpiresByType image/gif A2592000
      ExpiresByType image/jpeg A2592000
      ExpiresByType image/png A2592000
      ExpiresByType text/javascript A2592000
      ExpiresByType text/css A2592000
      ExpiresByType application/javascript A2592000
      ExpiresByType application/x-font-woff A2592000
      # HTML documents are good for a week from the time they were changed
      ExpiresByType text/html M604800
      ExpiresByType text/plain M604800
      ExpiresByType text/xml M604800
      # Enabling Compression
      AddOutputFilterByType DEFLATE text/html text/plain text/xml text/javascript text/css application/javascript
      BrowserMatch ^Mozilla/4 gzip-only-text/html
      BrowserMatch ^Mozilla/4\.0[678] no-gzip
      BrowserMatch \bMSIE\s(7|8) !no-gzip !gzip-only-text/html
      # Make sure proxies don’t deliver the wrong content
      SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ dont-vary
      Header append Vary User-Agent env=!dont-vary