3

首先要解决核心问题：是否有人使用过 Ektron 内容 API，并且可以评论使用它们来获取 Ektron CMS 内容，而不是使用原生 Ektron 控件？我想在 ASP.NET MVC 站点中使用这些 API。

现在是背景：我们有一个客户，其现有网站融合了 Ektron（用于基本内容）和用于其他功能（产品数据、电子商务等）的自定义数据库/代码库。我们需要为特定产品线构建相当于微型站点的内容，并满足以下要求：

  • 从 Ektron CMS 驱动尽可能多的基本内容（副本）
  • 大多数其他内容将来自自定义数据库
  • 电子商务功能应与主站点的购物车集成（购物车是定制的，必要时可以扩展）
  • 可能需要共享登录状态（我知道已经有一个解决此问题的 SO 问题）

我宁愿不为 WebForms 和尝试设计 Ektron 控件的样式而苦苦挣扎，所以我建议我们将子站点构建为独立的 MVC 应用程序。Ektron 内容 API 是否足够强大以支持这种方法，或者这条路线只会导致眼泪和梦想破灭？

任何见解都值得赞赏。谢谢！

4

1 回答 1

3

I coded a site with a large proportion of non-Ektron controls, but I used Webforms.MVP rather than MVC. This allowed me to mix-and-match MVP controls with the Ektron controls.

Ektron has got a couple APIs - there is an older web service based API which should be accessible from a non-Webforms project. I am not sure if it is possible to access the newer APIs (i.e. the non-web service API and the newer Framework API) fomr a non-webforms project. You would probably want to do a quick proof of concept for this to confirm.

The robustness of the Ektron APIs is a bit variable. Generally I have found dealing with simple HTML content to be good. Membership/login isn't too bad either. From memory, I've had problems with the more obscure components - eCommerce, Taxonomies, Blogs, Calendars. Generally, the problems include-

  • Empty properties
  • Lack of documentation

The newer Framework API (initial release in v8.0, covering Content and Folders, with a full release in v8.5, due in Aug 2011) is a lot easier to use, though I've still had occasional problems with empty properties.

Overall, as long as you're sticking to HTML content, you should be fine, provided you can access the API from a MVC project.

于 2011-06-09T03:14:40.383 回答