有没有人曾经使用过仅用于后端/管理的 PHP 电子商务平台，并且完全定制的前端仅利用该平台的 API？
标题几乎解释了这一点。
我想完全定制店面，并且通过疯狂的文件（例如，Magento）来完成此操作不是我喜欢的。
但我仍然想要管理员和管理员。 Magento 之类的计算功能 - 例如，折扣/优惠券代码、预定义期间的销售价格、税等。
以前有人这样做过吗...即使您没有，您能否推荐一个在此方面理想的平台情况？
我不喜欢 Magento，因为缺乏文档，并且标准 Web 主机上的性能非常差，即使只是进行 API 调用也是如此。
干杯伙计们！
The title pretty much explains it.
I want to completely customise the shopfront, and working through the madness of files (eg, Magento) to do this would not be my cup of tea.
I do however still want the admin & calculation features of something like Magento - eg, Discount/Voucher codes, Sale Prices over predefined periods, Tax etc.
Has anyone done this before... and even if you haven't, can you recommend a platform which would be ideal in this situation?
I'm not keen on Magento due to lack of documentation and really poor performance on a standard webhost, even when just making an API call.
Cheers guys!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
“那些没学会 Magento 的人注定要重新发明它，而且很糟糕。”
Magento 的性能在共享主机上是一个问题，但是，在一个中等规模的虚拟服务器上，如果启用缓存，则不存在性能问题。通过添加工具“Varnish”、“Nginx”等，可以实现可扩展的性能。有用。
遗憾的是，商店不能简单，只有简单的顾客表、简单的产品表、订单表和快得令人眼花缭乱的性能。然而，Magento 从这里开始（与 OsCommerce），意识到问题/限制，并用最好的编程方法构建了一个更明智的系统。尽管他们的工作非常出色，但仍有很多开发人员认为他们可以在周末编写一个网络商店，并根据需要添加需求。这些“noddy carts”很诱人，但它们不像 Magento 那样功能齐全，也不能以模块化方式扩展，因此它们通常完全是浪费时间。
我不认为 Magento 文档有你想象的那么大问题。 Magento 存在“网络效应”，因此很多“缺失的文档”都可以在 Google 上找到。
最初，布局引擎和“数百万个文件”似乎令人困惑。但是，需要一段时间才能了解其工作原理并获得一些自己的可重复使用的资源。我认为最好学习 Magento 的做事方式，包括模块、布局 xml 和 MVC 方法。认为您可以在 CMS（例如 Expression Engine）中更好地格式化 Magento 块，并仅将 Magento 用于后端，这会让您一无所有，最终会得到一个相当无用的设置，不会有任何进展。
"Those that fail to learn Magento are doomed to reinvent it, badly."
Performance on Magento is a problem on shared hosting, however, on a modest virtual server, with caching on, there is no performance problem. With added tools, 'Varnish', 'Nginx' etc there is scalable performance. It works.
It is a pity that shops cannot be simple with a simple customers table, a simple products table, an orders table and blindingly fast performance. However, the Magento started from this (with OsCommerce), realised the problems/limitations and built a far more sensible system with the best programming methods. Despite their great work there are plenty of developers that think they can write a web shop in a weekend and bolt on requirements to it as needed. Tempting these 'noddy carts' are, they are not full featured or extensible in a modular fashion, as Magento is, therefore they are generally a complete waste of time.
I don't think that Magento documentation is as big a problem as you imagine. There is 'network effect' with Magento hence, a lot of the 'missing documentation' is Google-able.
Initially the layout engine and the 'millions of files' seems confusing. However, it takes a while to learn how this works and to get a few re-usable resources of your own. I think it is better to learn the Magento way of doing things, with modules, layout xml and MVC methods. Thinking you can format Magento blocks any better in a CMS such as Expression Engine and use Magento just for the backend will put you on a hiding to nothing, to end up with a fairly useless setup that isn't going to go anywhere.