Closed (fixed)
Project:
Menu Multilingual
Version:
8.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Oct 2017 at 10:53 UTC
Updated:
19 Dec 2017 at 12:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
matsbla commentedCan you give exact steps to reproduce?
Comment #3
berin commentedI added the block of the menu to a region with context.
I dont have there the "Multilingual options"
Structure -> context -> add context -> add reaction -> block -> place block -> main navigation and then see at the image attached the block I get without this option.
Comment #4
berin commented??
Comment #5
matsbla commentedI can confirm it is not working when using contexts.
I will not prioritize make a fix for it right now, but will consider any patch you can provide to fix the issue!
Comment #6
ipumpkinMaybe you can use this patch for panels or context.
Comment #7
vlad.dancer@ipumpkin, I haven't yet tested, but it seems that your patch should be rewrited to reflect cnahges from #2925485: Some times not translated item appear in menu.
Comment #8
ipumpkin@vlad.dancer fixed.
Comment #9
ipumpkinComment #10
matsbla commented@ipumpkin
Thanks for this!
I tested it now and It seems like this is not working when using the Menu block module,
Comment #11
ipumpkin@matsbla Add suport for menu_block.
Comment #12
vlad.dancerI believe that all this methods, like
blockForm,blockSubmit,defaultConfigurationcould be moved to the trait, let's sayMenuMultilingualBlockTraitand reused either forMenuBlockMultilingualorSystemMenuBlockMultilingualto follow DRY principle@ipumpkin, what do yuo think?
Comment #13
ipumpkin@vlad.dancer You are right,it's a good advice.
Comment #14
vlad.dancerComment #15
vlad.dancerLooks good to me. @matsbla, could you do manual test?
Comment #16
matsbla commentedTested and works good!
Comment #18
vlad.dancer@ipumpkin, thanks. Fixed.
Comment #19
vlad.dancer