Analyze Routes in runway

I get the matched route

Matched route: leteste
Page arguments:
Array
(
    [0] => /leteste
)

but not a list of all routes defined in the backend.

Later on the same page, I planned to filter content depending on the position of the selected route in the route list.

The goal of this is of course to edit one page with fields in multiple languages.

Is there a way to analyze a route and get a pattern from it? Maybe match it to a <perch:pages> field?

I was trying to find out if a "single tree" structure with perch Pages is possible with existing on-board tools.

Homepage (all on one page, 3 langs)
+-Subpage (all on one page, 3 langs)
+-Subpage (all on one page, 3 langs)

So I wanted to detect from the URL/route which language has been preselected.

Wich, having given it a little more thought, is not even necessary: Just add a language marker like /en/ to the URL and go from there.

But how do I handle that incoming route then? Say it's /en/aboutus and /de/ueberuns Hmmm, I could strip the first bit in .htaccess and store it in $_GET['lang'], and then send the rest of the URL This might also work with domains as indicators for the language.

# Perch Runway
RewriteEngine On
RewriteRule ^/de/(.+)$ $1 [L,NC]
RewriteRule ^/fr/(.+)$ $1 [L,NC]
RewriteRule ^/en/(.+)$ $1 [L,NC]
RewriteCond %{REQUEST_URI} !^/perch 
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule .* /perch/core/runway/start.php [L] 

What do you think about prepping a runway URL in that way?

If I can bring it into each navigation template via PerchSystem::set_var() and if it's safe to do some rewriting like the above before passing it to runway: I don't think that would be even necessary.

It doesn't. Probably due to my .htaccess skills. It's too early for me to ask you for the routing prefix, though, as I'm only doing this proof of concept style.

Just an idea: if in start.php instead of

$RoutedPage = $Router->get_route($_SERVER['REQUEST_URI']);

you'd replace that by

$RoutedPage = $Router->get_route(PERCH_REQUEST_URI);

And then in config.php

define('PERCH_REQUEST_URI', $_SERVER['REQUEST_URI']);

I (ehm, integrators...) could modify the value for PERCH_REQUEST_URI dynamically (e.g. with a simple str_replace).

Hmm.. getting on not too bad.

If the language is based on the domain, it should work, start.php uses the REQUEST_URI.

RewriteCond %{HTTP_HOST} ^germandomain.ch$ 
RewriteRule ^(.*)$  $1?lang=de
RewriteCond %{HTTP_HOST} ^frenchdomain.ch$ 
RewriteRule ^(.*)$  $1?lang=fr

I will be using this approach and will post the working .htaccess later.

Albeit, with the prefix it's not so easy, as a Redirect (R) flag is necessary to alter the REQUEST_URI - which of course, results in a redirect, which we don't want.

RewriteRule ^(de|fr|it)/(.*)$  index.php?lang=$1 
RewriteRule ^(.*)$  $1?lang=de

So yes, maybe a global routing prefix would be a fine idea. Or, see my last post, allow developers to determine from where $Router->get_route gets its information (without hacking start.php)! That would be probably be the simpler way.

Happy Holidays!