When trying to create a basic page in my marinelli based site, any basic page has the first sidebar blocks stacked under the content. For articles, this does not occur, but for a basic page it does. It also appears the that content wrapper assumes the size of the sitecontent block the basic page is contained within (477 w rather than 1018w), and is not dynamically adjusting. The siteborder appears to be scaling correctly horizontally, but not vertically. Also of not the gird assignment of the basic page matches that of the articles. I am unsure of why it is scaling down to just the sitecontent block for a basic page, any ideas or suggestions? Thanks,

CommentFileSizeAuthor
#4 ok_comments.png5.33 KBkotoponus
#4 auction_comments.png11.25 KBkotoponus
#3 ok.png10.51 KBkotoponus
#3 auction.png12.37 KBkotoponus

Comments

popsucks’s picture

popsucks commented

Upon further review it looks like the sidebar is being placed within the same div section (site content) as the content and consequently not placing the sidebar correctly.

Here is the erroneous association of the basic page node:

<div id="contentWrapper">
      <!--start breadcrumb -->
    <div id="breadcrumb"></div>
      <!-- end breadcrumb -->
    
      <!--start innercontent-->
    <div id="innerContent">
      <!--start main content-->
    <div id="siteContent" class="grid_8"></div>
      <!--end main content-->
    
      <!--start first sidebar-->
    <div id="sidebar-first" class="grid_4 sidebar"></div>
      <!--end first sidebar-->
    </div>
      <!--end innerContent-->
    </div>

Here is the correct association as demonstrated in an article node:

<div id="contentWrapper">
      <!--start breadcrumb -->
    <div id="breadcrumb"></div>
      <!-- end breadcrumb -->
    
      <!--start innercontent-->
    <div id="innerContent">
      <!--start main content-->
    <div id="siteContent" class="grid_8"></div>
      <!--end main content-->
    
      <!--start first sidebar-->
    <div id="sidebar-first" class="grid_4 sidebar"></div>
      <!--end first sidebar-->
    </div>
      <!--end innerContent-->
    </div>

I am unsure of why the sidebar is being placed the way it is within the sitecontent div, instead of its own. Any suggestions?

kotoponus’s picture

kotoponus commented
Issue summary: View changes

popsucks saved my time finding out what is wrong with the behaviour (Thanks!) - I get some behaviour similar where side bar appears under the main content. It happens to me to a page created as Auction content type with Auction module. (I am afraid not on Basic content type!)

With the Auction page I get:

Not working

With my Basic or custom content type, I get:

Working

I will continue to look into it but if anyone knows or have any idea where to rectify this issue, I would appreciate it!

BTW I am on Drupal 7.41, Marinelli 7.x-3.0-beta11 and Auction 7.x-1.0-alpha2+24-dev

Since it is not happening on Basic or custom created content types and on a contributed module for now, I guess you may say it is to do with Auction module, and I will look into that in that perspective, but if you have got any thoughts, I would be grateful if you can share. Thanks.

kotoponus’s picture

kotoponus commented
StatusFileSize
new auction.png12.37 KB
new ok.png10.51 KB
kotoponus’s picture

kotoponus commented
StatusFileSize
new auction_comments.png11.25 KB
new ok_comments.png5.33 KB

Ok, I start to suspect that one of the the page.tpl.php conditions is not met properly.

Please see below element inspection from Auctions type content, which is not working for me:

closed by "main content"

The innerContent div is closed by </div> of main content (<!--end main content-->), which should not be paired up. The main content then is closed by </div> of drupal content (<!--end drupal content-->).

So, it makes me think that there is some mis "buttoning" of open and close divs.

In the page of a content type which works, the pairing appears working as intended as the innerContent div closes with seemingly with an appropriate close div (<!--end innerContent-->):

closed by "innerContent" div

I will see if I can keep pursuing any further along this line.

kotoponus’s picture

kotoponus commented

Ok, that was silly - it was a user error. In page.tpl.php, I had a condition which omits an open div when the display content type was Auction. Which will do it. If someone experiences something like above, check with your custom node.tpl.php too. There may be a problem there. Hahaha.

kotoponus’s picture

kotoponus commented

I suspect popsucks was doing the same or similar thing as me to Basic content type?