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. :-(

TinyMCE Module patching for IMCE integration

In the second attempt to use the TinyMCE Module it worked better. This time I wanted to integrate the IMCE module. Having seen how it worked on TinytinyMCE I thought it would be a piece of cake. Nope, this one also needs a patch. Luckily I found it here.

So much for documentation

Documentation is always a good thing, yet I keep forgetting to write down what I did, 'because it's so obvious'. Well, it wasn't. I was hunting down an error for several hours that occurred on one domain, but not on the other with the same Drupal installation.

So for every one out there, especially my future self: switch off PHP safe mode. Drupal doesn't like it. More specifically: it produces an error in Module File System when creating the tmp file.

Drupal Clean URLs on OS X Leopard

As said before, I did a Drupal installation according to the IBM tutorial and created my own 'drupal.development' virtual host. During the installation of Drupal I noticed I couldn't get Clean URLs. Now that I'm working on integrating Gallery2, I really needed them. So I had to look into the problem.

First I had to check if mod_rewrite was installed using 'apachectl -M'. This resulted in an error:

Safari vhost quirks and 'access denied on /'

As I started on Drupal I came across an IBM tutorial that explained how to setup a Drupal developement environment with Eclipse. What they did was setup a virtual host in Apache by the name of 'drupal.development'. That worked fine in Firefox and I was happily configuring Drupal when I decided to use Safari to test the 'anonymous user'.

Drupal best practice

Just found out: put downloaded modules not in the default /modules directory, but rather in sites/all/modules or sites/default/modules. I simply moved them around and nothing bad happens.

Drupal's menu system - take two

Ok, so I was wrong. The primary links can be used for a hierarchical menu and I can even set the secondary links to the same menu and they'll automatically show the second level items, or so I'm told. Haven't tested it yet.


Subscribe to SourceFusion RSS