Posted by toemaz on November 19, 2007 at 1:02pm
| Project: | Clickpath |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
Nice module! Thank you for releasing it.
Is there a D5.x version available? If not, are you planning to backport it?
Comments
#1
Me too.
#2
I don't have any plans to, at least right now, but if someone took a stab at it I'd happily release it. The big trick would be the breadcrumb hijacking -- there's no good place that I can think of off the top of my head where the breadcrumb hijacking would work cleanly in D5. Any thoughts?
#3
Please pardon me since I haven't even installed Clickpath yet, but I'm confused by the term "override" in the "Override breadcrumb trail" setting. By "breadcrumb hijacking" (said in #2), do you mean inserting Clickpath's own breadcrumbs (which more or less replicates the browser's back history) or simply hiding the breadcrumb trail?
#4
+1 for a D5 backport, please.
#5
The method used to manipulate the breadcrumbs on all pages is not available in Drupal 6: this task would need to be done at the theme level, not the module level, in D5.
#6
Attached is a simple backport of this module for D5.
To use, just install as you would normally, then in your theme (probably page.tpl.php) instead of echo'ing $breadcrumbs echo clickpath_get_breadcrumbs() appropriately themed, in the case of a phptemplate them that might be :
<?phpecho phptemplate_breadcrumb(clickpath_get_breadcrumbs());
?>
I've only breifly tested this backport and only with the breadcrumb replacement functionality, not block (but it might work).
Please review and comment.
a_c_m
#7
#8
For D5 see also http://drupal.org/project/trailscout I think the functionality is very similar to D6 clickpath.
#9
Thanks, looks interesting but the back port works just fine for me :)
#10
Marked #271721: Backport of clickpath to Drupal 5.7 as a duplicate.
#11
Please make a patch. Thanks!
http://drupal.org/patch/create
#12
strictly speaking its not a patch, its a whole different version!
The code i wrote works, isnt that enough for testing/review purposes?
I assumed a fully working file would be more accessible to most people for testing, once its confirmed it works, i will create a patch if your unwilling/unable to.
#13
#14
I'm sorry but Drupal 5 is far off my radar so testing and committing this is a low priority. If I get some positive reviews and demand I may commit.