Closed (fixed)
Project:
Menu Editor
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 Jan 2011 at 06:26 UTC
Updated:
15 Apr 2013 at 20:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
KirstenLangholz commenteddito
Comment #2
donquixote commentedI will produce a D7 version, just not sure when this will happen.
I need to do a bit of research about the changes of the menu_links system in D7. If you can give me some pointers, that might help.
Comment #3
AdrianC-1 commentedSubscribing
Comment #4
MatthijsG commentedSubscribing
Comment #5
Frits1980 commentedsubscribing
Comment #6
danny_joris commentedsubscribing
Comment #7
clashar commented+1
Comment #8
donquixote commentedThe multicrud module (6.x-2.x branch) now contains an experimental implementation of a multicrud-powered menu editor. This will be the direction when we go D7.
The good thing about multicrud:
- Nice js features (you will notice if you try it).
- The actual menu_multicrud module code is much much shorter than menu_editor, because so much of the logic is done by multicrud itself. This will make a lot of work easier.
So here is the battle plan:
1. Make multicrud D6 stable enough. Identify and fix possible shortcomings of the multicrud API.
2. Start a D7 branch for multicrud. I imagine this will involve some fighting with the D7 form api. I have not yet studied how D7 fapi is different from D6 API, but I very much assume that it is.
3. Port menu_multicrud (shipped with multicrud) to D7.
4. Let this flow back into menu_editor 6.x-4.x and 7.x-4.x, and make multicrud a dependency.
You can speed up this process with testing, feedback and code reviews!!
Comment #9
Jeff Burnz commentedAwesome donquixote, looks like a plan, definitely here to help with testing and feedback - actually I have been looking for a really good composite form element for D7 and found nothing that really fits my use case (all the others create micro-entities, whereas I just need a basic composite form element). Good stuff, will be participating in both issue queues as a tester.
Comment #10
mortendk commented+1
Comment #11
adriaanm commentedsubscribing
Comment #12
xandeadx commentedsubscr
Comment #13
marcusx commentedsubscribe
Comment #14
alexbk66- commented+1
Comment #15
vpolotskiy commentedSubscribing
Comment #16
vvs commented+
Comment #17
erlendoos commentedsubscribing
Comment #18
donquixote commentedBattle plan changes:
Multicrud is definitely the future, but for now let's port the 6.x-2.2 version to D7 as-is.
Advantage: The current version (6.x-2.2) of Menu editor is stable as a dream, no feature requests or bug reports have been posted for a loong time. This means, very little to port between versions in the near future. Very pleasant for maintenance
I do not have any interesting D7 use case myself atm.
Instead, any of you can feel invited to volunteer.
I will not immediately give people commit access, would like to see some code first (unless you can tell me a way to give limited commit access).
If you want to show up in the list of maintainers, or want your work to be visible as a git commit, I am sure we can find a solution.
Comment #19
tomas.teicher commentedI have made module Menu operations (http://drupal.org/project/1164672/git-instructions) in D7 that has similar functions. Now it is just sandbox project. Maybe it can be published or adjusted as Menu editor for Drupal 7.
Comment #20
chriscalip commentednice, checking out menu operations.
Comment #21
chriscalip commentedHey Donquixote,
I believe we tackled issues together on our mutual interest in multicrud module, nice to team up with you again on another task. So i am taking you on that offer; going for a straight forward port of 6.x-2.2 to d7.
Created Sandbox project http://drupal.org/project/1240648/git-instructions
Created branch 7.x-2.x currently coding on d7 port.
cheers,
Chris Calip
Comment #22
donquixote commentednice to see some activity.
i am not going to do anything before september (very busy type of traveling). after that, we will see.
Comment #23
chriscalip commentedNice summer traveling :) .. btw I think I am making progress, mind if I get git commit access I promise to just deal with the 7.x-2.x branch
Comment #24
donquixote commentedwhat do i need to do to give you access?
Comment #25
chriscalip commentedWell first create a branch 7.x-2.x
Then on the project page of Menu Editor click tab "Maintainers" -- add me and give me ('write to vcs','maintain issues'), thats all i need.
Comment #26
donquixote commenteddone.
Comment #27
Bahlool commentedsubscribing
Comment #28
Vote_Sizing_Steve commentedLooking forward to the D7 version of this time-saving module.
Comment #29
chriscalip commentedme too; got redirected to commerce for a bit. hoping to continue after that commerce module im working on is done.
Comment #30
Juan C commentedSubscribe
Comment #31
milos.kroulik commentedsubscribe
Comment #32
dAv3 commentedSubscribe
Comment #33
raijin commented+1
Comment #34
vdchristelle commentedAny news on the D7 version?
Comment #35
peluhnya commentedsubscribe
Comment #36
gynekolog commentedStop subscribing, start following -> http://drupal.org/node/1306444
Comment #37
dsdeiz commentedHi, Any help I can provide? I see 6.x-3.0-unstable3 from the repository, does this mean 7.x is going to start with 3.x version or stick with the 2.x version?
Comment #38
dsdeiz commentedHi! Here's a port of menu_editor in D7. At the moment, only the core menu_editor is ported as I'm not familiar with the included submodules. Also, I have temporarily removed the support for i18n as I'm not familiar with the D7 version. But I'll try to figure these out. Hope there are no major bugs on the basic functionality.
Comment #39
dsdeiz commentedSorry, I missed to test menu items that cannot be deleted. Attached update.
Comment #40
donquixote commentedThanks, this is great news!
And it works. Going to make this a release.
Comment #41
dsdeiz commentedHey guys. If anyone is still interested, feel free to test the latest 7.x-1.x. Thanks!
Comment #42
tahiticlic commentedAutocomplete doesn't work on last dev version (unstable1) with an error on me_path_module/menu_editor_path_autocomplete.module, line 56 : argument 2 passed to db_query must be an array
Comment #43
dsdeiz commentedHi! Yep, unstable1 doesn't have menu_editor_path_autocomplete ported to D7. You can try out 7.x-1.x-dev. Thanks!
Comment #44
simon georges commentedIn D7, there's the Content Menu module too, maybe it could be possible to join forces?
Comment #45
donquixote commentedWe have -unstable3 now.
#44: Interesting, going to have a look!
Comment #46
donquixote commented#44, can you give some feedback on
#1676718: Comparison with "Content Menu" module: Features and Usability
#1676726: Joining forces with "Menu Editor" module?!?
?
Comment #47
donquixote commentedUsage stats show around 500 installs of the D7 version.
There are some bug reports, but the number of people reporting problems seems to be small.
I think we can consider this fixed.
Please continue to test and give feedback, so we can finally publish a 7.x-1.0 stable!
(already made a 7.x-1.0-beta1 just now)
And please help on these issues if you can:
#1824958: Damaged nodes / cannot edit body field.
#1922278: PDOException: SQLSTATE[HY000]: General error
Comment #48
donquixote commented...
Comment #49
donquixote commentedAnd I should add, big thanks to dsdeiz for making this possible!