i18n

Did you add a taxonomy term to a vocabulary and it's just not showing up on existing content, contrary to all known laws of Drupal taxonomy?

Are you also using localization (l10n) / internationalization (i18n) such that your vocabularies and (even if you don't know it) terms can declare a language?

Check the language of that term. It will rudely default to the default language of the user you are using to add the term, even if the vocabulary overall declares itself to be neutral (blank) with respect to language.

The name of the Agaric Design Collective member who screwed this up will go unmentioned. (The person who in the first version of this note forgot to put the print statements before the l() with t() function was me, though.)

Before:

<div class="lbutton"><a href="/findaction"><span class="buttn2">Find an Action</span></a></div>

Step 1: Find a function that does some or most of what you want.
Step 2: Find another function that does the rest of what you want.
Step 3: Mash them together.

The situation this time: we have a Drupal 5 site (World Social Forum 2008) with i18n (internationalization module) and need translated content to show up in panels.

Update: Go straight to the patch.

Internationalization module (i18n) now supports views in a way-- unfortunately I think it hard wires in the

sure how well that works with the preferred "show current language and no language" setting.

And there's still no goddamned "show in the user's preferred language if available, if not in the default language." That's what we need. There shouldn't even be a conceptual hack of "no language" – content is either in a language or it isn't. But all that's another story.

"Also... how do I link a page I created in another page?"

For linking to other content on the site, I wanted to research what's best on a multilingual site, and haven't had a chance yet. But I'm fairly certain the best way is to do it directly to the node in the relevant language (in Drupal 5 each translation gets its own node, sadly) and to skip the language prefix.

Deep in this old thread, "Looking for internationalization use cases and application feedback" - http://drupal.org/node/88417 - a user wrote:

I'm not sure what I did wrong but the Language Switcher block failed to work on mine site. I've to use Translation block instead

Good enough for me to start out with Translation as the block, since they look identical anyway...

Resolution