| LifeType 1.1 Upgrade |
出自LifeType 中文文件計畫
目錄 |
升級到LifeType 1.1
在開始升級為LifeType 1.1之前，請記住重要的一件事：並非所有的模版與外掛程式，都能夠直接在LifeType 1.1上正常運作。請勿在LifeType 1.1上使用尚未完成修改的外掛程式或模版，若是你的Blog或是Blog社群相當依賴外掛程式或是模版，歡迎協助開發團隊完成外掛程式或模版的修正工作。為確保使用者升級過程能夠一切順利，開發團隊已經先行將幾個重要的、且較受歡迎的外掛程式與模版，修正為適合LifeType 1.1使用的版本。
LifeType 1.1模版相容列表這個頁面，已經表列出完成修改的模版； LifeType 1.1 外掛程式相容列表這個頁面，已經表列出完成修改的外掛程式。
另外，若是你的Blog社群開放使用者自行新增模版，那麼請務必記住：這些模版也必須修改，否則可能會有無法使用的情況，甚至這些模版也無法使用某些LifeType 1.1新增的功能，例如：分頁功能。如何修改模版，請參閱移植模版教學一文，裡面有詳細的修改方式。
總之，你必須建議Blog社群使用者修正模版，才能讓Blog社群使用者享受新的功能，假若社群使用者不知道該如何修正模版，社群管理者可以使用新的「管理模式」功能，強制將這些使用者的模版，置換成可以正常運作無誤的模版。
安裝需求
LifeType 1.1 的安裝需求與 LifeType 1.0 相同：
- Apache網頁伺服器
- PHP 4.1.x 或 PHP 5.x
- MySQL 3.23 或更高
下載與安裝
開始下載、執行升級步驟前，請先閱讀以下說明
備份舊版 Life Type 的資料
在下載 LifeType 1.1 之前，強烈建議先進行舊版 Life Type 資料備份的動作！備份範圍包含：
- 所有舊版 LifeType 的PHP程式碼與class資料夾，如果有自行修改過程式碼，也請一併備份。
- 所有經過修改過的模版，包含blog社群使用者新增的模版。
- gallery資料夾底下的所有資料。
在tmp資料夾底下出現的文件、內容不需要備份。
備份工作的最重要部分，就是將目前運作中的SQL資料庫備份，你可以使用你熟悉的工作來對資料庫進行備份，例如 phpMySQLAdmin。備份資料庫的目的在於：雖然升級的方式已經過測試，但升級過程中，你不能預期會發生什麼狀況，使得資料發生錯誤，因此備份資料庫是必要的動作。
下載檔案
LifeType的釋出版本，一直都存放在 SourceForge 的專案頁面。你可以在此下載到 LifeType 的最新版本。
解壓縮與上載檔案
若是你已從 LIfe Type 計劃的網頁中下載了 Life Type 的軟體，這檔案將會以一種封存的檔案格式存在你的電腦中。使用 Windows 的使用者，WinZip 可以讀取並解壓縮 .tar.gz 和 .tar.bz2 的檔案封存格式。同樣的檔案格式在 Mac OS X 中可以用類似的軟體解壓縮或是可以開始一個終端機的視窗然後用 tar 來解開壓縮。
在上傳新版本的 Life Type 前，建立一個 config/config.properties.php 的備分檔以防止在上傳的過程中會用預設的檔案將它取代。
在建立舊版本的 config.properties.php 後，除了 gallery/ 和自製的模版外，將其餘的檔案完全刪除。在過去，曾經發表過 Ftp 軟體無法如期望般的用新版本的檔案完全覆蓋舊版本的檔案，而發生了新舊版本混合執行的現象，因為在升級新版本，建議先刪除舊版本的 Life Type 檔案。
然後，可以上傳新版的 Life Type 到伺服器上。
一旦所有檔案上傳完成，將升級前保留的 config/config.properties.php 上傳到伺服器上，覆蓋目前的 config/config.properties.php。
執行 wizard.php。Wizard.php 將會偵測既有的設定檔設定，並且開始自動升級的過程。(請仔細閱讀升級過程中的訊息)
升級的相關設定
在開始升級的過程中，並沒有什麼特別的需求，只需要確定 'tmp/' 是可寫的。因為只是執行升級，在升級過程中，升級精靈 不會 對 config/config.properties.php 做寫入的動作，所以不需要像安裝的新的 Life Type 一樣，將此檔設定成可覆寫的狀態。
升級精靈
升級精靈會指導使用者升級的步驟，將LifeType 1.0.x 版本升級至LifeType 1.1。這裡所說的升級過程，適用於任何LifeType 1.0版本（LifeType 1.0到 LifeType 1.0.6）升級到新版本。然而，若要從 pLog 0.3.x（或更舊版本）升級至最新版，並不適用直接執行新版 wizard.php 的方式。我們強烈的建議使舊版使用者：先將你的 pLog 0.3.x 升級為任何 LifeType 1.0版本，再從LifeType 1.0版本升級至最新的LifeType 1.1版本。
執行 wizard.php後，會先檢查 config/config.properties.php裡面是否已經寫入資料，若有，則會自動開始升級流程。也是因為這個原因，在「下載與安裝」的說明部分，才要使用者在上傳前先行備份 config.properties.php。如果config/config.properties.php裡面沒有任何資料，這樣執行 wizard.php代表開始新的安裝，就不是算是升級。
檢查
This step will perform some basic checks to your environment to verify that it complies with the software requirements. Some requirements are strict (the installer will not proceed until they have been fulfilled) while other requirements are only recomendations and the installer will allow you to proceed with the installation process although it will display a warning message.
If everything is correct, there will be a button labeled "Next" at the bottom right corner.
更新
Wizard.php will now display the current configuration settings and ask us to confirm that they are correct. If they are, we can proceed to the next step.
It is not possible to change these values here in case they are not correct, so if they are not, the file config/config.properties.php will need to be edited manually and the upgrade process restarted.
資料庫變更
In this step the wizard will make the changes needed to some of the currently existing tables and will create some new ones. These are only changes to the database schema, and no data will be modified at this point.
These changes will be carried out automatically and no user interaction is needed. Once the changes are ready, the installer script will display a confirmation window and will allow us to move to the next step.
資料變更
In this step, the installer script will make all the necessary changes to the data (the format of some of the data required to function properly has changed)
This process is entirely automatic and will make your browser reload several times during the process. In case there is a huge amount of data, it would not be possible to update everything in one go without hitting either PHP's script execution limit or the browser's timeout, so data is processed in small increments. In order not to require users to click a button to proceed through each one of these incremental steps, the browser will reload itself until data has been totally processed.
NOTE: please do not attempt to click the refresh button or stop the process, or data will be left in an inconsitent state. If for whatever reason the process interrupts, the only way to get it started again is to restore the back up copy that was taken before starting the upgrade and try again.
Once all the article data has been converted successfully, the installer script will move to the next step where it will convert the rest of the data (categories, comments, etc)
完成安裝
到這一步，安裝程式已經完成所有必要的修改，並已將 LifeType 1.0 升級到 1.1。請不要忘記移除 wizard.php。
模版與外掛程式升級
When upgrading to a major releases, chances are that there have been changes as the API level which affect both plugins and templates.
This means that after, for example, getting our instance upgraded to LifeType 1.1 from LifeType 1.0.x we will have to also download and install updated versions of the plugins and templates that we are using. In case one of the needed plugins has not been updated yet, chances are it might still work if the API calls it uses have not been changed. If it helps, only about 30% of the 1.0 plugins worked right away in 1.1 without any changes.
Please remember to update your plugins before even attempting to test your new installation, or else you might get unexpected results. The Plugins page lists all the plugins available for LifeType 1.1, and those that have not been ported yet are listed in the Unported section.
Regarding templates, most of them should work right away in LifeType 1.1 although they will not use some of the newest features (such as paging) until they have been updated. The Templates page lists all the available templates and Porting Templates outlines all the changes necessary to get older templates working with LifeType 1.1.
Obviously if any of your templates uses a plugin that has not been updaded to work with LifeType 1.1, this will cause some extra trouble.
維護版本的升級
The project will usually release a few maintenance/bugfix releases during the lifetime of a "major" release. This means that once LifeType 1.1 is out, LifeType 1.1.1, 1.1.2 and as many as needed may be released to fix issues found with previous releases. These releases do not usually add new features and do not change the API. This ensure that plugins and customizations developed for LifeType 1.1 will work with any of the releases of the 1.1.x branch.
When upgrading to the latest release of the current stable branch there are two possibilities: download the full release package or alternatively, use an "upgrade" package to upgrade from one point release to another, such as from 1.1.1 to 1.1.2.
Regardless of the upgrade package used, there is no need to use wizard.php when upgrading to a minor/maintenance release.
使用更新包升級
Upgrade pacakges are smaller and therefore faster to download and upload in your server since they only include the files that were changes in the release. Additionally, these packages are useful if you maintain a customized version of LifeType and need to know which files changes.
Upgrade packages are usually noted as lifetype-1.1.X-upgrade-1.1.Y where X is the previous release from which to start upgrading and Y is the new release.
Upgrading using the upgrade package is the recommended option as it saves a lot of time. However the disadvantage is that this upgrade packages only allow to upgrade in sequential releases, i.e. only from 1.1.1 to 1.1.2, so the only way to upgrade from 1.1.1 to 1.1.5 is to either go through all the upgrade packages in sequence or grab the full 1.1.5 package and overwrite all files in our 1.1.1 installation.
