Comments on: How to handle urls for “mini sites” in panels 2 http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/ Men have become the tools of their tools. - Henry David Thoreau Tue, 06 Jan 2009 19:40:48 +0000 http://wordpress.org/?v=2.5 By: ekes http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/#comment-170 ekes Wed, 16 Jul 2008 07:05:34 +0000 http://pajamadesign.com/?p=32#comment-170 I've just done similar on http://demo.nabuurtest.com/ http://feedback.nabuur.com/ (both devel sites one should be working to some degree at any moment) and did it with custom_url_rewrite. To solve the i18n problem I just called the i18n_path_alias from within my custom_url_rewrite. The i18n module is quite civilised here and doesn't create a custom_url_rewrite if there is one existing already, so no patching required there either. So cutting useful bits from code you have something like: <code> if ($op == 'alias') { $result = i18n_url_rewrite($op, $result, $path); ... elseif (preg_match("@node/([0-9]+)/($subpages_or)(?:/feed)?$@", $path, $path_pieces)) { // [group|village]/[background|images|...] $group_node = 'node' .'/'. $path_pieces[1]; $group_path = drupal_lookup_path('alias', $group_node); if ($group_path != '') { $result = $group_path .'/'. $path_pieces[2]; } } ... if ($op == 'source') { if (preg_match("@($types_or)/([^/\?\s]+)/($subpages_or)(?:/feed)?$@", $result, $path_pieces)) { // [group|village]/[background|images|...] $group_type = $path_pieces[1]; $group_path = $group_type .'/'. $path_pieces[2]; $group_node = drupal_lookup_path('source', $group_path); if ($group_node != '') { $result = $group_node .'/'. $path_pieces[3]; ) } ... $result = i18n_url_rewrite($op, $result, $path); )</code> I’ve just done similar on http://demo.nabuurtest.com/ http://feedback.nabuur.com/ (both devel sites one should be working to some degree at any moment) and did it with custom_url_rewrite.

To solve the i18n problem I just called the i18n_path_alias from within my custom_url_rewrite. The i18n module is quite civilised here and doesn’t create a custom_url_rewrite if there is one existing already, so no patching required there either.

So cutting useful bits from code you have something like:


if ($op == 'alias') {
$result = i18n_url_rewrite($op, $result, $path);
...
elseif (preg_match("@node/([0-9]+)/($subpages_or)(?:/feed)?$@", $path, $path_pieces)) {
// [group|village]/[background|images|...]
$group_node = 'node' .'/'. $path_pieces[1];
$group_path = drupal_lookup_path('alias', $group_node);
if ($group_path != '') {
$result = $group_path .'/'. $path_pieces[2];
}
}
...
if ($op == 'source') {
if (preg_match("@($types_or)/([^/\?\s]+)/($subpages_or)(?:/feed)?$@", $result, $path_pieces)) {
// [group|village]/[background|images|...]
$group_type = $path_pieces[1];
$group_path = $group_type .'/'. $path_pieces[2];
$group_node = drupal_lookup_path('source', $group_path);
if ($group_node != '') {
$result = $group_node .'/'. $path_pieces[3];
)
}
...
$result = i18n_url_rewrite($op, $result, $path);
)

]]> By: eric http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/#comment-169 eric Wed, 16 Jul 2008 01:30:08 +0000 http://pajamadesign.com/?p=32#comment-169 Hey Jacob, To follow up on Jeff's note, here is a visualization of how context helps simplify site handling like blocks/menus/views/panels around it's natural IA: http://www.developmentseed.org/blog/2008/jun/13/wri-org-redesign-launches-using-content-ui hope that helps the Mexican project. Te vayas bien! Hey Jacob,
To follow up on Jeff’s note, here is a visualization of how context helps simplify site handling like blocks/menus/views/panels around it’s natural IA:
http://www.developmentseed.org/blog/2008/jun/13/wri-org-redesign-launches-using-content-ui

hope that helps the Mexican project. Te vayas bien!

]]> By: Jeff http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/#comment-168 Jeff Tue, 15 Jul 2008 12:35:02 +0000 http://pajamadesign.com/?p=32#comment-168 You may want to look at <a href="http://drupal.org/project/context" rel="nofollow">context</a> and <a href="http://drupal.org/project/spaces" rel="nofollow">spaces</a>. The context package includes the context_prefix module which handles generic path prefixing and also domain handing using the strategy Earl mentions above (and we've made it compatible with i18n). What context_prefix will do is establish a context based on the prefix, then strip the prefix off the path so the rest of Drupal respond like normal to a request. So for something like 'water_campaigns/blog' this would set a context value based on 'water_campaigns' and then let Drupal respond to 'blog'. In the views that generate content at such a callback you'd add an argument to filter based on the context, so that only appropriate content would be shown. Spaces makes this second part a bit easier by providing OG integration. Among other things it'll set an og_group_context based on a prefix, so that you only need to add the normal 'is in the current group' argument to you views and then everything 'just works'. You may want to look at context and spaces. The context package includes the context_prefix module which handles generic path prefixing and also domain handing using the strategy Earl mentions above (and we’ve made it compatible with i18n). What context_prefix will do is establish a context based on the prefix, then strip the prefix off the path so the rest of Drupal respond like normal to a request. So for something like ‘water_campaigns/blog’ this would set a context value based on ‘water_campaigns’ and then let Drupal respond to ‘blog’. In the views that generate content at such a callback you’d add an argument to filter based on the context, so that only appropriate content would be shown. Spaces makes this second part a bit easier by providing OG integration. Among other things it’ll set an og_group_context based on a prefix, so that you only need to add the normal ‘is in the current group’ argument to you views and then everything ‘just works’.

]]> By: Jacob Singh http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/#comment-167 Jacob Singh Tue, 15 Jul 2008 10:03:53 +0000 http://pajamadesign.com/?p=32#comment-167 Hi Earl, I looked into that, but it didn't work for me. Furthermore, it conflicts with i18n which is a PITA... Maybe I did it wrong, but it really did not work for me... Perhaps I used the wrong code? Do you have an example? Thanks for posting! Jacob Hi Earl,

I looked into that, but it didn’t work for me. Furthermore, it conflicts with i18n which is a PITA… Maybe I did it wrong, but it really did not work for me… Perhaps I used the wrong code? Do you have an example?

Thanks for posting!
Jacob

]]> By: merlinofchaos http://pajamadesign.com/2008/07/15/how-to-handle-urls-for-mini-sites-in-panels-2/#comment-166 merlinofchaos Tue, 15 Jul 2008 00:37:41 +0000 http://pajamadesign.com/?p=32#comment-166 You can accomplish the same basic thing in custom_url_rewrite(), which is something you also should put only in a client module. You can accomplish the same basic thing in custom_url_rewrite(), which is something you also should put only in a client module.

]]>