You're viewing Apigee Edge documentation.
View Apigee X documentation.
On Wednesday, October 21, 2015, we released a new cloud version of Developer Services Portal.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
The following bugs are fixed in this release.
|DEVSOL-1910||Support markdown parsing for all SmartDocs description fields
|DEVSOL-1907||SmartDocs: Use local assets instead of CDN by default
SmartDocs now uses local assets instead of CDN for all new installs.
|DEVSOL-1897||SmartDocs body attributes showing in Request Body and Body
Fixed issue where SmartDocs body attributes were being displayed in the Request Body and Body Parameters.
|DEVSOL-1895||In settings.php, check for existence of settings.local.php and include it if
Customers who need to add custom code to sites/default/settings.php can now avoid git conflicts by moving all their custom code to sites/default/settings.local.php instead, which is now included (if present) by sites/default/settings.php.
|DEVSOL-1894||Content-Type is not added to SmartDocs generated cURL command
The SmartDocs method template now properly adds Content-Type to the generated cURL display.
|DEVSOL-1893||SmartDocs Method Page: Only display Category label if values exist
Latest SmartDocs template does not show "Category" in Resource Summary section on method if there isn't a category.
|DEVSOL-1887||Developer Sync Fatal error: Unsupported operand types
Fixed issue where Developer Sync would throw "Fatal error: Unsupported operand types" in some situations.
|DEVSOL-1879||FormData fields not displayed/sent in SmartDocs method
The latest SmartDocs template and JS files fix an issue where body parameters were not being sent with the sendRequest to the API.
|DEVSOL-1878||SmartDocs Content-Type is not a dropdown on Dev Portal
The Content-Type header parameter is now displayed as a dropdown instead of a text field.
|DEVSOL-1861||Allow SmartDocs to interact with modules implementing
SmartDocs no longer has a conflict with the i18n_taxonomy module. Internationalized sites can now translate non-SmartDocs taxonomy pages.