To get the core question out of the way first: has anyone used the Ektron content APIs and can comment on using them to get Ektron CMS content instead of using native Ektron controls? I'd like to use these APIs in an ASP.NET MVC site.
首先要解决的核心问题是:是否有人使用了Ektron内容api，并且可以评论使用它们来获取Ektron CMS内容，而不是使用本地的Ektron控件?我想在ASP中使用这些api。净MVC的网站。
Now the background: we have a client with an existing site that is a fusion of Ektron (for basic content) and a custom database/codebase for other pieces of functionality (product data, ecommerce, etc). We need to build what amounts to a microsite for a specific product line, with the following requirements:
现在的背景是:我们有一个客户端，它有一个现有的站点，该站点融合了Ektron(用于基本内容)和自定义数据库/代码基，用于其他功能(产品数据、电子商务等)。我们需要为特定的产品线构建一个相当于微站点的内容，需要满足以下要求:
- Drive as much basic content (copy) as possible from the Ektron CMS
- 从Ektron CMS中驱动尽可能多的基本内容(拷贝)
- Most other content would come from the custom database
- 大多数其他内容将来自自定义数据库。
- Ecommerce functionality should integrate with the main site's cart (the cart is custom-built and can be extended if necessary)
- 电子商务功能应该与主站点的cart集成(cart是定制的，如果需要可以扩展)
- Login status may need to be shared (I know there is already an SO question that addresses this piece)
- 登录状态可能需要共享(我知道已经有一个SO问题解决了这个问题)
I'd rather not struggle with WebForms and attempting to style Ektron controls, so I would like to recommend that we build the subsite as a standalone MVC application. Are the Ektron content APIs robust enough to support such an approach, or would this route just lead to tears and broken dreams?
我不想与WebForms纠缠，也不想尝试设计Ektron控件的样式，所以我建议将子站点构建为独立的MVC应用程序。Ektron内容api是否足够健壮来支持这样的方法，或者这条路径只会导致眼泪和破碎的梦想?
Any insight is appreciated. Thanks!
任何观点都是感激。谢谢!
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控件的站点，但是我使用了Webforms。MVP,而不是MVC。这让我可以将MVP控制与Ektron控制相结合。
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.
Ektron有几个API——有一个基于web服务的API，可以从非webforms项目中访问。我不确定是否有可能访问新的API(即非web服务API和更新的框架API)来创建一个非webforms项目。你可能想要做一个概念的快速证明来证实这一点。
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-
Ektron api的健壮性是一个位变量。一般来说，我发现处理简单的HTML内容是很好的。会员/登录也不错。在我的记忆中，我遇到过一些比较模糊的组件——电子商务、分类法、博客和日历——的问题。通常,问题包括-
- 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.
更新的框架API(在v8.0中初始版本，涵盖内容和文件夹，在2011年8月发布的v8.5中完全发布)是很容易使用的，尽管我仍然有一些空属性的问题。
Overall, as long as you're sticking to HTML content, you should be fine, provided you can access the API from a MVC project.
总的来说，只要您坚持使用HTML内容，只要您能够从MVC项目访问API，就应该没问题。
#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控件的站点，但是我使用了Webforms。MVP,而不是MVC。这让我可以将MVP控制与Ektron控制相结合。
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.
Ektron有几个API——有一个基于web服务的API，可以从非webforms项目中访问。我不确定是否有可能访问新的API(即非web服务API和更新的框架API)来创建一个非webforms项目。你可能想要做一个概念的快速证明来证实这一点。
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-
Ektron api的健壮性是一个位变量。一般来说，我发现处理简单的HTML内容是很好的。会员/登录也不错。在我的记忆中，我遇到过一些比较模糊的组件——电子商务、分类法、博客和日历——的问题。通常,问题包括-
- 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.
更新的框架API(在v8.0中初始版本，涵盖内容和文件夹，在2011年8月发布的v8.5中完全发布)是很容易使用的，尽管我仍然有一些空属性的问题。
Overall, as long as you're sticking to HTML content, you should be fine, provided you can access the API from a MVC project.
总的来说，只要您坚持使用HTML内容，只要您能够从MVC项目访问API，就应该没问题。