[michaelbuster]

Terrific thanks!

[michaelbuster]

thanks Lauren, eventually I did it with Masonry and it works the way I want now (on another domain and theme, not the one in my first post!).

[michaelbuster]

the only tutorial available on using Masonry in Genesis (sridharkatakam...) did not work so well for me, I was hoping that removing some spaces was possible with a few CSS changes.

[michaelbuster]

whatever the theme, even with no child theme, the Featured Posts widget looks weird: one long column instead of two, sometimes depending on the browser window size, sometimes not. Maybe it has to do with mobile responsiveness, but it is very annoying. The link above points out this issue as well.

[michaelbuster]

It appears to be working perfectly and solved both problems (exclude some categories and number of posts to show). Thanks a million for taking time to solve this!

[michaelbuster]

Sure I tried in the fuctions.php file, problem is I do not understand the code.

Imagine I don’t want to show categories 2258, 2806, 2695, 2654, 2767 in the main loop.

Before 1.9 I used this in genesis_grid_loop:  ‘category__not_in’ => array(2258, 2806, 2695, 2654, 2767)

Now with 1.9 what the syntax would be? To exclude an array of categories from the main loop?

A syntax like this (along with the rest of the code above, in functions.php)

$query->set( ‘cat’, ‘-2258, -2806, -2695, -2654, -2767′ );

does not work.

I opened a ticket yesterday but no reply, I have multiple sites broken, would be grateful is someone could help.

[michaelbuster]

Brilliant, it worked! Hopefully they will fix the problem with Genesis 1.9.2 so we can uncheck from Appearance>Header, as it should be.

Putting out buggy updates and having people fix them themselves is not a good way to run a business though. I will get tons of support emails from my customers because of this. Updating to 1.9 _checks_  'Show header text with your image' even if previously unchecked!

[michaelbuster]

Sorry I don't understand what is this:

$query->set( 'cat', '-1,-2' );

I've always used this:

‘category__not_in’ => array(2258, 2806, 2695, 2654, 2767)

this wouldn't show (before the 1.9 update) categories 2258, 2806, 2695, 2654, 2767 from the main loop. I get the categories IDs hovering onto them.

What is '-1, -2' ?

If I use $query->set( 'cat', '-2258, -2806, -2695, -2654, -2767' );

it doesn't work.

 

[michaelbuster]

Didn't do nothing thanks anyway Susan. This is a minor problem (still annoying, customer's angry) but I have also another thread and even opened a ticket because of major problems with the Genesis loop in home.php. Really screwed up with this 'upgrade'.

 

[michaelbuster]

Sorry I do not understand that code. Before 1.9 I've always done this:

if ( function_exists( 'genesis_grid_loop' ) ) {
genesis_grid_loop( array(
'features' => 0,
'feature_image_size' => 0,
'feature_image_class' => 'alignright post-image',
'feature_content_limit' => 0,
'grid_image_size'        => 'thumbnail',
'grid_image_class'        => 'alignleft',
'grid_content_limit' => 250,
'more' => __( '[Read more...]', 'genesis' ),
'posts_per_page' => 58,
/** Do not categories in main loop */
'category__not_in' => array(2258, 2806, 2695, 2654, 2767)
) );
} else {
genesis_standard_loop();
}
}

How would I change that code now that the Genesis Grid Loop does not work anymore?

I don't want to show categories 2258, 2806, 2695, 2654, 2767 in the main loop.

BTW the 'posts_per_page' => xx does not work anymore either. This is another big issue for me since before I could have a certain number of posts in 'loop view', and a different number of posts in blog/archive view (as per Settings>Reading). Now everything is controlled by Settings>Reading.

Because of these two reasons alone I have dozens of sites screwed up, please help asap thanks.

[michaelbuster]

Thanks but I can't have a site without title and tagline under General Settings obviously, I'd rather have the bug fixed with some code.

[michaelbuster]

Nothing has changed?? at http://www.studiopress.community  first thing it says is " Responses in this forum are not guaranteed. ", which is kind of a weird/worrying statement for a "support forum". In addition, the Design Tips category is not even subdivided by theme for easy browsing - don't you see posters already have to write the theme child name in the post title. Can you imagine, 'Sidebar wider in Going Green', 'Sidebar wider in News', 'Sidebar wider in Agency'.... bit funny really.

[michaelbuster]

Okay imagine a very common question, like 'I want the Going Green sidebar wider'.

PAST:
I would go to the forum, search or browse the Going Green thread and very likely find an answer. Or if not, I would post the question and get the answer within minutes either by you guys or some gentle soul. No waste of time.

NOW:
Go to the old forum and very likely not find the answer since the old forum will get obsolete. Waste of time.
I would then go open a ticket and wait up to 24 hours. Waste of time (and money of course since I do design this for a living).
I would then get a reply and maybe it's not clear, so I have to answer back and wait some more, waste of time.
Maybe I should have posted on the old forum? I can't because it's ready only. Should I post on this forum then, no because this is not a technical forum and it says questions will not be replied (what kind of forum is this, I don't know. For 'suggestions'?).

Unless I am missing something this is how it is: an old read only forum, an useless forum, and a ticket system (wait there's even a fourth place called mystudiopress just to download a theme! Studiopress now takes 4 bookmarks in my browser).

I consider myself fortunate since I've been with Genesis for a long time so I rarely need help, but I can only imagine how awkward this can be for newbies. I can only suggest to reconsider this change.

[michaelbuster]

maybe if everybody keeps complaining they will go back as it was! Imagine the themes they could have designed with all the time wasted on this switch.

 

[michaelbuster]

I had to register from scratch for my.studiopress.com only to find out it's a ticket system. Then I went to the forum and it says 'Read only'. I  had to register again to access the (new) forum here, where there's only a bunch of (generic, not theme specific) posts and it says 'response is not guaranteed' (!) -- why would I post on such a forum.

I was used to find my answers instantly simply browsing the support forum or doing a search, and learning from others. Occasionally I would make a question in the same forum; now apparently I am forced to open a ticket, and others won't learn from the answer.

Unless I am missing something, I am literally speechless from this change (like others apparently), which also means much more work for you answering to tons of questions that won't be published. What's the point of all this??

[Author]

Posts