Earlier this week I had a conversation with one of our customers that wanted to add a cookie consent message to their community site.
After researching this further I decided to put together a simple Telligent Community 9.0 widget that shows how to do this. The code is on GitHub and still requires some more improvements, but it does work:
Get the EU Cookie Consent Widget on Telligent's GitHub
We are announcing the release of another open source project to GitHub, the SAML Authentication plugin:
https://github.com/Telligent/SAML
SAML (Security Assertion Markup Language) is an open-standard for enabling single-sign-on between your community and other applications or websites. You can learn more about SAML here.
Important points:
One of the common requests we get from customers is to be able to configure metadata on their site pages, this helps with SEO and also improves the experience when a page is shared on Facebook, Twitter or any other platform that reads extended meta tags. With the advent of Telligent version 9 there are some improvements to the blogs and media gallery to allow the author to specify some meta data but there is not a holistic…
We're very excited about the release of Telligent Community 9. To help you make the most of your community, we've prepared a complete set of developer training guides and tutorials:
community.telligent.com/.../developer90
This training provides specific guides and guidelines to supplement the API documentation no matter how you want to build and customize on the Telligent Community platform: via external inte…
Out of the box Telligent Community comes with a selection of oAuth client providers. Your users can use LinkedIn, Facebook, Salesforce, Twitter, Google and Microsoft Live. There are lot's of other social networks out there and sometimes you need to create a provider for one of these. In this post I will detail how to create a oAuth provider for Strava, which is a popular cycling and running network. Those that know…
When we launched the new telligent.com site we started with WordPress. It was an easy way to get a site up and running. While we eventually plan to move to Sitecore, we did want to integrate some community functionality with WordPress right awary. Specifically our trial experience that would allow people to setup trial groups in our community.
Side-note - this also gave us an excuse to work through the APIs on a non-.NET…