drupal

The first steps in OG land

All the recommendations for Organic Groups (OG) made me curious. Can I use them for my purposes and safely hand over part of the responsabilities of managing restricted content?

Pros and cons of the current configuration

The current configuration includes many modules, a.o. I18n, Content Access, Views and CCK. With these I'm able to define roles, grant restricted access to nodes based on roles and keep the site bi-lingual (Dutch and English, with the largest part of the content in Dutch). This works fairly well.

Drupal site requirements

Although I subscribe to the ideas in the book (see my previous post) that you need to write user stories and follow an architectural approach, my main goal here is to see whether Organic Groups provide features I need in the next version of my website.

Drupal website overhaul

Summer holidays is an excellent time to do some major work on my pet project. Sitting in the shade with cool drinks at hand I started to read a book on Drupal I came across some time ago. This book, Leveraging Drupal: Getting your site done right, turned out to be amazing.

Access denied, yet again

In an attempt to update Drupal to it's latest version (6.5) I decided to test it on my local setup. Lo and behold, I got an 'Access denied'. After testing out several possible causes, I googled around.

The answer: a few days ago I setup an SMB share on my home folder, with access for only my user account, no access for 'everyone'. That resulted in a permissions change on my home folder, even after removing the SMB share.

The solution: sudo chmod o+rx [home folder]

Drupal shows blank pages, sometimes

Something I never experienced on my local setup suddenly happened on the production site: random white pages. Consistent in that it was always the same pages (e.g. admin/build/modules), but random because most content pages would show up fine and many admin pages as well.

Digging aroung showed an error in the Apache log:
Fatal error: Allowed memory size of X bytes exhausted

Gallery2 woes

Finally I thought it was time to move my Gallery2 configuration + albums to the production site. This time making sure that I took the necessary precautions.

Yes, it was uploaded without errors and yes, I could switch off maintenance mode and yes, I could see my pictures and enter the site admin mode etc.

Drupal module subtleties

Drupal is growing on me: I like it more and more and I'm capable of doing much more with Drupal after a few months than I could with Joomla after the same amount of studying.

However, today I spend more than an hour figuring out why I couldn't get the CAPTCHA module to produce an image on a Webform form.

Finally, after googling around I found the answer: I can't set it in the edit mode of the form, only in the VIEW mode. So much for subtleness.

MySQL vs PHP login weirdness

During the reinstallation of Gallery2 I also wanted to set the database username to the same name as the production site to have as few differences as possible. I ran into a problem I had before when installing Drupal: the only connection allowed was using user 'root'. Whenever I used a user with a password who had only privileges on a single database I got an 'access denied' error. However, on the production site the installation with a username and password went well and using the username and password and logging in in a terminal using the mysql commandline also worked well.

Moving Drupal and Gallery2

When I started out I put the Drupal files in the local webroot I created. Gallery2 was installed in it's own folder underneath. After fiddling with settings and adding and editing content I felt I was ready to put the site on the production space. With the old site up there, I wanted Drupal in its own folder, rather than the root. After a hefty ftp session I found out I approached it wrong. :-(

Pages

Subscribe to RSS - drupal