// 擇一使用即可，依不可行性排序

01. 自己的主機 or 虛擬主機且可以修改 php.ini

a. 修改 php.ini 裡 max_execution_time 的數值，重新啟動 Server
b. .htaccess 加上 php_value max_input_time 300
c. wp-config.php 加上 set_time_limit( 300 );

02. 虛擬主機 : 不可以修改 php.ini

a. .htaccess 加上 php_value max_execution_time 300
b. wp-config.php 加上 set_time_limit( 300 );

// 如果主機有安裝 suPHP
.htaccess file 的 php_value max_execution_time 300 改成 max_execution_time = 300

Ref :
01. PHP Runtime Configuration
02. PHP set_time_limit ( int $seconds )

01. 下載 Stealth Login 並解壓上傳到 ./wp-content/plugins/ 下。
// 或從 WordPress 後台直接搜尋 Stealth Login 下載

02. Plugins -> Installed -> Activate Stealth Login

03. WordPress 後台 -> Settings -> Stealth Login

04. 把 Enable Plugin 切換到 On，然後依據您的需要來設定您想要的網址形式，含 WordPress 登入、登出、註冊、後台的位置。

eg :
Login Slug : in -> http://who-know.com/in/；Logout Slug : out -> http://who-know.com/out/；Register Slug : reg -> http://who-know.com/reg/；Admin Slug : admin -> http://who-know.com/admin/

05. 把 Stealth Mode 切換到 Enable，不然就變成 http://who-know.com/reg/ = http://who-know.com/wp-login.php?action=register 兩種網址形式都可以用來註冊帳號，這樣就沒有達到保護 WordPress 的用意了，我們希望的是透過修改 WordPress 登入、登出、註冊、後台的網址，來保護我們用心經營的聖地。

06. 最後它會生成一大串的語法加到 .htaccess file，接下來請立刻測試有沒有成功，如果您的 WordPress 是安裝在子目錄的且有使用 Permalink( 中譯 : 永久連結、固定網址、偽靜態等 )，可能會有問題。

eg : 假設您的 WordPress 原本是裝在 ./wordpress/ 下，您會發現剛才改的網址變成 http://your.domain.name/wordpress/wordpress/ ...，所以請下載 .htaccess file 把 RewriteBase /wordpress/ 修正一下再上傳覆蓋，即可解決問題了。
// 把 RewriteBase /wordpress/ 改成 RewriteBase /

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
# STEALTH-LOGIN
...
# END STEALTH-LOGIN
...
</IfModule>

# END WordPress

07. 附註
a. 設定好後，把 ./wp-content/plugins/ 下的 stealth-login 刪除，好像也可以正常運作。
b. 無聊也可以定期幫它換一下 stealth_folderName_key
// WordPress 後台 -> Settings -> Stealth Login -> Save Changes

Ref : // 紀錄一下其它方法，其中第二個方法很原始也很暴力
01. Who Else Wants to Hide Their Wordpress Folder?
02. How To Change "wp-admin" Folder Name on Wordpress

02. 以下由易達成性來做排序

  a. 使用 PSPad, NotePad++, EmEditor, UltraEdit 或其它的好一點的文字編輯器, 來另存成 UTF-8 且選擇不要添加 BOM 標籤。

    PSPad : 格式 -> UTF-8 -> 存檔
    UltraEdit : 檔案 -> 另存新檔 -> 格式選 UTF-8 無 BOM
    NotePad++ : 格式 -> 編譯成 UTF-8碼 (檔首無 BOM) -> 存檔
    EmEditor : 檔案 -> 另存新檔 -> 編碼選 UTF-8, 下方的加入一個 Unicode 籤名 (BOM) 不要打勾

  b. 檢查 wp-config.php 的 <?php 前, 和 ?> 後是否有多於的空白或空行。

  c. 使用 Windows 內建的記事本打開 wp-config.php, 然後直接另存新檔, 編碼請選擇 ANSI。

  d. 到 WordPress.zip 或 WordPress.tar.gz 下載最新版本的 WordPress, 解壓出 wp-config-sample.php, 改檔名成 wp-config.php, 再依您實際狀況, 來修改 wp-config.php 裡面的設定。

  e. 於 php.ini 添加或修改

output_buffering = On

或

output_buffering = 4096

// 如果您使用的是虛擬主機, 且可以修改 php.ini, 那就在 php.ini 添加上面兩句其中一句; 如果主機是自己的, 那就打開 php.ini, 把 output_buffering 設定成 On 或 4096。

; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit. You can enable output buffering during runtime by calling the output
; buffering functions. You can also enable output buffering for all files by
; setting this directive to On. If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = Off

