Submitted by Hans Salvisberg on Wed, 2012-03-21 00:41
Submitted by Hans Salvisberg on Mon, 2012-02-13 01:39
Internet Explorer's High Privacy setting "blocks all cookies from websites that do not have a compact privacy policy." This includes out-of-the-box installations of Drupal 7.
Here's a work-around:
Add
header('P3P: CP="We do not have a P3P policy"');
to your settings.php file. Tested with IE9.
Submitted by Hans Salvisberg on Wed, 2011-09-07 12:34
Submitted by Hans Salvisberg on Sun, 2011-08-14 19:30
Everyone has got their list of favorite extensions — here's mine...
Submitted by Hans Salvisberg on Thu, 2011-03-17 12:20
This is work in progress...
I like working in Eclipse, and I've gotten used to having one project for each major Drupal version. This allows me to put the corresponding contribs inside the respective sites/all/modules directory and to just .gitignore them. That way I can let my local webserver serve each Drupal version without having to switch branches.
Set Up a Cache
Submitted by Hans Salvisberg on Tue, 2011-03-15 23:02
Setting up msysGit on my Win7 box has been a bit of a pain.
Here's a step by step guide:
1. I don't quite understand what the Portable version is all about, but I went with the other one.
2. If you're not running as Administrator, then the Installer fails. So, run it as Admin. I had also installed TortoiseGit, and the Installer made me choose from
( ) Use OpenSSH
( ) Use (Tortoise)Plink
The former ultimately lead to success.
Submitted by Hans Salvisberg on Sat, 2011-02-19 18:52
Submitted by Hans Salvisberg on Thu, 2011-01-06 09:29
daemon.log:
mod_delay/0.6: unable to open DelayTable '/var/run/proftpd/proftpd.delay': No such file or directory
Fix: create the directory.
Possibly related: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506 ("runlevel unknown", #81, #94)
auth.log:
pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory
Fix: create the file.
Submitted by Hans Salvisberg on Mon, 2011-01-03 16:18
I like putting my servers under subversion control, i.e. treating the entire file system as a "local working copy." That way I can safely try things and be sure that I can go back to a previous configuration. Also, whenever I do some configuration changes (either manually or through a control panel), I can review all the changes, and when I'm satisfied I add a dated entry to a history file and commit / (root).
Workflow
Here's a typical workflow:
- Make some changes.
- Verify the intended behavior.
Submitted by Hans Salvisberg on Mon, 2010-10-04 21:10
Pages