The Telligent Evolution platform is the foundation for the Telligent Community 7 and Telligent Enterprise 4 products.
Are you looking for user documentation? Please visit our end-user documentation for Telligent Community 7 or Telligent Enterprise 4. If you are looking for 7.5 developer documentation, please see this wiki.
Plugins were introduced in Telligent Evolution 6.0 and continue to serve as the basis for extending the platform in 7.0. They allow for functionality to be enabled and configured without modifying configuration files or continuously removing components from your site.
Plugins are used for exposing UI data, search, parts of authentication, and the new core service model. Plugins replace CSModules for handling system events.
Telligent Evolution recognizes content as a minimal set of information needed for it to function within core services.
All core services rely on the content core service, which persists the basic information needed to identify and interact with content. This information is obtained using the IContentType plugin and related interfaces.
Many core services can be categorized within themselves. For example, you can specify a comment type in the comment core service, allowing you to have different comment streams for a single piece of content.
All additional core services extend IContentType to gather additional information specific to that service. For example, ICommentableContentType is a plugin that extends IContentType, adding methods that allow permission checks.
New Core services were added to 7.0:
Certain core services can be consumed by external systems using REST and OAuth services for Evolution. External systems are still loaded into the content core service; however, a unique url is used to identify the content. This enables features like commenting, likes, and ratings to be applied to custom content outside of Evolution. In this scenario, external content belongs to an application defined in the new OAuth services for Evolution and permissions are granted to the application.
The third-party application is responsible for determining permissions at the user level.
Telligent Evolution becomes an OAuth provider based on the OAuth 2.0 specification. OAuth is designed to ultimately replace REST authentication by API key. It uses the concept of obtaining a token that expires to access Evolution resources either by request or direct grant. The provider utilizes three types of authentication:
Event-based plugins replace CSModules in 7.0. (CSModules continue to work in 7.0, however they continue to expose internal code and entities that are not upgrade-safe.) Event-based plugins use the same Pre(Before) and Post(After) pattern for events as CSModules. They are handled in any plugin and wired up during the plugin initialization(Initialize() method).
In the new event plugins, signatures for events are different and upgrade-safe. Each event has its own event argument that only exposes properties which can actually be manipulated.
More about Plugins.
In 7.0, search is no longer divided into different search and index providers. A single plugin defines the search provider and provides the interface to both execute a search and index documents. Search indexing is handled by a derived IContentType Plugin called ISearchableContentType that provides methods to provide content(internal and custom) to the search index.
A plugin is also provided to allow translatable categories for custom content.
Given a search content type of “custom”, you can define “custom” to display a resource that appears in the search results widget.
More about Search.
Powered by Zimbra