03. 為什麼這個問題大部分發生在大陸用戶呢? 分別看了 CN 和 TW, 就不難發現

a. CN 的做法是: WordPress en + zh_CN.mo, zh_CN.po, 翻譯過的 wp-config-sample.php, readme.html, setup-config.php 的整合包
b. TW 的做法是: WordPress en + zh_TW.mo, zh_TW.po 語言包

如果您用好一點的文字編輯器, 或者是讓安裝程式自動由 wp-config-sample.php 產生 wp-config.php, 那您可能不會遇到這個問題, 還會感覺 CN 真貼心, 連安裝過程都翻譯成您熟悉的語言了。

04. 如果您 wp-config.php 都打開了, 那不妨順便添加下面 2 句

define('WP_POST_REVISIONS', false);
define('AUTOSAVE_INTERVAL', 86400);

  a. AUTOSAVE_INTERVAL : 用來設定自動儲存的時間間隔, 單位為 sec 秒。

  b. WP_POST_REVISIONS 用來設定文章版本數 : false 那邊可以改成 -1 (同 true), 0 (同 false), >1 的整數, 如果您希望每個修改的版本都儲存下來; 那就設定成 -1 (同 true), 如果您希望關閉文章版的的功能, 那就設定成 0 (同 false); 如果您希望只要保存一固定數量, 就設定成 >1 的整數。

true (default), -1: store every revision
false, 0: do not store any revisions (except the one autosave per post)
(int) > 0: store that many revisions (+1 autosave) per post. Old revisions are automatically deleted.

如果之前的文章版本已經積的很多了, 可以利用 phpMyAdmin 來刪除, 不過記得先備份資料庫喔。
// 也可以用 Delete-Revision 這個插件來做刪除。

DELETE FROM wp_posts WHERE post_type = "revision";

// 沒有說一定要用 phpMyAdmin 才能刪除, 而是一般虛擬主機大多提供的是 phpMyAdmin 所以 ..., 如果要用 MySQL command-line 或其它的工具也是可以的喔。

  c. 另外, 如果出現 Fatal error: Allowed memory size of xxx bytes exhausted (tried to allocate xxx bytes) in ... 則可以加上下面那句, 如果 64M 還是不夠就把數字再改大一點。但是如果您的主機商有限制 Memory limit 上限, 那就只能停用一些較沒再使用的外掛。

define('WP_MEMORY_LIMIT', '64M');

// 有些人會去改 ./wp-settings.php, 但每升級一次就要改一次, 所以改 wp-config.php 會比較好。

if ( !defined('WP_MEMORY_LIMIT') )
  define('WP_MEMORY_LIMIT', '32M');

// 另外, 修改 php.ini 也是一個辦法

memory_limit = 16M

// 最後, 修改 .htaccess file 也可行, 加上

php_value memory_limit 96M

// 如果您的虛擬主機有安裝 SuPHP, 則 .htaccess file 請改成

memory_limit = 96M

Ref:
01. UTF-8, UTF-16, UTF-32 & BOM

# 301 Redirect Non-WWW to WWW
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(who-know\.com)(:80)? [NC]
RewriteRule ^(.*) http://www.who-know.com/$1 [R=301,L]

02. Redirect WWW to Non-WWW
// eg: Redirect www.who-know.com to who-know.com, 於 .htaccess file 加上

# 301 Redirect WWW to Non-WWW
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www\.who-know\.com)(:80)? [NC]
RewriteRule ^(.*) http://who-know.com/$1 [R=301,L]

03. 如果覺得自己改有點麻煩, 可以利用線上製作 .htaccess file ( 繁 簡 英 日 ) 來產生, 點左邊的設置WWW(w) -> 然後填上您希望統一的網址 -> 複製貼上到您的 .htaccess file
// 參考上面舉的例子, 複製須要的部分即可, 用不到的就不用管它。

<Files ~ "^.(htaccess|htpasswd)$">
deny from all
</Files>
order deny,allow

04. 上傳完 .htaccess file, 可以利用 HTTP Server Header Checker, SEO Tools - Search Engine Friendly Redirect Checker 來檢查是否設定成功。

05. 關於上面 Rewrite Rule 所用到的 NC, $1, R, L 的解釋

  a. [NC] (no case) Case-insensitive, ignoring difference between 'A-Z' and 'a-z' when Pattern is matched against the current URL.

  b. $1 is magically replaced with the text which was captured previously. ( $ stuff means plug in whatever follows )

  c. L - Last Rule. No more rules will be proccessed if this one was successful.

  d. R[=code] - Redirect. The user's web browser will be visibly redirected to the substituted URL. If you use this flag, you must prefix the substitution with http://www.somesite.com/, thus making it into a true URL. If no code is given, then a HTTP reponse of 302 (temporarily moved) is sent.

