Magento 社区 VS. Magento Enterprise 编码方式
我开发了 Magento 社区版的扩展。 我想在企业版上测试一下。 我怎样才能做到这一点？ 您认为这些版本之间的代码会有变化吗？
谢谢
I have developed an extension to Magento Community edition.
I would like to test it on the Enterprise edition.
How can I do that?
Do you think there will be changes between those versions code-wise?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我每天都用EE。我能检测到的所有差异都以“app/code/core/Enterprise”中的额外模块的形式出现，类名以“Enterprise”而不是“Mage”开头，有些是用 ionCube 编码的。还有一个“企业”主题，但它与“现代”非常相似。 Magento 的其余部分与社区版相同，因此您的扩展可能在两者上同样有效。
但是你不能在没有经过测试的情况下声称兼容性，这是不负责任的。您可能覆盖了某些内容，然后又被其他版本重新覆盖。您可能不想为此购买一年的许可证，因此您必须寻求志愿者，最好的地方是 Magento 的 论坛和聊天。如果您无法在众多自由程序员网站之一上为有能力提供帮助的人做广告，那么这将比整个 EE 副本便宜。
最后是在 Magento Connect 上注册的问题。迄今为止只有awardWorks有幸出现在《企业版》中。部分。 （“专业版”部分尚未激活。）尽管您始终可以在自己的网站上解释重要部分，但您可能没有机会在那里列出您的扩展。
I use EE daily. All the differences I can detect are in the form of extra modules in "app/code/core/Enterprise", class names start with "Enterprise" instead of "Mage", some are encoded with ionCube. There is an "enterprise" theme too but it is very similar to "modern". The rest of Magento is the same as the Community Edition so your extension will likely work on both equally.
However you cannot claim compatibility without testing it, that would be irresponsible. It is possible you have overridden something which is then later re-overridden by the other edition. You probably don't want to buy a years licence just for that so you'll have to ask for volunteers, the best places are Magento's forum and chat. Failing that you could advertise on one of the many freelance programmer sites for someone who is in a position to help, that will be cheaper than a whole copy of EE.
Lastly there is the issue of registering on Magento Connect. So far only aheadWorks have the privilege of appearing in the "Enterprise Ed." section. (The "Professional Ed." section isn't even active yet.) You may not get a chance to list your extension there although you can always explain the salient parts on your own website.
Magento 企业版与社区版的不同之处在于以下几点：
1) 有额外的模块来补充 Mage 模块。它们都有 Enterprise 命名空间（Enterprise_ 前缀而不是 Mage_ 前缀）。企业模块要么添加一些新功能，要么修改 Mage 模块的行为。
2）企业有自己的设计方案。大约 30% 的模板被覆盖，其他模板则回退到 base/default 主题
3) Enterprise 有不同的许可证
因此，回顾上面提到的内容，如果不在 EE 上进行测试，则无法保证 CE 扩展的稳定工作。您的模块很可能会正常分叉，但我估计您的扩展需要进行一些修复才能与 EE 正常工作的可能性为 10%。
严格来说，您可以仅使用自己的 Magento EE（10 000 美元以上）来测试您的扩展。
不过还有另一种方法。 Magento EE 许可证允许买方向正在为买方的 Magento 开发某些功能的人员授予其 Magento EE 版本的访问权限。因此，您可以将您的扩展出售给拥有 Magento EE 的人，并通知他，该扩展尚未在 EE 上进行测试，您需要进行测试。您的客户将允许您访问他的 Magento EE，您将能够测试和调试该扩展。这符合 Magento EE 许可证，因为您将成为 Magento EE 所有者的受雇开发人员，并且您将为他的 Magento EE 开发扩展。
当然，您应该注意，您在 Magento Connect 的帐户必须具有发布 EE 扩展的特殊权限 - 普通帐户无法执行此操作。您需要询问 Magento 支持人员如何获得此类权限。
从我自己的角度来看，我建议不要理会 EE 功能，因为执行整个测试过程并将其作为 EE 扩展发布并不容易。 CE市场更广阔（虽然不是那么赚钱），所以你可以在这里卖。
Magento Enterprise edition differs from Community edition by following items:
1) There are additional modules, that complement Mage modules. They all have Enterprise namespace (Enterprise_ prefix instead of Mage_ prefix). Enterprise modules either add some new functionality, or modifiy behaviour of Mage modules.
2) Enterprise has its own design scheme. About 30% of templates are overriden, others fall back to base/default theme
3) Enterprise has different license
So, reviewing mentioned above, you cannot guarantee stable work of your CE extension without testing it on EE. It's very probable that your module will fork fine, but I'd estimate a 10% probability that your extension requires some fixes to work normally with EE.
Strictly speaking, you can test your extension only having your own Magento EE ($10 000+).
However there's the other way. Magento EE license allows the buyer to give access to his Magento EE version to people, that are developing some functionality for buyer's Magento. So you can sell your extension to someone having Magento EE, notifying him, that it was not tested on EE and you need to do it. Your client will give you access to his Magento EE and you'll be able to test and debug the extension. That conforms Magento EE license, because you'll be a hired developer for Magento EE owner and you'll be developing extension for his Magento EE.
Of course you should notice that your account at Magento Connect must have special access to posting EE-extensions - usual account can not do this. You need to ask Magento support how to get such privilege.
From my own opinion I recommend do not bother with EE functionality, as it's not easy to perform whole process of testing and posting it as EE extension. CE market is wider (although not so money-full), so you can sell it here.
我同意 Clockworkgeek 的观点，即您可能不会遇到任何问题，但 Magento EE 中存在您需要注意的覆盖。请务必找到 EE 安装进行检查，因为可能会有更改。
I agree with clockworkgeek that you are likely not to have any problems, but also that there are overrides in Magento EE that you need to be aware of. Please do find an EE installation to check on, as there may be changes.
我开发了一个magento模块。在我的本地环境中，它适用于社区版和企业版。将其安装在现场站点后，它对于社区版可以正常工作，但对于企业版则不行。它没有显示企业版中的任何管理配置。我错过了什么吗？
I have developed a magento module. It works fine for community edition and enterprise edition in my local environment. After installed it in the live site it works fine for community edition, but not for enterprise edition. It is not showing any admin configuration in enterprise edition. Am I missing anything?