Sourcefusion

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.
Read more »

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.

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.

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.

Read more »

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’. Whatever I tried, I got an ‘access denied on /’ error, not even the Drupal page I specially set up for it, no, just a plain white page with a single line.

Read more »

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.

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.

Right now I understand the usefulness of creating a separate menu for the actual content. That way the default Navigation menu can be left for site management tasks and hidden from anonymous visitors all together. What I still haven’t found is an easier way to create this menu. Compare this workflow in Daisy to the one I’m currently doing in Drupal.

Read more »

The essence of a good website is the ease with which visitors can find their way through the website. So navigation is important. I guess I’m spoiled with my own system where I only had to set the navigation once and the software figured out the correct language, but Daisy’s navigation isn’t bad either. It allows you to build a simple hierarchical menu where child items can be grouped by a parent that is either a simple group or a link to a page. A page link is created using the page ID. If you don’t set any language information, it simply figures out which language to use, and falls back to the default language in case there is no translation available.

Read more »

The disappointment of the missing WYSIWYG editor was quickly solved when I found the TinyMCE module. Or so I thought.

Read more »

It took me a while to get Drupal installed. Not because the actual installation process was difficult, but because it required much more manual steps than Daisy or Joomla or WordPress.

Read more »