06. 另外, 大家常說的 301、302, 實際上是 301、307?

  a. 301 Moved Permanently

The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.

The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

  b. 302 Found

The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

  c. 307 Temporary Redirect

The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.

If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

08. 由於實在太好奇 302 v.s. 307, 於是又 Google 了一下, 終於發現原因了, 原來一個是 HTTP/1.0 Hypertext Transfer Protocol (下面), 一個是 HTTP/1.1 Hypertext Transfer Protocol (上面)。

  a. 301 Moved Permanently

The requested resource has been assigned a new permanent URL and any future references to this resource should be done using that URL. Clients with link editing capabilities should automatically relink references to the Request-URI to the new reference returned by the server, where possible.
The new URL must be given by the Location field in the response. Unless it was a HEAD request, the Entity-Body of the response should contain a short note with a hyperlink to the new URL.

If the 301 status code is received in response to a request using the POST method, the user agent must not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

  b. 302 Moved Temporarily

The requested resource resides temporarily under a different URL. Since the redirection may be altered on occasion, the client should continue to use the Request-URI for future requests.
The URL must be given by the Location field in the response. Unless it was a HEAD request, the Entity-Body of the response should contain a short note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request using the POST method, the user agent must not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Ref: // 其實只有參考第一個, 複製了它的解釋, 其它篇是覺得寫得不錯, 值得收藏一下^^
01. mod_rewrite, a beginner's guide (with examples)
02. 301-redirect
03. Apache mod_rewrite
04. SEO Tips - Mod Rewrite Non-WWW to WWW
05. Using Mod-rewrite to Redirect Non-www URL to www URL
06. Improve Your SEO By Redirecting Non-WWW Traffic to WWW
07. Redirect Visitors From Non-WWW To WWW Version Of Your Website With .htaccess And mod_rewrite

<?php phpinfo(); ?>

查看了自己的 Server 是否有支援 GZIP, 發現恰是一切正常.

HTTP_ACCEPT_ENCODING  gzip, deflate
_SERVER["HTTP_ACCEPT_ENCODING"] gzip, deflate
_ENV["HTTP_ACCEPT_ENCODING"] gzip, deflate

02. 於是分別在 .htaccess file 加上

a. 結果出現 HTTP 500 - Internal Server Error.

php_flag zlib.output_compression on
php_value zlib.output_compression_level 4

b. 第二種沒反應 // that is, 不支持 mod_deflate

<ifmodule mod_deflate.c>
DeflateCompressionLevel 4
AddOutputFilterByType DEFLATE text/html text/plain text/xml application/x-httpd-php
AddOutputFilter DEFLATE js css
</ifmodule>

03. 兩種都沒成功, 於是又上網 Google , 找了好久才發現如果主機有裝 SuPHP, 寫法會有不同, 要稍稍修正。

When SuPHP is enabled, it is no longer possible to to include php_value directives in .htaccess files.

Instead of adding these directives to your .htaccess file, add them into a file called php.in and place this file in the same directory that your script runs in. Most often this will be public_html directory, but in some cases you will install your script in a subdirectory. Wherever your script runs, this is the place for your php.ini file. You will need to drop the "php_flag" and "php_value" prefix. You will also need to put an equals (=) sign between the setting and the value.

a. 前面不要加上 "php_flag" and "php_value"
b. 設定和值中間用 "=" 隔開
c. 原本放在 .htaccess file -> 改放置在 php.ini file

eg:原本放 .htaccess file

php_value max_execution_time 60
php_flag zlib.output_compression on

改後放 php.ini // 目錄下沒 php.ini, 就自己創, 改好後再上傳, 非 php.ini.txt 喔

max_execution_time = 60
zlib.output_compression = on

所以原本在 .htaccess file 的寫法, 要改成下面的樣子, 然後放置於 php.ini

zlib.output_compression = on
zlib.output_compression_level = 4

04. 最後, 別忘了來 Gzip Test 驗收成果

ps.
a. 如果啟用 Gzip 出現 HTTP 500 - Internal Server Error, 很可能就是您的虛擬主機有使用 SuPHP
b. JustHost 有使用 SuPHP
c. 沒特別設定 compression level 的話, 預設是6, 數字可以是 1~9
d. Compression test : 32,380 bytes // 超過 4 級就沒什麼差別了

