Reviewed & tested by the community
Project:
Auto Menu
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
26 Apr 2011 at 15:44 UTC
Updated:
2 Oct 2014 at 07:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Johnny vd Laar commentedThere is currently no work on the D7 version. We just released a 6.x-2.0 version so if anyone is interested to port automenu then we'd appreciate it that you focus on this version.
Comment #2
Jean Gionet commentedwould love to see a D7 port! I'm looking for a solution to work with the Workbench module!
Comment #3
ipwa commentedAs a workaround for now, I just realized you could use:
http://drupal.org/project/nat + http://drupal.org/project/taxonomy_menu
Comment #4
dreizwo commentedHere's a first version for automenu and D7. It only supports menu-link creation for nodes. Untestet, but works for me.
Comment #5
rogical commentedjust follow #3 's suggestion, I thought that's too complicated,
some may just want to automatically specify the parent menu and add a menu on node creation,
this module would be the just right one.
Comment #6
rogical commented#4 your package seems doen't work for me, my drupal is 7.2
Notice: Undefined index: plid 在 automenu_automenu_create() (行 122 在 /opt/difang/dev/pjkaixin/sites....
PDOException: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'expanded' at r.....
More details are attached.
Comment #7
dreizwo commented#6 You're right!
Here's a new completly redesigned version of automenu. It includes some new features and bugfixes:
>You can enable/disable automenu per contenttype.
>You can hide messsage
>You can ignore the status (published or not) of the child
>Contains classes to create automenu-links programmatically inside of other modules (@see sourcecode class.AutomenuCreateLinkDefaultImpl.php)
>Bugfix: uses the menu of menu-settings
Give it a try - and let me know if it's working now..
Comment #8
rogical commentedIt seems working fine, Thanks!
Currently get one notice when anonymous posting:
Notice: Undefined property: stdClass::$name on Automenu->initialize() (row 44 in /opt/difang/dev/pjkaixin/sites/all/modules/automenu/class.Automenu.php).
Comment #9
dreizwo commented#8 Should work now - but untested....
check for anonmyous user added
let me know....
Comment #10
Geex2011 commentedhey guys, i installed the port and it seems working fine so far ... but I have question, why does it append a "node/" to the node title?? is there a an important reason for it ??? if not, how can i remove it??
I really find this module very helpful and appreciate you time and efforts, thanks.
Comment #11
otx commenteddreizwo, thanks for the D7 port, great job! I just installed the module and it seems to work fine for me. But as described in #10, it adds undesired "node/" string in front of newly created menu title. Probably just copy paste problem in class.Automenu.php, I believe that changing
into
fixes the problem :)
Comment #12
dreizwo commented#11 otx - thank you for the hint!
as described... here's the new version...
Comment #13
marcusx commentedIs the taxonomy functionality in the port? #692360: Automenu with taxonomy integration I assume not, or am I to blind to find it?
Thanks!
Marcus
Comment #14
dreizwo commented#13 dear marcus!
sorry, but there's still no plan to integrate taxonomy
Comment #15
dreizwo commentednew version of automenu
needed for the sandbox project cttree see : http://drupal.org/sandbox/dreizwo/1209134
Comment #16
dreizwo commented#15 I'm dreadfully sorry.
this is of course wrong here's the right version
@admin | @community how to delete the attachment of #15??
Comment #17
Johnny vd Laar commentedi'm sorry for the lack of attention but i've broken my leg so didn't look much on d.o
I've mailed you back about further steps.
Comment #18
camdarley commentedSubscribe, and waiting for taxonomy integration. Thanks for your job.
Comment #19
Johnny vd Laar commentedDoes anyone know how to make someone a co-maintainer? Don't know if I can do this as I'm not the main maintainer.
Comment #20
corneverbruggen commentedHi,
yes, I know how to - currently I still am the main maintainer, but (as you have noticed) am not active in this project anymore.
@Johnny vd Laar: are you willing to be the main maintainer? If so, I will request a transfer of project ownership.
Comment #21
Johnny vd Laar commentedwell we don't use the module anymore as drupal 7 more or less fixes the issues for which we used auto menu. but perhaps dreizwo is interested?
Comment #22
rogical commented@dreizwo, hope you could take the role of D7 branch maintainer.
Comment #23
13rac1 commented#16 looks ok, but needs work. It doesn't follow the Drupal coding standards, and seems to re-invent some standard Drupal functionality. Can you tell me why it is class based? It seems like it requires significantly more code to be class based. The menuing system between D6 and D7 hasn't changed too much, a complete direct port (like #4) would probably be better.
Comment #24
matiki commentedsubscribing
Comment #25
wojtha commentedHello there, after initial trial to port this module to D7 I decided to start from scratch.
The code is now in my sandbox called "NodeAutoMenu" which is basically something like AutoMenu - The Next Generation.
Comment #26
lscalado commentedIf someone try checkout NodeAutoMenu, try using this command:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/wojtha/1331132.git nodeautomenu
Comment #27
Johnny vd Laar commentedIsn't it a better idea to merge the two modules and that you take over this module as maintainer?
Comment #28
wojtha commented@Johnny vd Laar ok, if you like it :-) But the sandbox is still just an experiment, I want to reconsider couple of things.
P.S. AutoMenu - The Next Generation name doesn't neccesarilly mean that I wanted to create new project, that just means that it is rewritten from scratch.
Comment #29
rogical commentedI think it's time to open a D7 branch, and maybe can consider Dealing with abandoned projects.
Comment #30
ipwa commentedHi @rogical, @Johnny vd Laar seems to be the current maintainer, and although he hasn't committed code in a while he's actively involved in this issue for example, so I don't think I'd classify this project as abandoned. He has also invited @wojtha to be a co-maintainer, so all he needs to do is add him in the maintainers tabs.
Comment #31
Johnny vd Laar commentedI'm not the main maintener so I don't think I can add people to the project. @corneverbruggen is the main maintainer so he can add people. I think it would be best if someone takes over the main maintainership but that's up to corne to decide I think.
I've committed code in the past but I'm not using the module myself anymore so I won't do any coding on it anymore.
Comment #32
ipwa commentedEven as a co-maintainer you can add maintainer if you have enough permissions to do so. Ask @corneverbruggen to give you those permissions, or for him to add @wojtha himself.
Comment #33
Johnny vd Laar commentedI don't see the page to add maintainers so I guess I don't have sufficient permissions. @wojtha can you contact @corneverbruggen to get maintainer access?
Comment #34
fretje commented@wojtha: I installed your module from the sandbox, but I have a problem with the taxonomy mapper. I have my content type linked to a menu which already contains a hierarchy of links to the taxonomy terms. When I check the "basic taxonomy mapper", no menu items get created. When I choose "default parent", they get created, but of course in the "root" of the menu. How exactly is this taxonomy mapper supposed to work? Am I missing something?
Also when using "default parent": When I replace a generated menu item inside the menu (so it's actually underneath the taxonomy term it belongs to) then it gets re-created in the root when the node gets saved. Wouldn't it be interesting to check on that, and only change the title/description of the menu-item, instead if re-placing it?
Comment #35
wojtha commented@fretje taxonomy mapper is very fragile now, it doesnt know how to create the taxonomy menu items by itself, so you need to create the needed menu structure itself - e.g. using http://drupal.org/project/taxonomy_menu_form
Comment #36
fretje commented@wojtha that's exactly what I did... I did use http://drupal.org/project/taxonomy_menu though, but no menu-items get created...
Comment #37
fretje commentedI found the problem... Apparently it was a typo in the settings string for the 'nodeautomenu_vocabulary' setting.
I had to change the string 'autonodemenu_vocabulary_' to 'nodeautomenu_vocabulary_' 2 times in the nam_taxonomy.module file.
Now the menu items get created, but I bump into another problem after adding 5 menu-items this way, when I want to add the 6th one (it doesn't matter if the 5 previous ones are under the same taxonomy term, or different ones), I always get this warning:
'Node auto menu link can't be created because 2 ancestor menu items are missing: mycategory1 > mycategory2. Create these items first and try to save this node again.'
But the 2 categories mentioned do actually exist.
When I remove a menu-item, I can add another one. Any ideas?
Comment #38
fretje commentedOkay, I figured it out... sort of. Not sure of all my changes, but here's what I did:
In the 'nodeautomenu_subtree_data' function, I made sure the query was always ordered, by taking the orderBy statement out of the 'if ($link)' clause:
and in the 'nodeautomenu_search_menu_parent' function, I only extract the 'below' array out of the fist node of $sub_tree when $plid is not 0 (as apparently that's not needed in that case):
I'm not really sure though if this is actually needed when $plid is not 0, as that's never the case in my case.
But anyways, with these changes, everything seems to work 'as advertised' ;-)
Comment #39
Yuri commentedIs this good enough for a dev version?
Comment #40
office@w3k.at commentedHow about this D7 module:
http://drupal.org/project/menu_position
Comment #41
replicaobscuraMenu Position does not solve the same issue. Menu position 'feigns' an item being in the menu, but it doesn't actually add any nodes to the menu. The rules you create are added to the menu, and if the page you're on matches one of those rules, then the page you're on shows up in the menu where that rule is.
We still need a good way to sync up nodes with menu items automatically based on some sort of rule structure.
Comment #42
webadpro commentedAny update on this?
Comment #43
webadpro commentedThere seems to be missing a js file also.
Line 54 automenu.module:
'automenu' => drupal_get_path('module', 'automenu') . '/automenu.js',Comment #44
webadpro commentedany update guys?
Comment #45
kristen polI tried NodeAutoMenu from #25 and get:
:/
Comment #46
webs.com.mt commentedI have downloaded the module provided in #4 and made some changes as it was not working for me. I am attaching the modified code.
This is working on Drupal 7.14.
Comment #47
elgandoz commented#46 worked perfectly for me (7.22). Is it possible to commit as 7.x release?
Comment #48
windmaomao commentedthis module works great, I have a request, the menu entry URL might not be the node link, instead, I want to have sort of pattern, ex. node/%/display, or xxxx/. I guess i can dig in and add that.
Comment #49
gaëlg#25 works great for me. #46 did not (duplicates on node updates). #25 is more advanced and the code seems cleaner. This should definitely be the D7 dev version. It would ease downloading, debugging and contributing.
+1 for wojtha as a new maintainer
Comment #50
botris+1 for #25, works great
Comment #51
Andrew Gorokhovets commented+1 for #25, works great
But only nodeautomenu.module
In nam_taxonomy.module settings is not saved on the content type edit page.
Comment #52
rooby commented+1 for #49 if wojtha is still interested.
Comment #53
ajwn commented#46 works here on 7.31 thanks for the contribution.