Odd but I am unable to click on the Admin button in the toolbar. The cursor on my windoze machine changes from an arrow to a finger when I hover over the admin button so it does recognize it as a button but nothing happens (no action) when I click.

I can type /admin and go to the admin part of the site without any issues.

  • I have tried with Firefox and IE.
  • I tried Firefox with Debugger turned on but I have no idea what to make of what it shows when I get the button highlighted.
  • I have cleared cache on browser and on the site.
  • I have also changed from Open Atrium Radix 7.x-3.5 theme to Radix 7.x-3.0-rc1 theme and back to Open Atrium Radix 7.x-3.5 theme to see if it would clear but no such luck.
  • I looked at the dblog and nothing is there to help troubleshoot this issue.

Any suggestions on how I can troubleshoot this.

Comments

jbrundle’s picture

I suddenly have the same problem. Updated the site version 7.x-2.26 with all the new updates. Just before that, I had installed a features override module, but that's another story. Reverted to an early version of OA2 from backup file. Then found that I had to install modernizr library. Did that. Log reports are clean now. Cleared caches and updated php and still admin button not clickable. Browser definitely recognizes it as a button, but no action defined. I can also get to admin pages via /admin

mpotter’s picture

Sounds more like a Javascript error the is preventing the drop-down action of the menu. Check your browser javascript console.

jbrundle’s picture

Thanks. I fixed the problem. I think the issue is the following. When you go to the "Available Updates" page, you see a myriad of optional available updates for the various drupal modules that are used by OA. Yesterday I checked all the boxes and updated them all willy-nilly, which is how the problem started. In other words, probably what happened is some of those drupal module updates post-date OA2 7.x-2.26 and may be in conflict with OA2.

Then the problem started to compound: the system asked for the modernizr module etc., which I installed. I had also been learning how to use the Features Override module, and made and installed an override module which more or less worked, but showed several conflicts. That's about when the menus stopped working properly. Actually, I think part of the problem is that my Features Override module "locked in" some of the problems with the menus.

Thought about it overnight, and fixed the problem this morning.

1. Downloaded and installed a clean version of OA2 7.x-2.26 :

a. Download tar file openatrium-7.x-2.26-core.tar.gz
b. Place it inside the root folder openatrium.com (or whatever you call it).
c. In a terminal window, cd to that root folder, and type:

sudo tar --strip-components=1 -zxvf openatrium-7.x-2.26-core.tar.gz

This operation unpacks the tar file and replaces all the files with the same names without destroying the tree structure of the files, or replacing any other files you added.
d. Then in the terminal window type:

sudo chown -R www-data:www-data .

e. Then run update.php
f. Clear cache at admin/config/performance

2. Then I removed my Features Override module: Disabled it and un-installed it, then deleted it. Ran update.php and cleared caches.

3. Then went to my browser(s) and cleared their caches.

Now all of my features and menus are operating normally again. Probably what I will now do is to create a new Features Override module which presumably will be a "clean" module without the problems that were locked into the old Features Override module.

So the takeaway here is don't do the optional drupal module updates (unless they are critical security updates), just wait for the next update of OA2 which presumably has the appropriate drupal updates included.

mpotter’s picture

Status: Active » Fixed

That certainly explains the problem. Normally when you go to the Updates page in Open Atrium you should see a big bold text that says:

Do not manually update modules within distributions!
Drupal Distributions contain a carefully selected set of module versions along with specific patches. You should never update individual modules within a distribution unless you are an experienced developer.

If you REALLY know what you are doing, you can find the links to the normal Drupal update pages in the collapsed section below.

And we specifically hide the normal Drupal update page. So you must have done something to bypass this to get to the update page.

Anyway, glad you got it all working.

jbrundle’s picture

Mike, That page is actually not hidden all that much:

http://169.237.222.225:8888/openatrium2.com/admin/modules/update

I had clicked the top box, which clicked all of them, and then just unthinkingly hit "Download These Updates" at which point the "fun" started...

Won't do that again...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.