Forum Replies Created
-
AuthorPosts
-
May 17, 2014 at 7:31 am in reply to: Modern Portfolio Pro – featured posts in blog widget on home page #105619RobinMember
In your stylesheet, line 1270 looks like:
.mpp-home .content .featuredpost .entry:nth-of-type(3n+1) { clear: left; }
This is telling it to put the fourth testimonial on a new line, no matter what--basically it's set up to expect the testimonials in rows of three.
Not sure where the width of your testimonials is being set, because I don't see that anywhere, so I think that's another issue preventing your testimonials from being the right width to make rows of three. So if you set a width for these guys, the block of CSS is ok for two rows of three. (Try playing with widths in Firebug for Firefox or Chrome's Developer Tools). HTH
I do the best I can with what I’ve got. (say hey on twitter)
May 17, 2014 at 6:57 am in reply to: Parallax Pro theme home page images not resizing responsively on phone #105617RobinMemberI would look at the CSS starting at line 1782 in your stylesheet, and see about copying that to a lower size media query, maybe the 768 section. In that spot, the background-size is set to auto. If you change it to contain, the images won't go beyond the width of the phone/device.
Note: You'll need to do some figuring out about how to handle the text, since the color below the images is white and the text is white, and since the background image will suddenly be much smaller, you have a lot of white on white. But the images will be smaller.
HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberGlad the tutorial was useful for you! I'm not 100% clear on what you're asking, but I think the easiest way to not show content on the second blog page would be to not put any into the page. If you leave it blank, it will still show the posts.
Does that help?
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberThe .site-header styling starts at line 860 in your style.css, it looks like. Remove the line that says
position: fixed;
and you should be set. You can experiment with it using Firebug or Chrome's Developer Tools first. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberIf you have the font on your computer, it will work. If the font isn't installed on your computer, it won't, unless the font is being served up from somewhere else. So I'll guess that the work computer doesn't have Museo 700 installed on it.
The instructions assume that you're putting the js file in the root folder of your site, and then the fonts folder goes from there. Actually, since the fonts are in your theme folder, you'll need your path to be something more like /wp-content/themes/your-theme/fonts/, or else the js will need to start out looking there.
I do a lot of this by trial and error myself, so that is all I can suggest. Maybe start out with the custom path commented, so it's not a factor, and work on making sure that the js is found. If the js is found but the fonts aren't, you'll still have an error but you'll be one step closer. So I'd comment out the var customPath line, and change the src for the js to /wp-content/themes/bluegrass-digital-media/fonts/museo.js ... you may want to try it with and without the opening / ... I feel like in some places, it works to have it there, some places, not so much.
Sorry this is being so convoluted. The nice thing about error messages is at least they help point out where things are going wrong. 😉
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberGreat on Google!
OK, on Museo, I'm guessing here because I haven't done it this way, but in the last line
<script type="text/javascript" src="museo-700.js"></script>
the source should maybe be changed to /fonts/museo-700.js since that's where your js file is. Try that and see if it helps. I'm guessing that you would need to recomment the var customPath line, because the js may be using a relative path, and without commenting it, it may look in /fonts/fonts, which isn't what you want.Not sure which browser you are using, but Firebug (Firefox) and Chrome Developer Tools will tell you if they can't find things and will tell you where they are looking. If you hit F12 in Chrome, it will show the panel and if there is a red circle, something is broken--click that and it will tell you where. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberI think something isn't quite right with your Google fonts. On I site I did, mine looks like this:
wp_enqueue_style( 'google-fonts', '//fonts.googleapis.com/css?family=Open+Sans:300,400italic,700italic,400,700', array(), PARENT_THEME_VERSION ); // Google Fonts
It looks like you're missing the first parameter, the handle, which is required.
The script itself may be looking in the /fonts folder but the Chome Dev Tools can't find the museo-700.js to begin with--how are you calling that?
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberLook at the Blissful functions.php file. Lines 18-21 unregister all of the three column settings. To enable them, you need to comment out or remove those lines. The theme may not include any styling for those layouts (I haven't used it so I do not know), so you may have to work that out as well. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberHow are you loading the fonts on your website? I do not see the Google fonts being called in your source code at all. The Museo appears to be looking for a .js at http://demo.bluegrassdigitalmedia.com/museo-700.js and that's showing a 404, which is why Museo isn't loading.
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberI had a similar thing I needed to do where I needed post B to have a custom field with meta from post A. To set it up correctly, I had one function which was hooked to both save_post and publish_post. I forget the full reasoning behind it but my research determined that they are two separate events, and to make sure I was covered whether the post was being saved, updated, or published, I needed both. My code is here if it helps you at all.
Also if you are using the Custom Metabox/Field plugin, those are usually prefixed with an underscore, eg. _cmb_from_textdate_unix, so if you have underscores in one place but not the other, that may be part of the issue. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberFor the one under the header, this should work:
ul.menu-secondary { text-align: center; }
If you want them both centered, add
text-align: center;
to the .genesis-nav-menu block at line 416 of your style.css. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberIf you uncomment the lines you commented and change it to:
if( is_page_template( 'page_landing.php' ) ) {
then on any page using that template (assuming it's named the same as what's in the folder on my computer) won't display the widget area. (source: Codex Conditional Tags)
HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberIt's a plugin you're using--the folder is google-maps-ready. Would assume that the plugin name is something similar. It has a line of styling that looks like this:
.wrap, #dashboard-widgets .meta-box-sortables, .ui-buttonset {margin:0 !important;}
The .wrap is affecting all of your wraps, including the one for the .site-inner, which is set for
margin: 0 auto;
.... not sure why the plugin developer would do something like that. You could disable the plugin and look for something else, or you could add !important to your theme's .wrap styling and see if that will override it.HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberIn the second block of style you posted, remove the background line, change the list-style-type to disc or square or whatever you want, remove the margin line, and change the padding line to be the margin. (You can test it before you commit by using Firebug in Firefox or Chrome's Developer Tools.)
HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberIt's your margin in this block starting at line 1115 in your style.css:
.content .post, .content .entry { background: transparent; border-top: 0px solid #DDDDDD; border-bottom: 0px solid #DDDDDD; border-left: 0px solid #DDDDDD; border-right: 0px solid #DDDDDD; margin: 0px 0 40px; padding: 0px 10px 0px 0px; }
If you set the margin to 0, it pulls it up. This will affect the margin under the .content everywhere in your site, so if you're only wanting to change the home page, you might need to do a new rule starting with .home. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberSince your theme is an HTML5 theme, the genesis_after_post_content hook doesn't exist. You need to either use genesis_entry_content with a large number so it loads after your content, or use genesis_entry_footer with a small number. (source: Visual Hook Guide)
Great link, Brad--thanks for sharing it!
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberYes, you should be able to use a hook for it. If I'm not sure about a hook, this Genesis Visual Hooks guide is pretty awesome. I'd guess you just want genesis_entry_content, but you may have to add a priority number to your action to make sure it runs before the content itself does. A lower number gets run before a higher number.
HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberShelli, you can try this solution which a friend put together for me a few years ago. Add it to your functions file (make a backup first). Since it's working with an RSS feed, you probably won't be able to see the changes until cache is cleared or a new post is posted. You might want to delete the thumbnail lines (I was posting galleries and didn't want the thumbs going to the feed) and just use the very last line, replacing 700 with 1024. I made as many comments as I could.
I used it for years, tweaking sizes when I changed my process or theme, and it never failed me. HTH
I do the best I can with what I’ve got. (say hey on twitter)
RobinMemberEven though the date is below the image, it's in the header. Also, in the new HTML5 themes, I think you need to use genesis_post_info instead. Check this snippet and see if it helps instead. Good luck!
I do the best I can with what I’ve got. (say hey on twitter)
January 12, 2014 at 10:13 am in reply to: Adding a Background Image to a Container in the Focus Theme #84773RobinMemberTo add a background to just the content area, you'd want to use #content. To make it specific to that page, try:
.page-id-13 #content { background: #ddd; }
That color is probably not what you had in mind but hopefully it will get you started. HTH
I do the best I can with what I’ve got. (say hey on twitter)
-
AuthorPosts