問題描述

進行 Magento 更新(維護不善的 Magento 安裝)的最佳做法是什么.

What is the best practice for making a Magento update (of a badly maintained Magento installation).

我想到了以下幾點:

• 查看 app/code/local 中的完整覆蓋模塊 - 將文件與舊版本進行比較，并將它們轉(zhuǎn)發(fā)到新的 Magento 版本
• 比較模板
• 比較布局 XML 文件(如果它們被直接復(fù)制到自定義主題文件夾并且沒有使用僅包含真實更新的單個 layout.xml)
• 比較重寫類的方法與原始類的方法

主要問題是:在舊的、維護不善的 Magento 安裝中比較文件時，您永遠不知道復(fù)制的原始文件具有哪個版本.有時我試圖通過查看文件注釋中的 Magento 版權(quán)來識別舊版本.

The main problem is: When diffing files in old, badly maintained Magento installations, you never know, which version the original file that was copied had. Sometimes I tried to identify the old version by having a look on Magento's copyright in the file comment.

為了避免更新過程中的麻煩，我們通常會執(zhí)行以下操作:

To avoid hassle during update we usually do the following:

• 避免重寫，改用事件
• 如果需要重寫，盡量不要復(fù)制代碼，而是調(diào)用 parent::method() 以在被覆蓋的類中只保留必要的功能
• 如果需要復(fù)制代碼，請使用標記注釋，例如 [Mycompany BEGIN] ... [Mycompany END]
• 不要復(fù)制整個布局文件，而是使用一個只進行更新的 layout.xml.

但是如果沒有采取這些預(yù)防措施，如何進行更新?

But how to do an update if those precautions where not taken?

推薦答案

正如其他人所指出的，這里的關(guān)鍵是讓它與干凈安裝相媲美，所以這里是我將在版本控制的幫助下做的事情.

As others have noted the key here is to make it comparable against clean installation so here's what I would do with the help of version control.

