Hi,

I have installed Acquia Dev Desktop in order to have a local Drupal development environment. My computer is running Windows 7. The prototype site provided with the installation appears to run fine, but there are two problems in the dashboard.

(1)
Under "Reports > Status report", the section on "Drupal core update status" is in red and says, "See the available updates page for more information and to install your missing updates." The words, "available updates" in that are linked. When I click that, I get "All of your projects are up to date" plus a link for "Check manually". When I click that, it works for a while and then says, "Checked available update data for 5 projects. ... All of your projects are up to date."

So Drupal both reports being up-to-date and says that there are "missing updates."

(2)
Under "Reports > Available updates", there is a red box at the top of the page with four bullets:
• Notice: Undefined index: reason in theme_update_report() (line 86 of C:\...\local\DrupalDev\DrupalTest\modules\update\update.report.inc).
• Notice: Undefined index: in theme_update_report() (line 137 of C:\...\local\DrupalDev\DrupalTest\modules\update\update.report.inc).
• Warning: date_timezone_set() expects parameter 1 to be DateTime, boolean given in format_date() (line 2040 of C:\...\local\DrupalDev\DrupalTest\includes\common.inc).
• Warning: date_format() expects parameter 1 to be DateTimeInterface, boolean given in format_date() (line 2050 of C:\...\local\DrupalDev\DrupalTest\includes\common.inc).

Below that, under the heading, "Drupal core", there is a yellow text box. In the top right corner is a warning icon (dark yellow triangle with exclamation mark) and the box has the following text:
"Acquia Drupal 7.34.40 (Drupal 7.34 core)
Recommended version: ()
Includes: Acquia Connector, Bartik, Block, Color, Comment, Contextual links, Dashboard, Database logging, Drupal 7 driver for SQL Server and SQL Azure, Field, Field SQL storage, Field UI, File, Filter, Help, Image, List, Menu, Node, Number, Options, Overlay, Path, Pathauto, RDF, Search, Seven, Shortcut, System, Taxonomy, Text, Toolbar, Update manager, User"

===================
I found the recommendation to use Acquia Dev Desktop in three places:
www.drupal.org/node/1248034
www.drupal.org/node/263
www.drupal.org/node/1065212
which are the links in the first, second, and sixth bullets in "Local server setup" at www.drupal.org/node/157602 .

So it comes highly recommended. But the above behavior looks pretty flaky. Have I done something wrong with the installation?

Thanks for your help.

Comments

nlamot’s picture

Hi, I'm experiencing the same problem.
Did you find the solution for this?

NewSites’s picture

Since I didn't get any responses to my question and the behavior looked flaky, I uninstalled Dev Desktop and installed XAMPP instead. I'm pleased with it and have succeeded in setting up a 5-site multi-site installation in it.

nlamot’s picture

In my case, this problem was caused by updating the Drupal core with pm-update while using the Acquia Drupal installation profile.
This is not the right way to update your Drupal installation if you use this profile, as you can see here: https://docs.acquia.com/acquia-drupal/upgrade.

In order to solve this, I switched to the standard Drupal profile using the profile switcher module and I moved all modules (except for the acquia connector modules) in the Acquia Drupal profile to my contrib folder. It's very important you don't use the acquia connector modules from the profile. You need to download fresh copies from Acquia and use these. Otherwise you get the errors you got because of the Acquia Agent module (it hooks in the update process when the modules originate from the profile).

When you've done this, you can just rebuild your registry using drush (drush rr) and your problem should be solved.

NewSites’s picture

In my case, the problem was not caused by updating anything, but the problem occurred on a fresh install of Dev Desktop. I note that four other users reported similar problems on the Acquia forum between Dec. 2014 and May 2015 and Acquia has never posted any resolution or explanation.

diamondsea’s picture

I ran into this with an Acquia Cloud hosted account. Acquia told me that there was a setting that needed to be changed in Insight's behind-the-scenes settings (put in a ticket for Acquia to change it).

The thing I turned off was in our central customer information for the subscription. If it comes up again refer in the ticket to the Acquia-internal document called 'Acquia Drupal "Available Updates" dated 1969' if you want to point a Support Engineer towards it. - Acquia Support