Critical Update - cAPI 1.3.4.5 Coming Soon!

A bug fix is due with cAPI v1.3.4.5 which resolves access control limitation in the Services Control Panel. Specifically, it fixes an issue where non-core.admin users are not able to administer their own tokens due to an error in the ServicesTabletoken class which results in "index not found" for the following ACL capabilities:

core.edit
core.delete
core.edit.state

As part of this fix, the com_services component is being updated for improved compatibility with Joomla 3.8+ and the upcoming Joomla 4.0 (in-testing).

cAPI v1.3.4.5 should be available on or near Tuesday, January 30th, 2018.

My apologies for the delay on this release. The scope of bug-fixes and compatibility updates great exponentially. With that said, the next release is almost complete, but the new version will increment to 1.3.5 (instead of 1.3.4.5). This is due to the new model and table classes being created for this release. Not REST endpoint schemas will change however.

Quick update on progress for cAPI v1.3.5 release:

Additional testing is now being done to resolve a few issues related to front-end token management (new feature!) and token delete from the administrative backend.

In addition, a significant amount of work has been done over the past few weeks to create a Professional support tier for cAPI and build SSO between Joomla, or centralized directory server and JIRA Service Desk. This will facilitate an improved support experience for customers requiring advanced technical support and consultation with respect to cAPI extension development.