Here are the two basic strategies I thought of, but got nowhere with:

- In CCK Display settings for the node, if only there were a “Mobile” option along with “Basic”, “RSS”, “Search” and “Token”… Or can I use Token somehow? I don’t know how to make use of this option
- In Panels, I could create different variants of the node view for mobile vs primary theme, but how do I set “current theme” as the context (or otherwise know that the page is being viewed on a mobile device)?

I’d appreciate any thoughts on how I could accomplish this!

Because all your output is eventually controlled by your theme, you
could handle this with an override of theme_imagecache() in your
mobile theme.  Here’s how I’d do it:

1) create mobile versions of each imagecache preset you’d like
replaced (example: thumb and mobile_thumb, full and mobile_full)
2) create a mobiletheme_imacecache function, which works exactly the
same as theme_imagecache, but before just using the preset specified,
it first checks to see if there is a preset with the prefix “mobile_”
and if there is, it uses that instead.

There may be a more elegant solution, but I think this will do the
trick for you.

Then when you think you are ready, take another dump from your live
site, drop your upgraded database (keep a backup) and import the D5
database again and visit update.php to bring the database up to date
again.

The only place you will lose any data is with settings and module
configurations, and those you should document so you can revisit each
settings page quickly after the next database upgrade.

I just went through this exact process for a site with 80 contrib
modules and it worked great.  I only upgraded my db three times. Once when I started, once to test the real thing and to make sure I had all the necessary
documentation, and once when I did the real upgrade.

I’m working in panels and have a node template.  I want to add a visibility rule for a pane so that it is only visible when a CCK field is a particular value.  The field is a single on/off checkbox, with key values “Yes” and “No”.  I’m using PHP for the visibility rule, and tried this:
return ($node->field_listing_green[0]['value'] == ‘yes’);

It produces an error on the page:
“Parse error: syntax error, unexpected ‘[' in .../ctools/plugins/access/php.inc(55) : eval()'d
code on line 1"

For starters the $node you are using in your visibility code doesn't
exist here, so if you want to run a test on part of it, you need to
load the node frist.  (The node is already cached on this page so it's
not a big dea to call node_load() again).  Do something like...

if (arg(0) == 'node' && is_numeric(arg(1)) && !arg(2)){
$node = node_load(arg(1));
return ($node->field_listing_green[0]['value'] == ‘yes’);
}

I’m not sure why you got the PHP error, but what you are trying to do
is dependent on how you set up the cck field.  I tried to guess how
yours was set up from your email, and added one to one of my content
types.  I chose a “single on/off checkbox” where the “allowed values”
were defined as follows:
no|
yes|Yes

Then I created a node-view panel layout for this content type, and
added a pane with visibility settings as above, and it worked as
expected.  I’m not sure what you were doing wrong, but perhaps this
recipe will help you?

I've set up a Drupal site for someone else.  I gave him 'sub' admin
privileges, so he can log in and approve user account requests.  But
it is I who am flooded with the emails.

I tested this out - on a separate site, I created two admins - me and
my evil twin.  I get the user account requests by mail (the standard
"someone has applied for an account" mail) -- my evil twin does not.

It's not clear to me where function_user_mail pulls the value of the
recipient from.

The email address Drupal is sending the emails to is the one defined on the settings page page at Admin > Site configuration > Site information.  If you are willing to hand of this power to your friend on his site, he will get the user account emails.  If not, please try Chris Bryant’s solution:

The Actions and Triggers systems of Drupal core should be able to handle this for you. It’s not immediately obvious what can be done by combining those two modules, but they are quite powerful and you can do amazing things.

This should get you going….

1. Enable the Triggers module

2. Go to Admin –> Site Configuration –> Actions (http://example.com/admin/settings/actions) and scroll to the bottom to “Make a new advanced action available” and select “Send email…” from the drop down.

3. Fill out the appropriate fields for Description, Recipient, Subject and Message. For “Message” I would suggest going to Admin –> User Management –> User settings (http://example.com/admin/user/settings) and just copy and pasting one of the appropriate emails (since it will have all the Tokens that put in the site name and username, etc. in it.) The “Welcome, awaiting administrator approval” email is probably a good base to start with and you can modify it as needed. Then click “Save.”

4. Now you just need to create the Trigger to tie the Send Email action to fire when a user is created. Go to Admin –> Site Building –> Triggers –> Users and chose the action you created from the dropdown next to “Trigger: After a user account has been created” and click “Assign.”

5. You’re done. Enjoy the the evil you have now done to your evil twin.

As a bonus there is also a “Token Actions” sub-module as part of the Token project which will let you use more Tokens in your Actions.

I’m working on a large site that has two different visual styles. Pages from each style can submit to the search function. Depending on which “side” of the site users come from, I’d like to specify the page template to use for displaying the results. I was thinking of passing a value from a hidden field in the search submit form, but I’ve poked around and don’t readily see any way to pass that value on to the results.  Does anyone have any ideas?

A few ideas come to mind.

You could change the action of the search form to include a $_GET
variable…  something like  search?site=first or search?site=second.
Then in your theme’s preprocess_page function you can sniff out the
$_GET and alter the template file accordingly.

You could also add a hidden element to the search form itself. This
seems harder because I’m not sure which of those values survive the
form processing and get passed on to the results page. You could dig
around and see if you could find it, but it will probably require a
form_alter to get the value in there, then a form_submit to save it
someplace useful in addition to the preprocess_page to get it out
again.

Another option would be to save the version of the site in the
session.  This might be useful incase you ended up with more than one
place you needed to use this functionality.  You wouldn’t need to
tackle each problem individually, you could solve this once and re-use this value other places as needs arise.

I hope one of those solutions works for you

Answer given to Berkeley Drupal Users Group, 6/7/2010

I’m interested in making some edits to Panel’s Page Content menus, and my investigations so far haven’t provided a suitable solution for doing this.  The menus are provided by CTools and allows users to modify the content and behaviors of panels pages – things like Region: Style, Add content, etc.

You can add something to those menus in panels by designing and
building the thing you’d like to see there, and once your thing is in
the right format and hooked into panels correctly, it will just show
up!  But the existing panel’s menus aren’t really designed to be
altered.

Panels – like views – is a developer tool, and not intended to be
turned over to end users. In that respect, there’s no need to change
any of the language on any of the menus (ha ha!).  That said, panels
was designed to have a plugable UI.  So, if you don’t like the
developer UI, you can write your own client-facing UI.

Fortunately, someone’s already beaten you to it.  Check out this
patch:  http://drupal.org/node/785576

I know, that doesn’t really answer your question.

Answer given to Berkeley Drupal Users Group, 5/13/2010