You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Tuesday, February 5, a new version of Developer Services Portal is ready for you to
apply. See [How
do I apply Apigee updates to my developer portal in the public cloud?](https://docs.apigee.com/api-platform/publish/drupal/developer-portal-faq#how-do-i-apply-apigee-updates-to-my-developer-portal-in-the-public-cloud)

> [!NOTE]
> **Note:** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support) if you have questions or issues.
>
> Sign up for release notifications:
>
> - **Cloud** : Go to [http://status.apigee.com](https://status.apigee.com) and click **Subscribe to
>   Updates**.
> - **Private Cloud** : Fill out the form at <https://pages.apigee.com/release-notifications-submit.html>.

## Bugs fixed

The following bugs are fixed in this release.

| Issue ID | Component Name | Description |
|---|---|---|
| 123525730 | Developer Portal - Drupal | **Rules Fatal Error following PHP update to 7.2** Some customers are experiencing a Fatal Error on their site after updating through the Pantheon upstream (which upgraded PHP from 7.1 to 7.2). `Fatal error: Declaration of RulesRuleUI::form(&$form, &$form_state, $options = Array) must be compatible with RulesActionContainerUI::form(&$form, &$form_state, $options = Array, $iterator = NULL) in /srv/bindings/86f3e0d8eb44481c874852dacec4fa17/code/profiles/apigee/modules/contrib/rules/ui/ui.plugins.inc on line 0` The error occurs because Apigee's Rules install version is 2.10 and has some features that are not compatible with PHP 7.2. Updating the Rules version to 2.11 is a confirmed fix for the issue. |
| 120799908 | Developer Portal - Drupal | **Company App Analytics not displaying** Fixed issue where App analytics for companies were not being displayed. |
| 119270106 | Developer Portal - Drupal | **Remove `noreply@apigee.com` from Dev Portal Profile** Changed the default admin email from `noreply@apigee.com` to `noreply@example.com`. |