Magento升级

发布于 2024-10-06 21:32:58 字数 440 浏览 2 评论 0原文

我正在寻找将主题/自定义 Magento 从 1.3.x 升级到 Magento 1.9 Enterprise。到目前为止,经过多次尝试升级,都失败了。 第一次升级后,我在干净的环境中上传了新的Magento,将数据库复制到开发数据库。使用这个,升级出现两个错误:看来Magento升级目前仅支持1.4+,并且不包括以前的mysql升级脚本。升级“安装”后,我无法访问管理员或前端,并且没有错误告诉我发生了什么。

放弃了这个想法,我尝试了全新安装:效果很好。然后我尝试从 CSV 导出导入所有产品。工作正常,但图像、尺寸等自定义属性未传输。我有 900 多种产品,手动输入所有内容会很痛苦,而且不可行。放弃这个想法。

现在我处于各种升级配置中,从 Magento 1.3 升级。我打算尝试将 1.3 升级到 1.4,然后将 1.4 升级到 Enterprise,但是之前是否有人成功执行过此类升级并且可能能够提供提示? 谢谢, 布赖恩

I'm looking to upgrade a themed/custom Magento from 1.3.x to Magento 1.9 Enterprise. So far, after multiple attempts at upgrading, I have failed.
After the first upgrade, I uploaded the new Magento in a clean environment, copied the database to a dev database. Using this, the upgrade occurred with two errors: It appears Magento upgrades only support 1.4+ currently, and previous mysql upgrade scripts were not included. After the "install" of the upgrade, I couldn't access wither the admin, or the frontend, and there was no errors to tell me what gives.

Scrapping that idea, I tried a clean install: It worked fine. Then I tried importing all the products from a CSV export. Worked OK, but custom attributes such as images, sizes, etc. didn't transfer over. I have over 900 product, and entering everything manual would be a pain, and unfeasible. Scrapping that idea.

Now I'm at various upgrade configurations, upgrading from Magento 1.3. I'm going to try and upgrade 1.3 to 1.4, and then 1.4 to Enterprise, but has anyone performed such an upgrade successfully before and might be able to provide hints?
Thanks,
Bryon

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

笑红尘 2024-10-13 21:32:58

拜伦,我感受到你的痛苦。一个月前,我在从 1.3 升级到 1.4 的过程中遇到了困难。

尝试这里提到的技术: http://www.webshopapps.com/blog/2010/02/upgrading-magento-to-version-1-4-keeping-it-simple/ 最后它对我有用。

与直觉相反的事情是删除数据库。我一直试图跳过这一步,这让我一度陷入困境。您必须删除数据库并重新加载数据(这会对关键约束产生影响)。最后我能够升级到 1.4,而无需手动移动任何内容。

Byron, I feel your pain. I struggled with an upgrade from 1.3 to 1.4 a month ago.

Try the technique mentioned here: http://www.webshopapps.com/blog/2010/02/upgrading-magento-to-version-1-4-keeping-it-simple/ In the end it worked for me.

The thing that is sort of counter intuitive is the deletion of the database. I kept trying to skip that step, and that's what stymied me for a while. You have to delete the database and reload the data (it does something to the key constraints). In the end I was able to upgrade to 1.4 without manually moving anything.

同展鸳鸯锦 2024-10-13 21:32:58

您应该走路线 1.3 到 1.4 ,1.4 到企业并在此过程中切换到默认皮肤。皮肤/模板稍后需要特别注意,因为 dom 非常不同。将 1.3 模板合并到企业 dom 需要约 2-4 天经验丰富的切片器,他们知道如何使用 diff 工具,

我通常的工作流程是:

  1. 将所有三个 magento 版本添加到 git 并按版本标记,使用您自己的 magento 安装作为基础并忽略默认情况下未安装
  2. 在您的 Web 目录中的模板文件夹和本地/社区扩展,请检查您的基本版本
  3. git pull 1.4 到您的安装并访问网站以获取升级
  4. git pull enterprise 到您的安装并访问网站以获取 按照这样的顺序进行升级

,您还可以删除magento从每个版本中删除的已删除文件,并且您还可以获得所有更改和新文件。

You should go the route 1.3 to 1.4 , 1.4 to enterprise and switch to default skin while doing so. Skin/templates needs special attention later as the dom is quite different. Merging 1.3 templates to enterprise dom will take ~ 2-4 days experienced slicer who knows how to use diff tools

my usual workflow for this is:

  1. add all three magento versions to git and tag by version , use your own magento installation as base and ignore your template folders and local/community extensions that are not installed by default
  2. on your web directory , checkout your base version
  3. git pull 1.4 to your installation and visit the website to get the upgrades
  4. git pull enterprise to your installation and visit the website to get the upgrades

doing it in such order you also get rid of removed files that magento has removed from each version and you also get all changes and new files.

無心 2024-10-13 21:32:58

