Forum Replies Created
-
AuthorPosts
-
February 28, 2022 at 11:39 pm in reply to: Genesis framework bug in WP 5.9.1 a bazillion . wp-containe #504769carasmoParticipant
//Fixes 5.9.1 bug in Genesis
remove_filter( 'render_block', 'wp_render_layout_support_flag', 10, 2 );
Please fix this in Genesis core. Thanks!
carasmoParticipantThis is due to the matchHeight jquery plugin. The default is set to height, so when a height is changed via another script, then it will have the overlap since a resize is not being triggered.
*Open the global.js file in a code editor. Add the option for property as per the instructions on MatchHeight https://github.com/liabru/jquery-match-height
Before:
jQuery(document).ready(function($) { // Match height for content and sidebar $( '.content, .sidebar' ).matchHeight(); });
After changing to min-height.
jQuery(document).ready(function($) { // Match height for content and sidebar // changed to min-height. $( '.content, .sidebar' ).matchHeight( { property: 'min-height' } ); } );
Next open up your functions file in a code editor and find the constant
CHILD_THEME_VERSION
change the version of the theme toBefore
define( 'CHILD_THEME_VERSION', '1.0.0' );
After
define( 'CHILD_THEME_VERSION', '1.0.1' );
The last part is to clear the cache. When you make changes to CSS or js, you should bump the version number so that the browser will dump the stored files.
*Assumes FTP and code editor. Attempting to edit php and jquery files by other means is risky.
carasmoParticipantVersion of Genesis is 2.5.3?
Turn off all plugins too.
Contact the official support. This is the volunteer forum.
October 27, 2017 at 10:17 am in reply to: Gallery Pro Widgets show up in Chrome but not Safari or Firefox #213025carasmoParticipantNo the button does not show up in any browser and there is nothing in the source code with those words except for a menu item.
Go in to your Widgets, is it there? Make sure and save.
Clear your server cache and your browser cache.
carasmoParticipantYou have the incorrect property width in your
max-width: 1180px
media query. Allwidth: xxx
should be changed tomax-width
. You also have incorrect property:backgroundcolor
, should bebackground-color
. Use a good code editor and you'll see that error.This fixes the home page un-responsiveness and the horizontal scroll bars.
Replace your
@media only screen and (max-width: 1180px) {
declaration block to the following:@media only screen and (max-width: 1180px) { .site-inner, .wrap { max-width: 960px; } .title-area { max-width: 380px; } .site-header .widget-area { max-width: 570px; } .content-sidebar-sidebar .content-sidebar-wrap, .sidebar-content-sidebar .content-sidebar-wrap, .sidebar-sidebar-content .content-sidebar-wrap { max-width: 780px; } .home .content { max-width: 1140px; } .content { max-width: 630px; } .content-sidebar-sidebar .content, .sidebar-content-sidebar .content, .sidebar-sidebar-content .content { max-width: 450px; } .footer-widgets-1, .footer-widgets-2, .footer-widgets-3, .home-middle .featured-content .entry, .sidebar-primary { max-width: 300px; } .sidebar-secondary { max-width: 150px; } }
carasmoParticipantcarasmoParticipantcarasmoParticipantBill's post works fine on single posts, but on CPTs, since they are created on init, you'd run it earlier, this is what I would do.
//* first use a conditional to affect your cpt function your_prefix_remove_title_from_your_single_cpt_crumb( $crumb, $args ) { if ( is_singular( 'my-cpt-slug' ) ) : return substr( $crumb, 0, strrpos( $crumb, $args['sep'] ) ); endif; } add_action( 'after_setup_theme', 'your_prefix_run_filter_to_remove_your_single_cpt_title' ); //* Run genesis_single_crumb earlier on the after_setup_theme hook function your_prefix_run_filter_to_remove_your_single_cpt_title() { add_filter( 'genesis_single_crumb', 'your_prefix_remove_title_from_your_single_cpt_crumb', 10, 2 ); }
carasmoParticipantYou would just paste this additional CSS panel. They are specific to that front-page area, not site wide.
carasmoParticipant.nav-primary
doesn't not have a width set in the site you linked to. Use width: 100% on that property.
carasmoParticipant/* -- default state front-page 1 button */ .front-page-1 .button { background: #ffe303; color: #222; } .front-page-1 .button:before { border-bottom-color: #ffe303; } .front-page-1 .button:after { border-top-color: #ffe303; } /* -- hover/focus state front-page 1 button */ .front-page-1 .button:hover, .front-page-1 .button:focus { background: #222; color: #fff; } .front-page-1 .button:hover:before, .front-page-1 .button:focus:before { border-bottom-color: #222; } .front-page-1 .button:hover:after, .front-page-1 .button:focus:after { border-top-color: #222; }
carasmoParticipantGeesh this forum has a hard time with images:
Link to image:
Use the additional css in the customizer:
/* -- default state front-page 1 button */
.front-page-1 .button {
background: #ffe303;
color: #222;
}.front-page-1 .button:before {
border-bottom-color: #ffe303;
}.front-page-1 .button:after {
border-top-color: #ffe303;
}/* -- hover/focus state front-page 1 button */
.front-page-1 .button:hover,
.front-page-1 .button:focus {
background: #222;
color: #fff;
}.front-page-1 .button:hover:before,
.front-page-1 .button:focus:before {
border-bottom-color: #222;
}.front-page-1 .button:hover:after,
.front-page-1 .button:focus:after {
border-top-color: #222;
}
carasmoParticipant<img src="https://christinacreativedesign.com/studiopressforum/Screen%20Shot%202017-10-26%20at%203.54.37%20PM.png
" alt=" " />
October 26, 2017 at 11:13 am in reply to: Working On A Live Website Offline Until Ready To Launch New Layout #212974carasmoParticipantYou would google for local WordPress development. I use Local by FlyWheel (for Flywheel hosted sites but you can -- if you know what you're doing -- use it for other hosting situations). and/or Desktop Server. I suggest taking a course on WordPress development, learning FTP, getting a good code editor:
https://www.lynda.com/WordPress-tutorials/
https://teamtreehouse.com/library/topic:wordpress
This link is for their LAMP server (a typical setup), it assumes you have cPanel, and subdomains on your hosting account, and other knowledge (probably PhpMyAdmin):
https://www.greengeeks.com/tutorials/article/how-to-clone-a-wordpress-site-and-when-you-should/
carasmoParticipantYour issue is not the same so the code will not work. You would need to write jQuery to close the menu when the search icon is clicked. Open up another thread and see if a volunteer here will help you. You will need to link to your site.
October 25, 2017 at 2:21 pm in reply to: Outreach Pro – :focus outline not working in Safari #212948carasmoParticipantOctober 25, 2017 at 1:34 pm in reply to: Outreach Pro – :focus outline not working in Safari #212946carasmoParticipantI'm viewing your (http://www1.sunybroome.edu/) and Safari 11 on Mac and the outlines are there but not seen very easily when it's not the first or the last one. Using a negative offset would probably fix this.
Screen Shots
https://christinacreativedesign.com/studiopressforum/Screen%20Shot%202017-10-25%20at%203.32.54%20PM.png
October 25, 2017 at 10:58 am in reply to: Outreach Pro – :focus outline not working in Safari #212942carasmoParticipantSince it's not an accessible theme, the menu js is old and doesn't have the accessible stuff in it, since the newer themes open the drop menus with tabbing (see Monochrome Pro -- I bought the dev package -- for an example).
However, it looks like the outline is there but the menu items are covering it. So would make a negative offset:
outline-offset: -2px;
However, that theme is missing more than CSS to make it accessible, skip links and the js for the menu and the CSS for the menu is missing code.
carasmoParticipantThis should be a question for StudioPress support as this is an oversight in their js.
Anyway, this is untested but should work.
First you have to change the js to use the unminified version then re-minify or pack it afterwards.
Using FTP and a code editor, open up responsive-menus.js (not the min version), at the very bottom find:
$(document).ready(function () { if ( _getAllMenusArray() !== null ) { genesisMenu.init(); } });
Change that to add the function to close the menu:
$(document).ready(function() { if (_getAllMenusArray() !== null) { genesisMenu.init(); //* Close Menu Panel when a link that is an anchor is clicked but not just a # $('.genesis-responsive-menu ul li a[href*=#]:not([href=#])').on('click', function() { var $toggle = $('.menu-toggle'); $toggle.next('nav').slideUp(); $toggle.attr('aria-expanded', 'false'); $toggle.attr('aria-pressed', 'false'); $toggle.removeClass('activated'); }); } });
After this chunk make sure you have kept the
})( document, jQuery );
Now stick that on your server in the correct location in your theme with FTP and open up the php in a code editor (probably functions.php) where they are enqueueing the scripts and find the words
responsive-menus.min.js
and change that to theresponsive-menus.js
. Clear all local and server cache.Test. If it works, then re-minify the script (online you can use http://refresh-sf.com/) and replace the code inside responsive-menus.min.js and then change the php back.
In order to this properly, use the proper tools.
Backup first all the files so you can swap back if you create an error.
October 25, 2017 at 9:29 am in reply to: Outreach Pro – :focus outline not working in Safari #212936carasmoParticipantOutreach Pro is not under the accessible-ready themes.
I add a focus to my CSS, then on areas that have dark backgrounds, I change the outline color:
:focus { color: #000; outline: #777 dotted 1px; /* works on light backgrounds */ outline-offset: 2px; } /* example for dark background */ .nav-secondary :focus { outline: #fff dotted 1px; }
-
AuthorPosts