Jérôme Vieilledent
Jérôme Vieilledent
Disqus API's default authentication system is what they call _Legacy admin authentication_. **eZDisqus** should support it out-of-the-box. **Disqus documentation:** http://disqus.com/api/docs/auth/
Be able to pass options specific to the exporter and/or formatter in CLI script (like [SQLIImport import options](https://github.com/lolautruche/SQLIImport/blob/master/bin/php/sqlidoimport.php#L29))
Provide a moderation interface inside eZ Publish's admin interface. Should be done through Disqus [Posts](http://disqus.com/api/docs/posts/) and [Threads](http://disqus.com/api/docs/posts/) APIs
At the moment, the DisqusComments datatype only checks and sets the open/closed status through the **data_int** field in the database. This should be done through [**Disqus API**](http://disqus.com/api/docs/) to be fully...
Disqus supports [OAuth2 (draft 20)](http://tools.ietf.org/html/draft-ietf-oauth-v2-20) as an authentication system for their API. **eZDisqus** should be able to authenticate this way. - Check if it is possible to develop against [**Authentication...
Provide a framework for Disqus API consuming, including authentication. Can be inspired of the [Disqus official PHP library](https://github.com/disqus/disqus-php). ### Official documentation - [Making requests](http://disqus.com/api/docs/requests/) - [Authentication in the API](http://disqus.com/api/docs/auth/)
With multiple frontend siteaccesses (1 Disqus shortname per siteaccess) and only 1 admin
This a Disqus Professional feature : http://docs.disqus.com/developers/sso/
With datatype implementation (see #2), threads would logically identified by **ContentObjectID**, but it should also be possible to identify by the **NodeID**. Multi-located content would have 2 options : 1....
As stated in #6, Disqus provide an import/export feature. Migrating back from Disqus to eZ Publish (eZ Comments, regular sub-content, or just for archive) should be made possible. Might be...