What to do if you see the "deprecated modules" warning

[#1]

After upgrading to recent releases of the Developer Portal, when logged in as an administrator you may start seeing the following warning message at the top of pages:

You have enabled one or more modules which are deprecated and will be removed from a future release of Apigee Dev Portal.

What does this mean?

Apigee Dev Portal is a custom distribution of Drupal, in which we bundle some platform-specific modules as well as a large number of contributed modules. In the past, we have shipped many more contrib modules than are needed for a barebones Dev Portal install, with the idea that many of our customers will make use of them on an optional basis. We have come to the conclusion that the installation of many of these optional modules should be handled by individual customers, and are therefore planning on removing them from our distribution.

What this means is that, whereas up until now these modules have lived in profiles/apigee/modules/contrib, from now on customers will be responsible for installing them in sites/all/modules.

Which modules are affected?

The following modules are deprecated as part of the Apigee Dev Portal profile:

• Bugherd
• CCK Phone
• Commerce WorldPay Business Gateway Integration
• Content API and its submodules
• Date and its submodules
• Display Suite and its submodules. (SmartDocs does not work properly when Display Suite is enabled anyway.)
• Entity Construction Kit and its submodules
• Features Extra
• ftools
• Google Auth and its submodules
• Github Connect
• Highcharts (the highcharts module is deprecated, but the highcharts JavaScript library is still an integral part of the Apigee Dev Portal distro)
• Internationalization (i18n) and its submodules
• Migrate and its submodules
• Node Export and its submodules
• Strongarm
• Util and its submodules
• UUID Features
• Variable and its submodules
• Views Accordion
• Views Slideshow and its submodule Views Slideshow Cycle

Does this mean I can't use these modules?

By no means! You can continue to use these modules by adding their code to your sites/all/modules directory. If Drupal detects any of these modules there, it will change their path in the system table so that it will no longer rely on their code under profiles/apigee/modules/contrib.

What will happen to my site when these modules are removed from the Apigee distribution?

If you have not enabled any of these modules: absolutely nothing.

If you are using one or more of these modules, and you have not migrated their code to sites/all/modules, the functionality provided by these modules may silently disappear. In a worst-case scenario, you may temporarily experience site breakage until Drupal's registry is rebuilt (generally accomplished via drush registry-rebuild).

What does this mean for me in the meantime?

The deprecated modules listed above will be marked with a (Deprecated) designation on the module listing admin page, unless you have placed code for that module undersites/all/modules. You will not be able to enable deprecated modules until you have placed code in this location.

In the short term, your site should continue to run as it always has.