- This topic has 15 replies, 10 voices, and was last updated 8 years, 9 months ago by
.
-
Posts
-
I'm relatively new to Genesis but is this type of issue -- something in the Parent Theme affecting settings so important on a child theme -- does it happen upon updates often? I can imagine all the auto update sites that are displaying with the unintended layout(s). Really horrible.
I'm wondering if I should not have auto updates selected on my client's sites and then, whenever the service agreement is arranged, update then.
You're right. It is horrible.
Even worse is that paying members are not notified via email about upcoming updates, update issues, and update solutions. At the very least, you would think that they would diligently convey this information via the StudioPress blog.
Apparently, we're supposed to fumble around on Facebook looking for the GenesisWP group, request to become a member, then wait for Nathan Rice to provide a short-term fix that will soon be replaced by another update.
Ugh.
Yes, or via Twitter. I was lucky to see it on Facebook but I tend to subscribe to stuff I'm trying to keep ahead of and that is a lot of time out of the day. Since I already had the ftp open on a couple sites, the fix was very quick, but doing that over and over again until an unknown time when the patch will be released is time consuming. People count on their site for marketing google ads and offline endeavors which they don't tell me about necessarily, "Hey, make sure my site is working on such and such day in particular." It's just supposed to stay as it was intended in the first place.
Anyway, I've heard far worse stories from non-Genesis theme's out there and seriously crappy code too, so in spite of this, we are lucky it's easily fixed.
The latest Genesis upgrade caused the following problem.
No longer am I able to control the Select Default Layout format for individual blog posts. Within Genesis, I can select 100% content or a combination of content and sidebar. If I select 100% content, all my blog posts show 100% content. If I select ~75% content and ~25% sidebar, all blog posts follow this structure. It is all or none and individual blog control is gone - kaput.
Prior to the upgrade, I was able to control the content/sidebar relationship from blog post to blog post.
Anyone else having this problem. My Genesis Theme is the Minimum Pro Theme.
Physlab
@physlab I'm having the exact same problem after the update! So frustrating!
I just received info on Twitter that a fix is coming tomorrow:
Is anyone having issues with Genesis 2.2.4 and page layouts? I can't get override settings to work by page! #genesiswp
— Cami MacNamara (@WebCami) December 17, 2015
@webcami Thanks for the update I hope everything goes well with this fix.
In the meantime, this worked for me.
Advice from StudioPress’s Facebook page…
If you’re having the layout issue with 2.2.4, change the following line in lib/functions/layout.php (line 343) to this:
$post_id = is_home() ? get_option( ‘page_for_posts’ ) : null;
In all the years I've been using Gen, it has never broken one of my sites... until now.
It's been about 8 hours since the problem was reported here so I'm kind of surprised that the SP folks have not fixed it and put out an update yet.
I see the fix above, but I don't like editing WP core files.
Just in case a Gen fix does not come around soon, how do you roll back to the previous Gen version... or can you?
You can solve this problem via your functions file using conditional layouts.
Hi carasmo,
I've been using Genesis for well over 2 years now and this update is the first that breaks something this major. So no it is not habitual in their case.
I have many clients in paid maintenance so I'm more sensitive than many on this and this is a big reason I've stuck with Genesis and will continue to do so. It has been very stable for us so far aside from the 2.2.4 layouts breakage which will apparently be fixed very quickly.
But regardless of this update issue for Genesis 2.2.4, I really think autoupdates of everything is an absolutely terrible idea. It looks good on paper and I understand the security concerns, but auto-updating everything is asking for trouble, trouble that many users are not equiped to deal with. I find that autoupdate everything philosophy very naive...
In our case, it also simple is not possible to have everything autoupdate as, a lot of the times, updating requires also updating translations we maintain separately (the vast majority of our sites are bilingual). Also, larger plugins often break things. From template overrides needing to be updated to changes in functionality as well as bugs introduced with early new major versions (yes, looking at you Yoast...), so we've always used a prudent approach to updates and take the time to evaluate them. The past history of the component being updated is also an important factor.
I leave the WP core autoupdate on for minor versions, but if they ever forced autoupdate for all WP versions, I'd deactive it right away. I don't want anything else to autoupdate. I really do not need the headache.
I wouldn't want to be a new WordPress user nowadays. The community is really sending mixed messages. Between the (very good) advice to test every big change to sites on staging or local servers and this recent push to update everything right away, I'd be very confused. Few updates are truly that time sensitive and critical. For example, it's not like WP 4.3.1 is suddenly a huge security risk now that 4.4 has been out a week or so. Same for most plugin or theme updates unless the update is one adressing a newly discovered and serious security issue.
I much prefer to test first and see if any issue come up immediately following a major update of any WordPress site component. That's what our clients pay us for.
My 0.02$
Sorry but can't access or see private messages so cannot respond. Use [email protected]
Because I have a 'sensitive' client who depends on the website for their living and who was not happy with the breakage I applied the fix to the Gen 'core' file as posted above.
Worked great.
(My fault, I should have waited a few days before I did the update but I was 'in' the site's admin area to do something else and figured "Never had a problem with Gen before so 'go for it.'" )
What surprises me is that there has been no communication out of SP on their website or this board or anywhere else that I know of. These are the people who 'teach' good marketing and communication as one of their enterprises (Rainmaker?)
I got a chuckle out of reading Brian's Ask Me Anything piece yesterday where he said "As you know, Genesis is rock solid...."
I don't understand why there is no word... not even a tweet... out of SP.
2.2.5 is out!
Genesis 2.2.5 is out and addresses issues we were having #genesiswp https://t.co/z5iXdWBsxp
— Cami MacNamara (@WebCami) December 17, 2015
- The topic ‘2.2.4 Update and the layout problem’ is closed to new replies.