Thanks for the great work in this module. Mega menus are awesome and you make it easier to implment them.

I am using version 7.x-1.1 of Minipanels, with 7.x-1.2+7-dev of CTools (because with the recommended version of CTools, it wasn't working at all)

But there are things that are still impossible to configure from the User Config. Screen:

- Horizontal and Vertical alignment being one of them. I needed for the menu to align always with the border-left of the first item, and wished for the menu to pull down from the border bottom of all items. The negative number for the horizontal alignment was always ignored. Trying to displace the pop-out 5px down was impossible. It didn't matter what number I entered in the field, it always sent the menu to the middle of the page.
I started playing arounf with the position pulldown, and changing parameters and for relative, for example, the menu didn't show at all.

The only way I had to position the pop-out where I wanted it, was to force it via its selector in my css sheet, like this:

div.qtip-contentWrapper {background-color: transparent !important; margin-top: 33px; margin-left: -10px;}
(Setting the position to Absolute and with Custom alignment in reference to the menu container div)

Also, the width never automatically adjusted to the content. The content is 960px and the pop-out was always opening to it's maximum allowed by default, 250px. I had to set 960px for both max and min width, in the default config.

With all that, it works perfect and makes the website eye-candy.

Have a great day!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Kendall Totten’s picture

I too am having a great deal of trouble with the horizontal and vertical adjustment just as cara described. The problem with overriding with CSS is that it becomes absolutely positioned to the edge of the window instead of lining up with the menu items.

I'm trying to align all of the flyouts to the edge of the main content area (so that they are all 960px wide on the normal desktop view) and all flyouts are all positioned in the same place.

I plugged in a 1 or -1 as the vertical adjustment and now the menu is positioned 1761px down the page. Where that number came from I don't know.

The only thing I think I can do is to leave the qtip container where it is and then position the qtip-wrapper using negative margins.

tusik’s picture

I am positioning towards a div that has a margin: 0 auto; and hence it's positioned correctly, right below the main menu.
I think there must be some % issue with that snippet of code, and instead of reading pixels it's reading percentages. otherwise I can't see why the increment is so out of proportions. It would also make sense for negative numbers to be ignored.

But there are yet other issues. If you do not fix the z-index for the wrapper to be below the menu, on roll out from the menu item, it will not disappear to show the minipanel for other items.

tusik’s picture

Issue summary: View changes

Some important info was added

WickedJ’s picture

sub.

vip_sa’s picture

Yes it does not work

tom friedhof’s picture

Issue summary: View changes
Status: Active » Needs review
FileSize
644 bytes

The Qtip library expects the values to be integers coming from the settings page. The attached patch forces the type to int so that when array is converted to js, it is an integer.

vip_sa’s picture

I will test it and let you know if it works thank you very much for the patch

selfuntitled’s picture

Well, this patch no longer applies cleanly to the current version of the module, so I needed to apply it manually. That said, it seems to resolve the problem. Looks good to me! If I have a few minutes I'll re-roll something that applies to current code.

vip_sa’s picture

OK that will be great!

jenlampton’s picture

Status: Needs review » Reviewed & tested by the community

This patch still applies cleanly to 7.x-1.1. It solves the problem for me, the Horizontal and Vertical adjustment settings are now affecting my menus.

selfuntitled’s picture

Looks to me like this is working, and is ready to be committed.

DamienMcKenna’s picture

Status: Reviewed & tested by the community » Fixed

Thank you. I've committed this to both the 6.x-1.x and 7.x-1.x branches.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.