Forum Replies Created
-
AuthorPosts
-
April 14, 2013 at 1:10 pm in reply to: Primary and secondary sidebars not aligning when adding another widget area #35437Gary JonesMember
The background is added via an image, so you'll need a new (larger size) image, and apply it to either #text-15 h4 {} or #sidebar h4:first {}
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberDisable all plugins, then open a private browser session, head to your protected post and try an incorrect, then correct password. Does it still redirect to a 404?
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberDisable all plugins, and check through your functions.php file for anything that looks like it it could be amending something to do with the password form.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberAround line 1983, you'll see the normal font color of #888 - change this to whatever font colour you want on top of the red menu.
Around line 2019, you'll see a background-color: #fff - change this to be the hover colour that replaces the red.
Just after line 1990, you'll see a color: #484848 - change that to whatever font colour you want when hovering.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
April 14, 2013 at 8:21 am in reply to: Primary and secondary sidebars not aligning when adding another widget area #35389Gary JonesMemberYou mean the Egg Money background bit?
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberYes - that would be the best way of doing it 🙂
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
April 14, 2013 at 7:09 am in reply to: Displaying single post pages differently in specific categories #35380Gary JonesMemberPretty close!
Try:
add_filter( 'body_classes', 'bms_add_about_cat_class' ); function bms_add_about_cat_class( $classes ) { if ( is_single() && is_category( 'about' ) ) $classes[] = 'category-about'; return $classes; }
Then keep the same CSS as before.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberAppearing fine for me in IE7/8/9 standards views in IE9.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberOdd. Looking fine on Chrome 27-beta.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberYou've read that wrong. Password protected pages work fine - unless you customise them in some way (with the_password_form) filter.
Your example post protected doesn't look any different to the standard, so you probably don't need any custom form, if you are already doing it. I can't see anything (quick look) in the AgentPress 2.* code that suggests the default is to override that part of WP functionality, so it's either a customization, or a plugin.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberA Google search for "meta viewport" will bring up millions of results.
http://webdesign.tutsplus.com/tutorials/htmlcss-tutorials/quick-tip-dont-forget-the-viewport-meta-tag/
https://developer.mozilla.org/en-US/docs/Mobile/Viewport_meta_tag
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberAdd a priority to the second add_action() call, to make the function happen earlier than the function that adds the sidebars.
add_action( ‘genesis_after_content’, ‘end_conent_wrap’, 5 );
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberI can reproduce the jump.
Try disabling Jetpack and / or other plugins, or whatever is adding in your typekit script.
As far as I can tell, it's not something inherent with Genesis or a child theme.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberTags are free form, and as such, going to be fairly useless in a forum like this. I can guarantee, for instance, that your tagging of "Studiopress rocks" is not something that's going to be used as a search term to solve someone's problem. Someone people won't read the sticky you suggest (most don't read the forum rules that say about including their site URL in a help request!), some will but might forget, apathy sets in, or they try but do it wrong.
Since the list of themes is an enumerated list then an optional dropdown containing a list of all themes when creating a new thread would be more beneficial.
Equally a list of other topic areas (Nav, scripts, plugin compatibility, design customization, and so on) would be a different fixed list taxonomy to which threads could be assigned, without the need to have posts moved to different forums.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberAs you've got the Gray style selector in use, then changing the standard colour won't work, as it gets overridden in the .focus-gray section towards the bottom of the style.css, around line 1976:
.focus-gray .menu, .focus-gray #header .menu li a:active, .focus-gray #header .menu li a:hover, .focus-gray .wp-caption { background-color: #f3f3f3; }
#f3f3f3 corresponds to the grey you are seeing, so change it to whatever red hex colour code you want.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberPlease read and find a solution at http://remkusdevries.com/maintain-translation-upgrade/
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberYes, you should do the update. No you should not ignore.
You should always apply any WordPress, Genesis or plugin update - it's been updated for a reason.
The change from 1.9.1 to 1.9.2 is barely 10 lines of code once the usual upgrade code changes that happen for all releases is discounted.
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberPlugins get set up by WP before themes do, so at the moment your plugin runs and the class gets parsed, none of the Genesis_Admin_* classes exist.
What you need to do is to put your class into a different file, then wrap a function around the require() call, which is hooked into genesis_admin_init. You'll see that hook fires at the end of genesis/lib/classes/admin.php.
// my-plugin/class-uvasomnavbar.php class UVASOMNAVBAR_Settings extends Genesis_Admin_Boxes { ... }
// my-plugin/my-plugin.php add_action( 'genesis_admin_init', 'myplugin_admin_init' ); /** * Include admin class, now Genesis admin classes exist, then instantiate it. */ function myplugin_admin_init() { require( 'path/to/class-uvasomnavbar.php' ); new UVASOMNAVBAR_Settings(); }
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberThis thread is marked as resolved - did you find a solution?
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
Gary JonesMemberWhen you hook something in
add_action('foo', 'bar');
...you can add a third parameter for a priority, so when two functions are on the same hook, WP knows which to process first. Default value is 10 (including when no priority is given, as above), so if you want to add something in earlier, then choose a lower number (5 is good).
WordPress Engineer, and key contributor the Genesis Framework | @GaryJ
-
AuthorPosts