Level 1: 9,161 bytes 71.7%
Level 2: 8,915 bytes 72.5%
Level 3: 8,757 bytes 73.0%
Level 4: 8,400 bytes 74.1%
Level 5: 8,215 bytes 74.6%
Level 6: 8,155 bytes 74.8%
Level 7: 8,120 bytes 74.9%
Level 8: 8,108 bytes 75.0%
Level 9: 8,100 bytes 75.0%

Ref:
01. All servers having SuPHP installed for added security
02. How to use gzip compression on your PHP websites
03. Force GZIP compression on your HostMonster-hosted website
04. GZIP files

a. 請到這下載 WP-WaterMark，解壓上傳至 /wp-content/plugins/ 下，並在後台啟用。
// 有兩種版本，一種是 with fonts、without fonts，如果您是要加自己的圖片 or 有自己較喜歡的字型，那下載 without fonts 即可。

b. 打開 /wp-admin/includes/media.php，用 Ctrl+F 找到 "function media_handle_upload" 或 "// Save the data"，然後在適當位置 "// Save the data" 前加入下面的 code

    // For WP WaterMark
    MM_Execute_WM( $file, '' );

c. 圖片浮水印 : 請把 /wp-content/plugins/watermark/ 下的 stempel.png 換成您想要加的 logo。

d. 文字浮水印 : 請上傳您想用的字型到 /wp-content/plugins/watermark/fonts/ 下。

e. 請移駕玉步到 WP 後台 -> Settings -> Watermark -> 進行設定。

啟用 -> 選位置 (用Offset微調) -> 選圖片型 Watermark 浮水印 -> Save。

啟用 -> 選位置 (用Offset微調) -> 選文字型 Watermark 浮水印 -> 設定字型、大小、顏色(Html Color Code)、要顯示的文字、不透明度 (100:完全不透明，0:完全透明)、陰影。

f. 這樣只要自 WP 後台上傳的圖片，都會自動加上 浮水印 Watermark 了。

02. 這不是一個專屬於 WordPress 的 Plugin，但這邊就先介紹怎麼把它應用於 WordPress 來自動添加 Watermark 浮水印。

a. 請到這下載 Watermark Script，解壓，上傳至您 WordPress 所在的目錄。
// That is, empty.png, watermark.png, and watermark.php 和 wp-admin, wp-content, and wp-include 是在一起的。

b. 請把下面的 code 加到您的 .htaccess file。.htaccess file 天生穿著隱形斗篷，如果想要看到它，要開啟類似 show hidden files 顯示隱藏檔案的功能。
// eg: FileZilla -> Server (伺服器) -> Force showing hidden files

RewriteRule ^(.*)wp-content/uploads/(.*) $1watermark.php?src=wp-content/uploads/$2

c. 照您以前的習慣繼續寫 Blog 和上傳圖片即可自動添加 Watermark 浮水印。

03. GlamourGaby's Watermark Script v.s. Marekkis's WordPress Watermark-Plugin

右邊的 石井香織 Kaori ishii 比左邊的地球 Earth 漂亮，但左邊的地球 Earth 比右邊的 石井香織 Kaori ishii 更重要，那怎麼比啊 ? 不是請您看 Earth 和 Kaori ishii 啦。

如果您注意看的話會發現，用 GlamourGaby's Watermark Script 弄的，看的時候有 Watermark 浮水印，但存的圖片是沒有 Watermark 浮水印的喔；但 Marekkis's WordPress Watermark-Plugin 弄的，卻是表裡如一喔。
所以 Marekkis's WordPress Watermark-Plugin 還能先備份圖片，然後批次加 Watermark 浮水印。

a. 請移駕玉步至 WP 後台 -> Settings -> Watermark-Dir -> 進行設定

Ref:
01. GlamourGaby's Watermark Script
02. Marekkis's WordPress Watermark-Plugin

1. 找到你安裝 Apache 的資料夾，並進到 conf 資料夾 (default:C:\AppServ\Apache2.2\conf)

2. 用 文字編輯器 (eg:NotePad, NotePad++, Emeditor, UltraEditor ... etc ) 打開 httpd.conf

3.
a. 法一
Ctrl + F 找到 #LoadModule rewrite_module modules/mod_rewrite.so 把前面的 # 去掉
b. 法二
Ctrl + H 取代 目標 #LoadModule rewrite_module modules/mod_rewrite.so
取代 LoadModule rewrite_module modules/mod_rewrite.so

4. 用上面的方法把 #AccessFileName .htaccess 前面的 # 去掉 ( 有的default就去掉了 )

5. Restart Apache Server, Done! // 我按Restart沒有用，按 Stop 再按 Start 才成功