wayoflinux

Hello,

So it is working. 🙂
It also needed the .post class to be marked, and I added a media query so on small screens the original scaling would happen.

Here’s my final solution:

/* display content area widget posts in two columns, on large screens only */

@media only screen and (min-width: 719px) {
#panel-85-1-0-2 .widget_siteorigin-panels-postloop article .post,
.entry #panel-85-1-0-2 .alx-posts li
{
  width: 50%;
  float: left;
  margin-bottom: 20px;
}
}

The #panel-85-1-0-2 id is there as i wanted this to happen only in that specific place. The solution was so simple, I would not have even thought of it. 😀

(On a side-note, for anyone who cares, I could not yet make this happen using the same logic on the Post Loop widget, whatever I tried, so it remains a theme-, and widget-specific solution for now.)

Thanks again, you were of great help! Marking as resolved.

Hi,

Sorry, I though the URL would be visible.

So I created a page to show what i mean.

This is he expected result, the standard Blog page on my site. The featured item is large at the top and below the rest are organised in two columns, as usual:

http://wayoflinux.com/the-tao-of-linux-blog/

Next you see a normal page, where widgets have been added. First the AlxPosts widget from the theme itself, after that the Post Loop widget (I think it1s from Jetpack).

Both of these show the post loop basically full-width, no columns, whatever i do.

http://wayoflinux.com/blogrolltest/

I poked around the little. So contents.php does not concern the layout of columns, it only has the article bit. obviously the specific layout gets added somewhere else, and the widgets will not get that.

the solution seems easy, make a page template, which is just like that of the blog itself, and create a page with that template. I guess (although I don’t know how exactly that would work with the PageBuilder, so it might be difficult).
Problem is, I have not got enough experience with either WordPress or PHP for this…

Any help would be appreciated!

Thanks (and sorry about the delayed reply)!