You can clone with
HTTPS or Subversion.
Now using two API keys -- one for dealing with content channels, and …
…one for dealing with the airtow/library calls
Changed content type references to meet new spec
Content type is "Post" (capitalized), with fields
"link","title","description" and "content" (all lower case).
Removing vim swap file.
Moved API up to beta3 standard.
Using ping method to check API status instead
Pushed testing of axilent API on admin pages
Slightly backing off portlet height. Down to 500px.
Use production domain and protocol
Fall back to POST on PUT failure
Refactored API base and friends
Merge branch 'master' of github.com:Axilent/Axilent-Wordpress-Plugin
Fixed iframe height. Now gigantic
Changing protocol to https.
Changed references to main cluster
Previously wpdev.axilent.net was the endpoint, changing to main cluster
Fixed summary / description
Added configurable content fields for both imports and widgets
Only do sync if setting is on
Removed subdomain setting
Added light debugging to Axilent::Net class
Doubling height of Axilent widget
Added support for limit, and also got related post listing working
Only posts with published status get sent to axilent
mostly done, related content items still in flux
rounded out admin functions, last peice is getting content
Added related ocntent query
Fixed iframe, and some POST/PUT tweaks
Removing NEt lib and integrating mor etightly with Axilent core
Create/update is finally in working order (with portlets)
More naming changes
Some naming changes from reused code
Built out more of the core Axilent API class
Added admin UI, pulling in some data (incomplete)
Core libs for Axilent