I struggled with this one for a while and it really depends somewhat on your server set up but here’s how I managed to increase my file upload limits on a Heart Internet hosting account:

1. ) This is worth doing if you need to make minor changes to the Atrium admin: Allow variable overrides in the Strong Arm Module here: admin/settings/strongarm

2. ) In the root of your website (so inside public_html or something like that) add a PHP5.ini file with the following inside it:

memory_limit=124M
upload_max_filesize=200M
post_max_size=400M

…obviously replace the limits with your required details

The ‘5′ bit in PHP5.ini is the bit that caught me out, it’s normally just PHP.ini but my host requires the 5 if the site is using PHP 5, strange because the actual files (eg settings.php) don’t need to change. But it works.

We’ve been using Open Atrium recently and one of the trending issues with both Drupal and OA is that there isn’t a built in rich text editor. It turns out it’s not that difficult to add in, I thought I’d post the steps below for any wandering Interterer:

1. ) Download the Wysiwyg module for Drupal: http://drupal.org/project/wysiwyg

2. ) Download your editor of choice, I went with TinyMCE (but secretly I’m waiting for CKeditor to be compatible, don’t tell TinyMCE): http://tinymce.moxiecode.com/

3. ) Unzip the Wysiwyg module and upload it to your server in the modules folder: /sites/all/modules/contrib/

4. ) Unzip the editor and upload that to a new folder here: /sites/all/libraries/

5. ) Go to your Open Atrium site admin: admin/modules and enable the Wysiwyg module

6. ) Go to: admin/settings and click on the Wysiwyg configuration link

7. ) Select your editor from the drop downs

That should be it, if you visit your OA site the content editor sections should all now be using the editor.

Recently we’ve installed Open Atrium for a client, and have had brilliant success with it. It’s super pretty (which is important to me) and it really fits a certain kind of intranet/wiki set up that some clients need.

I mentioned on Twitter that I had a couple of bugs getting it running online and I though it would be a better to explain things here for anyone who might have similar issues, don’t worry it’s pretty straight forward and there were only two (…well two and a half).

1.) PHP Memory limit: In the requirements Atrium needs 64M, and by default you get 8M – Easy fix is to add a file called php.ini in the root of your Atrium folder with one line in it:

memory_limit = 64M

2.) When I clicked on Edit in a book page (and a couple of other screens) a warning popped up about not being able to find og.nid in the og table. This turned out to be because during the install I’d chosen to use a table prefix (wiki_) and although Atrium could find the table, it couldn’t find the column inside the table which hadn’t adopted the prefix. So I simply hard coded the table prefix in a couple of places in the function:

og.nid -> wiki_og.nid around line 1025 of spaces_og.module (sites/all/modules/contrib/spaces/spaces_og)

The half.) I can’t see the modules page in the admin section …not sure why yet?!

Thanks @ultimateboy for asking!

UPDATE: Looks like the og.nid bug is sorted in Beta2 – Follow @open_atrium for the latest updates

UPDATE: It turns out that the reason I coldn’t see the modules page is that it uses waaaayy too much memory on the server, for me this was fixed by installing Beta3 …but it’s still an issue for a lot of people with lots of modules installed.