I recently added a few new blocks to a site. The new blocks seem to have

tags in random locations which is messing up my formatting.

The site is http://www.filmadelphia.org
The spacing at the top and bottom of the Support, Join, and Email blocks are all larger than I would like.

I can remove the tags with firebug to verify thats what I want to change but I'm not sure where to make these changes permanent.

Support and Join are created by Views. I created Email manually on the blocks page.

Any help would be awesome.

Thanks.

Comments

nevets’s picture

A quick look shows you can adjust the white space with css, the default css is adding margins/padding that you do not want.

thelastknowngod’s picture

True but that would also change the spacing on the other blocks as well. That seems like more work than should be necessary.

I'd rather just use what I have and fix the p tag problem.

nevets’s picture

Each block has a unique id so you can target the css.

thelastknowngod’s picture

bump..

any other ideas?

WillHall’s picture

nevets was right - though it isn't the block title its the block content - you have padding on block-content-inner and that is adding to the inherit padding on p.

You can isolate individual blocks with their id and style their children from that.

thelastknowngod’s picture

Alright I guess I could do it that way.

I would really like to know why the p tags are there at all.. none of the other blocks have those tags. I don't want to have to hack the css if I have to create new blocks in the future.

WillHall’s picture

They look to be in the views template.

gforce301’s picture

When you made your "email block" on the blocks page you probably used "filtered html" or "full html" as your input format. Now, just like on this forum, those formats say "Lines and paragraphs break automatically". You can interpret this as "we will add paragraph tags for you" because, generally speaking, it is considered poor form to just dump "raw" text in a web page.

As far as the blocks created by views: it would depend on the view itself, the node type being pulled and how the content of the node was entered. Basically several factors and all most likely going back to input filters.

This is "why the p tags are there at all.. ". Because they should be there.