- Apigee Developer Services Portal Release Notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On Wednesday, February 12, 2014, we released version of the Apigee Developer Services portal for the cloud only.

If you have questions, go to Apigee Customer Support.

New features and enhancements

  • New default theme added to support Bootstrap 3
    By default, portals now use the new Apigee Responsive theme that is based on Bootstrap 3. All Bootstrap 3 features are available in this theme. Existing portals can be upgraded to this new theme but must first ensure that all blocks, templates, and other content is compatible with Bootstrap 3. For more, see Customizing the theme.
  • Support added for mobile screen resolutions
    The portal default theme now supports devices with widths from 768 pixels to 1400 pixels.
  • The Drupal admin menu can now be used on mobile devices
    The default Drupal admin menu is not compatible with the small screen sizes of mobile devices. If you want to administrate your portal on a mobile device, you can now enable the new admin menu that supports mobile devices with a screen width of 768 pixels or larger. See Customize the appearance for information on enabling the mobile-compatible admin menu.
  • New design for the My Apps page
    The My Apps page is where developer's manage apps. This page has a new design that simplifies the process of managing apps.
  • Modal support for forms in default theme as well as allowing custom themes to support modal submission of forms
    The portal now supports the use of modals to display common Drupal forms, including the user registration form and the user login form. Support for modals is provided by the Drupal Bootstrap Modal forms module. The Bootstrap Modal forms module requires Bootstrap 2.3.2 or later as part of the Drupal theme. For more, see Customizing the theme.
  • BugHerd support added to the portal
    BugHerd lets portal users submit comments and bug reports by making annotations directly on the pages of the portal. BugHerd then converts those annotations to bug reports. You manage bug reports by categorizing them, assigning them to developers, and tracking progress.

    BugHerd can easily be used by an entire development team to collect, track, and resolve issues. Each member of the team can submit BugHerd reports, view the report backlog, track report progress and status, comment on reports, and perform many other tasks. For more, see Integrating BugHerd.
  • Support added for the Drupal Advanced Forums module
    The portal forums now use the Drupal Advanced Forums module by default to add additional features including improved styling and quick search for active topics, unanswered topics, and new topics. For more, see Add blog and forum posts.
  • Completely updated blogging
    The default blogging tool is now a custom module with a new view for posts, new content types, and an "tumblr-style" editing toolbar. For existing customers these are available but turned off. For new portals, this is the default blogging workflow. For how to enable this feature on your existing portal and for usage of this feature, see Add blog and forum posts.

As always, you can discover the version any portal is running with the following command:

curl <portal url>/buildInfo