I'm experiencing "Error accessing CC API: Not Found" error both on CC enabled node or user CC settings since 24 hours.
First occurrence: 01/10/2011 - 19:40 UTC

This brings up the needs again to improve the API access and not to connect with the CC server during a user session but instead during cron time.

This issue is connected with #873738: Error accessing CC API: Connection timed out

Comments

toemaz’s picture

toemaz commented

I forgot to add that the results is that no node can be submitted, nor user settings can be changed. Quite a problem.

JED3’s picture

JED3 commented

The CC REST API was updated earlier this week to address concerns with the service's performance (mentioned in a separate issue for the this plugin). This plugin has been using a URL which should have never been a valid API method, but was supported as a result of a bug in previous versions of the CC REST API. When we updated the service, that URL was no longer valid, and as a result, 404s started going out. We've updated the API to be backwards compatible with this URL and we apologize for the oversight.

John Doig
Creative Commons Engineer

toemaz’s picture

toemaz commented
Status: Active » Closed (fixed)

Hi John,

Thanks for the explanation! Very kind of you to inform us about this API function change.
However it's time for us to act and rewrite how this module interfaces with the CC API.

I'll move back to #873738: Error accessing CC API: Connection timed out