Drupal tips and tricks

So the scenario is this: you notice that you are no longer able to login on your Drupal site:

• the {users} table entry for your account looks just fine
• the login and access timestamps on your account are just a few seconds old, matching your latest attempt to login
• you reset your password in the DB, just in case, and it still does not work
• the telltale is that Drupal will not even tell you your login failed: it actually works, as the {users} table shows, but yet you are not logged in

Can you guess what can have been going wrong and fix it ?

I noticed today that one of my sites returned 403 Access denied on various pages with URLs like format/<foo>, although it was an alias for a taxonomy/term/<tid> taxonomy path which was actually available when not aliased. What could be going on ?

Received this Harris Interactive poll today, on behalf of Tarsus, the french company organizing the Solutions Linux expo.

One of the choices was a list of the top 30 Internet Technologies. And guess what ? For once, Drupal was on the list: first time I see it mentioned in this type of business context. Interesting.

Most of the time, when working on some piece of code, I'll resort to the configured debugger in my current Zend Studio configuration. And you probably do too :-)

However, I often have to access debug-type information on live sites where installing a debugger is out of the question, and I find myself often resorting to parameter dumps like the following:

<?php// lazy version for simple casesfunction foo_bar($x, $y, $z) {  dsm(func_get_args());  // [...]// less lazy version for more hairy casesfunction foo_baz($x, $y, $z) {  dsm(array('in foo_baz, x' => $x, 'y' => $y, 'z' => $z));  // ...?>

You've probably being using it too and, of course, after the first few dozen times, it becomes a bit used. So here's a tiny snippet that makes such dumps simpler to type and use :

Sometimes, you want to delete a whole bunch of users, terms, or nodes, say to cleanup a site while developing and still keep its configuration, so reinstalling is not really an option, and the normal content- or user-administration pages get in your way because they only show a limited number of entries, meaning you have to delete page after page of entries.

In case you've found Jeff Miccolis' post about the Extendr module for Flickr great, but have been bothered by the fact that the link on the blog was broken and that comments on that article were closed, the good news is that he made his code available on drupal.org too, at:

http://devseed.svn.cvsdude.com/sandbox/drupal-6/extendr/

In case you've been living under a rock, DrupalCon Paris is happening next week, and features, not one, but two Views Sessions, in addition to merlinofchaos' own CTools sessions on Panels 3 and CTools. One of them being, of course, by yours truly :-)

2011-08-06: UPDATE: now available from my drupal.org sandbox

After a massive user import to a customer's site, said customer noticed that, while he could see any user profile when logged, he could only see some of them when he was not logged in, receiving an "access denied" on the other accounts.

Now, with the administer users permission, a user can see any profile, so this didn't come into consideration, but since anonymous users could see some profiles and not others, the permissions granting anonymous access to the profiles were obviously set up correctly. So what could be wrong ?

The primary sources are of course the d.o. handbook pages about CCK, the CCK Group on g.d.o., and the source code itself.

There are also a lot of blog pages all over the web, which I'm trying to gather here. I'm opening comments on this page so if you find any good page elsewhere, please add a comment about it so it can be added to that list.