Open Atrium miniblog

[WARNING: This blog is a bit geeky]

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.


Leave a Reply