1. 讓自己獲得當前使用的 Magento 的干凈版本，并且不要忘記使其具有可比性.或者使用現(xiàn)有的 magento git 鏡像(參見更多 http://blog.speedupmate.com/post/4063307705/magento-git-mirror )

根據(jù) 1. 在這里設(shè)置一個主存儲庫并準備好

set up a master repo based on 1. here and have it at hand

在評論中提問:您的最終目標是擁有一個干凈的核心，其中包含 magento 安裝文件中存在的 git 中的所有文件.這是必需的，因此您可以將所有內(nèi)容與全新安裝進行比較.管理核心更改，核心文件樹(現(xiàn)有、不存在、添加的文件).您可以使用 .gitignore 處理您的異常(不包括媒體、緩存、具有服務(wù)器特定范圍 local.xml .htaccess 的所有字段).我發(fā)現(xiàn)將 Magento 核心文件移出到不同的(非公共)目錄很容易(如此處所述 http://blog.speedupmate.com/post/9992573819/poor-mans-multisite-setup-for-magento )，這會給我一個代碼狀態(tài)，其中 .htaccess 從不升級沖突.我也從未在版本控制、緩存和 magento 生成的所有臨時文件中包含媒體.這將保證您的升級路徑清晰，因為您可以在升級時間內(nèi)禁用所有功能.稍后比較代碼將為您提供需要概覽的范圍，并且您可以估算比較更改的部分并進行升級所需的時間.

Asked in comments: Your ultimate goal is to have a clean core with all files in git that are present in magento installation files. That is needed so you can compare everything against the clean installation. Managing core changes, core filetree (existing, non-existing, added files). You can handle your exceptions with .gitignore (excluding media , cache, all fiels with server specific scope local.xml .htaccess). I find it easy to move out Magento core files to different (non public) directory (as explained here http://blog.speedupmate.com/post/9992573819/poor-mans-multisite-setup-for-magento ) and that will give me a code state where .htaccess never conflicts on upgrade. I also never include media in version control , cache and all temporary files that magento generates. This will guarantee you clear path on upgrades as you can disable all for the upgrade time. Comparing the code later will give you scope of things you need to overview and you can estimate how long it will take you to compare the changed parts and go live with upgrade.

現(xiàn)在使用您現(xiàn)有的站點和 git config(使其具有可比性)在您的代碼庫上執(zhí)行 git init 并將所有內(nèi)容添加到 git 那里，這將檢查您的 git 配置并使每個文件具有可比性(相同的換行符、空格等)，然后將文件權(quán)限修復(fù)為相同.之后，您可以從您的站點中刪除 .git 文件夾，因為您只使用 git 在那里制作可比較的文件.

now with your existing site and git config in place (to make it comparable) do a git init on your codebase and add everything to git there , this will go over your git config and make every file comparable (same newlines, whitespaces etc) then fix file permissions to be the same. After that you can remove the .git folder from your site as you only used git to make files comparable there.

在評論中提問:這里的重點是讓 git 為您工作，例如將所有行結(jié)尾轉(zhuǎn)換為 unix 樣式并忽略空格，理論上您也可以忽略權(quán)限，但這沒有用(這里的格式有點不對，所以 代表命令之間換行

Asked in comments: The point here is to have git do work for you like converting all line endings to unix style and ignore whitespaces, you can ignore permissions too in theory but that's not useful (formatting is bit off here so represents a line break between commands

git config core.autocrlf 輸入 git 配置 core.eol lf git config apply.whitespace nowarn

現(xiàn)在如果你執(zhí)行 git init并添加這些配置并將所有內(nèi)容添加到 git 然后在提交階段 git 將替換您所有的 Windows 行結(jié)尾和所有廢話，以統(tǒng)一和可比較的樣式.請注意，zend 編碼標準建議使用 unix 樣式的行結(jié)尾，但是您也會看到 Zend 庫不遵循其自身標準的文件.這里的關(guān)鍵點是您需要您的文件具有可比性，以最大限度地減少您必須做的差異負載.在 git 為您格式化所有錯誤的安裝文件后，您將刪除 .git 文件夾.Git 僅用于自動化此步驟中的使事物具有可比性的過程"，沒有其他作用

Now if you do git init and add those configs and add everything to git then during committing stage git will replace all your windows line endings and all that crap to unified and comparable style. Note that zend coding standard suggest unix style line endings however you will also see the files where Zend library does not follow it's own standards. Key point here is that you need your files to be comparable to minimize the diff load you have to do. You will remove the .git folder after git has formatted all your bad installation files for you. Git is only used to automate the "make things comparable process" in this step and nothing else

根據(jù) 1. 中的主存儲庫簽出您的測試存儲庫，并使用您當前所在的版本簽出一個分支并將其命名為testsomething"或您需要的任何名稱

checkout your test repository based from your master repo in 1. and checkout a branch with the version you are currently on and name it "testsomething" or whatever you need

刪除該結(jié)帳文件夾中的所有內(nèi)容并僅保留 .git 以使其為空，但版本控制仍然存在.它將處于所有內(nèi)容都已刪除的狀態(tài)，這在這里很重要，因為您將知道您可能在不良站點上刪除了哪些文件.

delete everything from that checkout folder and leave only .git in place so it is empty but version control still exists there. It will be in state like everything is deleted and this is important here cause based on that you will know what files you might have deleted on your bad site.

在評論中提問:我通常在 git config 中添加忽略空格(本地或全局范圍可用)并讓 git 為我處理.在團隊中工作時，我們總是同意基于 Zend 的標準:4 個空格用于制表符、unix 樣式行結(jié)尾和 3 中提到的 git 配置變量.如果涉及構(gòu)建腳本，我們會使用提交鉤子進行代碼格式化和驗證.

Asked in comments: I usually add whitespace ignoring to git config (local or global scope is available) and let git handle that for me. When working in teams we always agree on based Zend standards: 4 spaces for tabs, unix style line endings and git config variables mentioned at 3. and if build scripts are involved we do code formatting and validation with commit hooks.

將所有文件移動到您的空目錄中(請注意，您已將 .git 目錄從現(xiàn)有站點中刪除，使其具有可比性)從您的 fcked magento 安裝(它們現(xiàn)在可以比較)和運行 git status >更改.txt .該文件現(xiàn)在列出了您擁有的所有差異、您擁有的任何新文件、任何已刪除、重命名的文件，以及您在安裝"中與當前使用的干凈 Magento 代碼相對應(yīng)的文件.