Magento 企业版 1.9 到 1.9.1 的升级过程
一般来说,所有 Magento 升级都是通过使用旧数据库运行更新后的代码来进行的。差异将被检测到并自动合并到下一页请求中。因此,Magento 会跟踪每个模块的版本号。如果您有自定义代码,则不建议在此升级中这样做。

免责声明 – 如果您有大量定制,升级将会破坏系统;最好在新的(临时)站点上执行此操作,进行比较,错误修复,然后测试,然后跨浏览器测试。
您的一般做法:

  1. 关闭生产服务器全部备份
    DB 和 Magento 安装 转
    关闭所有自定义扩展并且
    主题

  2. 从 HDD 中删除:核心 Magento 模块、其布局、所有标准主题和缓存。

  3. 获取 1.9.1 EE,将其复制到新的数据库安装中,然后将自定义代码放在顶部。
  4. OTB 1.9.0 和 1.9.1 之间的文件比较。特别注意已被覆盖的核心控制器列表,并比较这些控制器在 1.9.0 版本中的差异。和 1.9.1。
  5. 以下是已知问题的列表,这些问题将导致我们的自定义代码返工:

1) Google Analytics(不适用于
1.9.0 并修复它,需要对我们的自定义代码进行许多更改)
2) 平
类别
3) 按属性搜索 –
(xml 修复)
4) CMS中的iFrame问题
页面
5) 缺少管理自定义选项卡
(前后比较)
6) 主页
页面 enterprise_home 必须是
改名了! (这是一个例子
未记录的隐藏陷阱和
代表警告您要考虑的因素
及时解决此类问题)

7)检查法师/社区的新模块

覆盖我们需要的模块。

8) 任何能够扩展客户的事情
实体应该经过严格的测试。

9) JavaScript – 小心 –
实际的js模板可能是相同的,
但是调用的块和模块
他们可能会发生微妙的变化!

10) 定制产品导入 – 进行测试
使用数据流在 1.9.1 上导入产品
方法见

需要哪些数据库字段,然后将它们添加到自定义代码的过程代码中。

  1. 检查主题的发行说明文档和更新,是否支持 EE 1.9。如果支持则将其打开,否则您将需要另一个主题。

  2. 检查所有自定义扩展的发行说明文档和更新 - 是否支持 1.9.1 打开它们 - 逐一打开。

  3. 如果是自动生成的,您在升级所有核心数据库数据时将会遇到问题,请检查哪些字段丢失/更改并添加它们。

  4. 跨浏览器测试 - 您的自定义主题存在问题,您需要检查您的自定义扩展并升级其模板文件、皮肤 CSS 和数据库数据以适应 1.9.1。 。

  5. 测试是最重要的任务,遍历应用程序,注意错误和警告,并修复它们。

Magento Enterprise Edition Upgrade Procedure for 1.9 to 1.9.1
Generally all Magento upgrades work by running the updated code with the old database. The differences will be detected and incorporated automatically on the next page request. Magento keeps track of every module's version number for this reason. This is not advised with this upgrade if you have custom code.

Disclaimer – if you have a lot of customization, the upgrade will break the system; it is best to do this on a new (temporary) site, compare, bug fix, then test, then cross browser test.
Your general approach:

  1. Close production server Backup all
    DBs and Magento installation Turn
    off all your custom extensions and
    themes

  2. Delete from HDD: core Magento modules, their layouts, all standard themes and cache.

  3. Get 1.9.1 EE, copy it into a fresh DB installation, then place custom code over the top.
  4. File compare between OTB 1.9.0 and 1.9.1. Pay special attention to a list of core controllers which have been overridden and compare the difference between these controller in version 1.9.0. and 1.9.1.
  5. Here is a list of known problematical issues which will cause rework in our custom code:

1) Google Analytics (does not work in
1.9.0 and to fix it, many changes are required to our custom code)
2) Flat
Category
3) Searching by Attribute –
(xml fix)
4) iFrame problem in CMS
pages
5) Missing admin custom tabs
(compare before and after)
6) Home
page enterprise_home has to be
renamed! (this is an example of a
hidden pitfall undocumented and
represents a warning to you to factor
in time for such problems)

7) Check Mage/Community for new modules which

override modules which we need.

8) Anything which extends the customer
entity should be rigorously tested.

9) JavaScript – be careful - the
actual js templates may be the same,
but the blocks and modules which call
them may have subtle changes!

10) Custom Product Imports – do a test
product import on 1.9.1 using dataflow
method and see

what db fields are needed then add them into the procededural code for your custom code.

  1. Check release notes documentation and update for your theme, whether it supports EE 1.9. Turn it on if it supports, otherwise you'll need another theme.

  2. Check release notes documentation and updates for all your custom extensions - whether they support 1.9.1 Turn them on - one by one.

  3. You will have problems upgrading all core DB data if it's made automatically, check which fields are missing/changed and add them.

  4. Cross Browser testing - problems with your custom theme, and you'll need to check your custom extensions and upgrade their template files, skin css and DB data to fit 1.9.1.

  5. Testing is the biggest task, walk through the application, notice errors and warnings, fix them.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文