Forum Replies Created
-
Posts
-
We plan to tackle this issue by writing guides for updating some of the older StudioPress themes on our blog at http://genesisupdate.com
We haven't had a chance to publish anything yet because we've been updating sites all day, but we'll have something up by next week for sure! 🙂
It was part of the updates in the final version of 2.0. I'm pretty sure the changes they made were to ensure that sections that were merged into one hook would still be hooked in the same order that they were in the XHTML version.
Gary Jones has a book that outlines all the changes in the latest version. If you're interested in learning more, you can check it out here: http://gamajo.com/changes
Are you sure you've activated HTML5 correctly? Make sure you add
add_theme_support( 'html5' );to your functions.php file. If you're sure HTML5 has been activated correctly, try this:
//* Remove the entry meta in the entry header (requires HTML5 theme support) remove_action( 'genesis_entry_header', 'genesis_post_info', 12 );
If anyone is running an older theme that they'd like updated to 2.0, just let us know. We can't sell HTML5 versions of SP themes because it wouldn't be fair to StudioPress, but we'll gladly update your theme for you.
We'll probably also be publishing some tutorials for each of the older themes for anyone who would like to tackle it themselves. 🙂
Bill Erickson posted a nice list of the changes from RC2 and 2.0. You can check it out here: http://www.diffchecker.com/k1j3cwz7
Basically you just need to check your theme for the items in red and make sure they are updated to the items in green.
I guess it would probably make more sense to run through that first set with a foreach loop.
Something like this:
https://gist.github.com/fatmedia/26faf43ea62f5153c6be
I'm not totally sure if I'm setting that up right though, there's a good chance that won't work and I'm not in front of my main dev machine so I can't really test it. Gary, can you escape the data that way? Did I screw anything else up on that?
It looks like there's an unclosed div tag in there. It's causing the second div to render inside the first.
I updated my code based on Gary's suggestions. I'm pretty sure this is what he meant:
https://gist.github.com/fatmedia/6005802
Again, that hasn't been tested so I'm not sure if it will work. I also escaped the data for you. Let me know if that does the trick. You probably don't even need the spans in there, but I dropped them in in case you need them for styling.
Angie,
You can use column classes for this so you don't need to write any extra CSS for the columns themselves. You should probably run a check to make sure you're not outputting empty divs when there isn't any data. Something like this should work:
https://gist.github.com/fatmedia/6005802
I haven't tested that, but it should work. I can't remember if ACF automatically sanitizes the output when you use get_field but it's generally good practice to use esc_attr() when echoing out the data. You probably also don't need so many divs in there unless you're planning on styling each line individually, in which case you could use a <span> for some of them.
There's really no need to delete all that code. Since you're not that familiar with PHP, deleting the code will probably make it difficult for you to restore the original functionality of the theme if you change your mind.
In order to prevent the widget area from loading, all you need to do is comment out the action which loads the widgeted areas. You can do that by adding two forward slashes in front of it like this:
// add_action( 'genesis_after_header', 'minimum_home_featured', 15 );Doing this will prevent the mimimum_home_featured area from loading. If you change your mind later it'll be very easy for you to go back and turn it back on. All you'll need to do is delete the slashes and you'll be back in business.
I'd be a little concerned about that one. It's hard to say without seeing the back-end code but it looks pretty screwed up on the front end. Not only is he loading his own version of jQuery, which is a pretty bad idea all by itself... He's not even dequeueing the version in WordPress core.
You'd probably be better off sticking with themes that have been endorsed by StudioPress or at least using ones that are built by developers who have a reputation for quality.
My general opinion on dropdowns is that they are shit. They are shit for a lot of reasons, one of which is that they're not ideal for SEO*.
People severely underestimate the value of siloing their site. Think about it like this:
Google wants relevancy in everything that you do. Is it relevant to have a link to damn near every page of your site on every page of your site? If you have a section on your site about cars, why would you link to it from the section of your site about dogs? I'm not sure why you'd have a site with sections about dogs and cars, but you get the idea.
Dropdowns also water down your linkjuice. If you've got 10 menu items plus 5 or 6 dropdowns for each you've got 60-70 links on every single page before you even get into your content. That's not good.
Here's a pretty good guide on how to create a siloed website: http://scratch99.com/wordpress/wp-seo/siloing/
*I'm sure plenty of people will disagree with me on this. That's fine. My opinion is based on my own testing/experience as well as data that's been published all over the web. If you think dropdowns are great for SEO, awesome. Keep using them.
The short answer to this is yes. You could definitely do that. Bill Erickson outlines how to create a better, easier grid loop using column classes in this post:Â http://www.billerickson.net/a-better-and-easier-grid-loop/
What you're talking about is similar to what he's doing there. If the content that you wanted to include was static, it would be even easier to include. You'd just need to set up some conditional statements to include your content on the pages/sections that you wanted.
If you need some help figuring it out, let me know and I'll give you a hand.
The procedure will be little different depending on how you are gathering the info. I can probably write up a tutorial for both GravityForms and Genesis E-News Extended and post it to my blog if that would help. I'll try to get to it this weekend.
Shan,
If you like you can send me a message through this form. Send your Skype name and I'll add you to help diagnose the rest of your issues. http://youneedfat.com/contact/
eightcrazy - I'm not sure if this is what you mean or not but if you're talking about the menu breaking as the site scales, a quick fix would be to do something like this:
https://gist.github.com/fatmedia/5131359
Alright, I think I've caught the majority of the problems and put them here:
https://gist.github.com/fatmedia/5131287
You can click the revisions link to see what I changed.
There's definitely still some issues with your CSS. I also may have missed some stuff when copying the styles over. It's difficult to do without being able to refresh to check, but this should at least get you started.
If you still have trouble, I'd be happy to give you a hand cleaning the rest of it up if you can provide me with access.
Shan,
You've got some major issues with your CSS on this. I can fix it, but it would be difficult to go through all the changes one-by-one.
Would you feel comfortable giving me access to your site temporarily?
The reason this is happening is because #wrap has a background color of #fff.
The easiest way to fix this is to add the following to your functions.php file:
/** Move #header outside of #wrap */
remove_action( 'genesis_header', 'genesis_do_header' );
add_action( 'genesis_before', 'genesis_do_header' );You may have to add some CSS rules for your header once you do that because it will no longer be constrained by the #wrap element.
