Posted by fde on January 23, 2009 at 4:46pm
Jump to:
| Project: | Menu Settings per Content Type |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I backported the 6.x-1.0 version of ctm to Drupal 5.
I did a bit of testing and am using it on one of my sites. If others are interested they are welcome to test it on their own and leave comments if they find issues.
Maybe it could even be added to the cvs?
Notes:
- Use at your own risk...
- I had to manually change the weight of the ctm module to something greater than the weight of the core menu module in the system table to make it work.
| Attachment | Size |
|---|---|
| ctm-5.x.zip (unofficial) | 8.93 KB |
Comments
#1
I tried your version for drupal 5 and seems to work (without change the weight of the ctm module). do you have CVS access to give access to ctm to upload the module?
should i upload myself?
#2
I don't have CVS access, I guess this is my first real contribution to Drupal :-) So don't hesitate to upload it if you think it's ok and that it could be useful to others.
#3
You'll never know when you'll need a CVS account in drupal.org, but now you have all you need to apply for a cvs account.
other infos about CVS : CVS account on drupal.org.
If you succeed with CVS, let me know to give you access to CVS of this module.
in the mean time, i'll try to upload your version of the ctm module.
keep drupalling!
#4
A 5.x version is up. I'm marking this issue as fixed.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.
#6
Why was this marked as fixed/closed? The 5.x stable version is still dated Feb 2009...and exhibits the original issue.
#7
I agree this is not fixed. The 5.x-1.0 at the project page is still the version that does not work properly for me. This unofficial version does.
But the non-working 5.x-1.0 is described "backported 6.x-1.0 version of ctm to Drupal 5 by fde." if I get what it says right. Anyway, thanks fde.
#8
should be fixed
#9
Automatically closed -- issue fixed for 2 weeks with no activity.