Frog CMS

Nice solution, defunct! This looks like it could be very useful.

I can spot two limitations (other than the Google thing), which do not detract from the usefulness of this solution “as-is”, but may be worth noting:

• you will only ever get the English title, I suppose. But it would take something more radical to get to a multi-title solution.
• having used the page-parts for languages, I don’t see a way of doing the read more thing, although maybe I haven’t had enough coffee yet today.

Meanwhile, thanks for the write-up! Looks good!

A suggestion about NOT using the “extended” page-part for “Read more…” links is here.

I’m not sure how the thought below fits in with Martijn’s musings, but would this pictured suggestion be a Froggish way of accomplishing what this Wordpress plugin does?

Hmmmm… this is beginning to become increasingly more complex… For now, I will (personally) stick with using the copy-tree functionality to create a language specific subtree. Though I will be using defuncts function to auto-redirect the user to a new subtree based on the browser’s preferred language.

@David – You definitively won it, beware of your liver because at this pace I will have to invite you a full beer keg :P

Just a thought on David’s title posting…

Regular expressions might be quicker, and if in this sort of format too:

de: Auf Deutsch
fr: En Français

Right — solution from IRC. Craig cracked it! (That’ll be a pint for my friend, then! :P )

Use the page-part “titles”, with filter set to -none- and having this content:

de: Auf Deutsch
fr: En Français
it: Lingua Italiano
es: Si, Español

That is, with your language-specific title following their 2-character tag. Then, in your Layout where you expect the page title to come (the <h2>...</h2> bit in the default layout), put this code:

<?php if ($this->hasContent('titles')) : ?>
<h2>
<?php
$lang = $_SESSION['lang'];
$titles = $this->content('titles');
$res = preg_match('/'.$lang.':\s*(.*)/i', $titles, $results);
if($res == 1){
	$title = trim($results[1]);
	echo $title;
} else {
	echo $this->title();
} ?>
</h2>
<?php else : ?>
<h2><?php echo $this->title(); ?></h2>
<?php endif; ?>

And … it works! I’ll see about setting up a live example.* Craig says: “people can then turn it into a snippet if they like to keep it out of the layout” [from IRC]. And he’s quite right. I just dumped all that into a pageTitle snippet, called it in the Layout with

<?php $this->includeSnippet('pageTitle'); ?>

and all is as it should be! It certainly makes for a tidier layout.

Thanks, Craig! And thanks again, defunct, for setting this one rolling.

* Update: live example now online.

Fantastic. This will end in some kind of beerfest.
I think that this is the best solution if someone doesn’t want to duplicate their page trees. And again, this is a proof of the flexibility of Frog, you can do amazing stuff without the need of a ton of plugins.

We need one final thing…displaying a translated menu.

Done

:)

P.s. The menu code! It’s just a mash-up of Craig’s routine with the MadeByFrog style sidbar menu The class="current" bit even works.

<?php $lang = $_SESSION['lang']; ?>

<h3>Sidebar Menu</h3>

<ul id="nav_sub">
<?php foreach ($this->children() as $child): ?>
<?php if ($child->hasContent('titles')) {
  $titles = $child->content('titles');
  $res = preg_match('/'.$lang.':\s*(.*)/i', $titles, $results);
    if($res == 1) {
	$title = trim($results[1]);
	$childTitle = $title;
  } else { $childTitle = $child->title(); } 
} else { $childTitle = $child->title(); } ?>
    <li><?php echo $child->link($childTitle, (url_start_with($child->url) ? ' class="current"': null)); ?></li>
<?php endforeach; ?>
</ul>

Neither rude, nor insulting! It would be good to have this as an easier-to-follow tutorial. Consider it on the “to-do” list.

Where’s that wiki again…? :P

Hey there!

I got an issue with the hidden “lang” page.
When i click on the links that set the lang parameter all I get is the code from “lang” in my browser.

I’ve taken all the code from first post and followed the instructions.

If I overstep the “lang” page and set the lang parameter myself it works fine.

Did I forget something?

Greetings,
Rumpirat! Arrgh!