Recent update broke site CSS

Not sure what you updated, so I'd need more details on that.

There *is* a bug in the 2.0 release that causes the default home-page widget to mess up the css on a page when you Customize a page and click browse the Open Atrium section of the widgets. This is fixed in 2.01 which should be out soon (barring any more problems on drupal.org)

Also, when posting bug reports, please try to post as much detail and a step-by-step method for reproducing the problem. Otherwise it's hard to help when you just say "messed up" and "broken" without specifics like screenshots.

What browser are you using? Not seeing any problems like that here. Also be sure to flush your browser cache.

Not sure the step by step but I updated the drupal modules in the module update section and it seems to have happened since then.

You should NEVER do that with a distribution. Distributions use very specific versions of modules with very specific patches. Updating a module from the update page will break your site. You'll need to rebuild your profile directory using the build.sh drush make script, or replace with that latest version of the distribution on drupal.org (which is unfortunately broken).

Added a new oa_update module to oa_core. Will be in the 2.02 release (hopefully tomorrow).

This submodule replaces the default module update pages on the site with a warning page about updating individual modules within distributions. That should help prevent some of these issues caused by people updating modules themselves.

This submodule will eventually be improved to actually show new versions of the distribution and allow you to upgrade easily, but I decided not to wait on all of that fancy work and to just get the warning in place for now.

Can some one please explain how does the oa_update module works? I have the same problem with site breaking after update. is there a documentation about updating the proper way?
Thanks

@mpotter: FYI, I created an issue in the Panopoly issue queue about implementing a module similar to oa_update upstream (since this probably affects all Panopoly based distros): #2128959: Replace default "update" module behavior with something that makes sense for distributions

The easiest way to fix your broken distribution is to download the latest tar.gz file from the Drupal.org project page and then replace the profiles/openatrium directory on your site with the profiles/openatrium folder that you downloaded.

(although see the issue that v2.03 is still slightly broken, so might want to wait till tomorrow)

(You should only use build.sh if you know how to use drush, so if you can't find build.sh then you probably don't fall into that category)

The oa_update module prevents the update notices for modules within the distribution. It will only tell you to update when the main openatrium distribution has a new version, or if there is a security patch to some module (or drupal core). It will show the current openatrium version and provides a download link for it, just like with a module.

Sometime in the future we'll try to improve this further to make a one-button "update distribution" function. But for now the new oa_update should at least help prevent people from corrupting their site.

oa_update also fixes the issue with patched -dev modules being reports as unsupported. It also removes the oa_* Features modules from the module update list (since they don't exist on drupal.org separately).

Try:

drush cc all
drush updb
drush cc all
drush fra -y

The last step will update all your features in case something is wrong from your previous install attempts. I haven't ever gotten that error myself though, so just guessing.

Are you uploading a file to a comment in WorkTracker, or in the Discussion plugin? If it's in WorkTracker, please post this over in the oa_worktracker issue queue so the module maintainer will see it.

(still sounds like a module or table didn't get installed properly somehow)

Another theory: since you attempted to upgrade all modules earlier, that table could have been removed by an update? And now that you're back on older code, it's looking for it. Anyway, just a theory - I don't know the Media module internals.

Your Open Atrium install is broken. The "media_filter_usage" table is created by the version of the Media module included in OA - yours either failed to install or was removed in an aborted upgrade to a newer version of the Media module.

To reinstall the Media modules tables, you can try:

1. Enabling the Devel module
2. Going to "/devel/reinstall"
3. Selecting "media" from the list and clicking "reinstall"

However, I can't gauranty that this will work! The only sure way to get an unbroken Atrium is to install fresh.