Inconsistent Stack display; spacing issue

Permalink 1 user found helpful
I am installing a stack on a page type default and the stack appears in a slightly elevated position on some pages but not others, both using the same page type. Does anybody know why? I have many pages using the same page type. I recently put this menu into a stack and then installed it into the defaults of my "full_page" page type. When I view the pages in the live site, some appear correct and others are not. See my attached image for an example. On the Contact Us page the menu appears as it should. On the Privacy Policy page, also using the same page type, the menu is positioned higher.

Any ideas for me out there?

1 Attachment

Pixelfixer
 
Apos replied on at Permalink Reply
Apos
Okay, so I went on your site, and the reason is really simple. There is a CSS rule that is added and it messes up your theme.

The CSS rule that is added:
#areaStyleMain540 {background-repeat:no-repeat; margin:0 0 15px 0; }


I have noticed that depending on the page it can also be a different CSS rule such as:

#areaStyleMain285 {background-repeat:no-repeat; padding:0 0 15px 0; }


I'm am not sure what causes it, it's likely that you have an add-on that adds it automatically.

Edit: The cause appears to be because you have added a style to your block. When you click on your block in edit mode, there is a design option. It will open a dialog with custom CSS options. Verify to see if anything has been modified for the pages with the errors.
Pixelfixer replied on at Permalink Reply
Pixelfixer
Thanks for the quick reply. I just discovered this as well. Now I just have to figure out where this is coming from. I'll keep searching.
Apos replied on at Permalink Reply
Apos
I have edited my reply above. Hopefully this is the right solution. If it isn't, I'm probably really close to it, it definitely has to do with an edited design style.
Pixelfixer replied on at Permalink Reply
Pixelfixer
I wish it were that simple. I checked that early on and it is fine. Currently, in my testing, I have disabled this menu from showing on all of the child pages associated with my "full_page" page type and then added the stack to the "Privacy" page only and directly. This also causes the same problem and this div is added:
<div id="areaStyleMain285" class=" ccm-area-styles ccm-area-styles-a2991">

And, of course, the padding-bottom:15px is there.

I don't know of anything concerning an addon that is any different on the Privacy page vs. the Contact Us page. The only addon used on these two pages is the MegaMenu which is on every page.

Still confused.
Pixelfixer replied on at Permalink Reply
Pixelfixer
No doubt it is related to a design style, and that style is in the class "ccm-area-styles ccm-area-styles-a2991" This class is assigned to the Div id="areaStyleMain285".

But this is what is confusing to me:
1) Two pages, Contact Us and Privacy Policy. Both are simple pages using the same add-on menu, MegaMenu. Both are using the same Page Type; "full_page".
2) If I add the Top Menu stack directly to each page, independently, the Contact Us page works fine, but the Privacy page shows an added Div which adds a 15px padding-bottom.

Can't seem to find any difference between the pages that would cause this.
Pixelfixer replied on at Permalink Reply
Pixelfixer
Mnkras solved this one for me in an IRC chat. He discovered that I had applied a 15px bottom spacing within the Design option of an area without using a block. I have used this in the past to apply space at the bottom of an area. I should have applied the space to the bottom block in the area. For some reason, doing it this way, caused the space to be applied to the bottom of a different area, in this case, my "top-menu" area. I still don't understand the logic behind that, but removing the bottom spacing from my empty "main" area, and applying it to the lowest block, in the "main" area, instead, solved my spacing problem.

Thanks Mnkras!

P.S. I marked Mnkras's reply below as "Best Answer" to give him credit for finding the solution documented in this paragraph.
Mnkras replied on at Permalink Best Answer Reply
Mnkras
No problem, I am also going to file a bug as I think there is something funky going on...