Forum Replies Created

Viewing 15 replies - 106 through 120 (of 1,249 total)
  • Plugin Contributor Nick C

    (@modernnerd)

    You can update the name labels to alter the breadcrumb name and browser tab title. Add these alongside your other args changes:

    $args['labels']['name']          = _x( 'Projects', 'taxonomy general name', 'genesis-portfolio-pro' );
    $args['labels']['singular_name'] = _x( 'Project', 'taxonomy singular name', 'genesis-portfolio-pro' );
    $args['labels']['menu_name']     = _x( 'Projects', 'taxonomy menu name', 'genesis-portfolio-pro' );
    

    The properties you can override for the portfolio type and taxonomy are visible here.

    • This reply was modified 7 years, 5 months ago by Nick C.
    Plugin Contributor Nick C

    (@modernnerd)

    @tbebicom No timeline on this yet, but I added a note with your vote for the feature at https://github.com/copyblogger/genesis-simple-faq/issues/46.

    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @bozzmedia.

    Thanks for this report.

    I cannot reproduce this so far either. I see the magnifying glass button with Genesis Sample and Genesis Connect active:

    Screenshot showing WooCommerce magnifying glass button on a product thumbnail

    There are a few things to check:

    1. Try disabling all other plugins temporarily except for Genesis Connect and WooCommerce.

    2. Review your browser’s JavaScript console for errors. (Broken JavaScript can prevent that magnifying glass button from showing.) https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    3. If you’re using custom WooCommerce template files in your child theme, try removing or renaming them temporarily.

    Plugin Contributor Nick C

    (@modernnerd)

    Great, thanks for the update, @jenxi!

    Plugin Contributor Nick C

    (@modernnerd)

    Thanks for the link, @jenxi — that’s been a big help!

    To match the homepage widget styling for the Breakthrough Pro theme, you can try this code instead of anything you’ve added already (it’s the same as above except for the first add_action line):

    add_action( 'genesis_before_while', 'sp_amend_portfolio_archive' );
    /**
     * Add the portfolio post type links under the portfolio title.
     */
    function sp_amend_portfolio_archive() {
    	if ( is_post_type_archive( 'portfolio' ) ) {
    		add_action( 'genesis_after_entry_content', 'sp_add_type_to_portfolio', 9 );
    	}
    }
    
    /**
     * Output portfolio post type links.
     */
    function sp_add_type_to_portfolio() {
    	$terms = get_the_term_list( get_the_ID(), 'portfolio-type' );
    
    	if ( ! $terms ) {
    		return;
    	}
    
    	genesis_markup(
    		array(
    			'open' => '<p %s>',
    			'close' => '</p>',
    			'context' => 'entry-meta',
    			'content' => genesis_strip_p_tags( do_shortcode( "[post_terms taxonomy='portfolio-type' before='']" ) ),
    		)
    	);
    }

    You’ll also need to add this to your theme’s style.css or at Appearance → Customize → Additional CSS if you want the terms to appear uppercase on the portfolio archive, like they do on the homepage:

    .genesis-pro-portfolio.post-type-archive .entry-header .entry-meta {
    	text-transform: uppercase;
    }
    
    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @taridonohue

    The “link dots” are coming from some CSS in the Divi theme in http://mercatus.wpengine.com/wp-content/themes/Divi/style.dev.css?ver=4.9.8 on line 2975:

    #footer-widgets .footer-widget li:before {
    	position: absolute;
    	top: 9px;
    	left: 0;
    	border-width: 3px;
    	border-style: solid;
    	-webkit-border-radius: 3px;
    	-moz-border-radius: 3px;
    	border-radius: 3px;
    	content: "";
    }
    

    The dots are not added by the Simple Social Icons plugin by default.

    You could remove them with CSS like this in Appearance → Customize → Additional CSS, or in the theme’s stylesheet.

    
    #footer-widgets .footer-widget .simple-social-icons li:before {
    	content: none;
    }
    
    Plugin Contributor Nick C

    (@modernnerd)

    @jenxi The code is working in my tests. Please could you link to your site so we can help?

    Plugin Contributor Nick C

    (@modernnerd)

    @jenxi

    You can show the tags above the title (but below the image, more like the widget) by changing this line from the above code:

    
    add_action( 'genesis_entry_footer', 'sp_add_type_to_portfolio' );
    

    To look like this:

    
    add_action( 'genesis_entry_content', 'sp_add_type_to_portfolio' );
    

    Or show the tags above the image by changing the same line to this:

    
    add_action( 'genesis_entry_content', 'sp_add_type_to_portfolio', 9 );
    
    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @jenxi!

    You could add this PHP code to the bottom of your active theme’s functions.php file to output the types on the archive too:

    add_action( 'genesis_before_while', 'sp_amend_portfolio_archive' );
    /**
     * Add the portfolio post type links under the portfolio title.
     */
    function sp_amend_portfolio_archive() {
    	if ( is_post_type_archive( 'portfolio' ) ) {
    		add_action( 'genesis_entry_footer', 'sp_add_type_to_portfolio' );
    	}
    }
    
    /**
     * Output portfolio post type links.
     */
    function sp_add_type_to_portfolio() {
    	$terms = get_the_term_list( get_the_ID(), 'portfolio-type' );
    
    	if ( ! $terms ) {
    		return;
    	}
    
    	genesis_markup(
    		array(
    			'open' => '<p %s>',
    			'close' => '</p>',
    			'context' => 'entry-meta',
    			'content' => genesis_strip_p_tags( do_shortcode( "[post_terms taxonomy='portfolio-type' before='']" ) ),
    		)
    	);
    }
    Plugin Contributor Nick C

    (@modernnerd)

    You’re welcome, Brian! Thank you for letting us know it helped.

    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @amduffy.

    We don’t have plans to switch to relative URLs at the moment, as it could cause issues for CDN users who have CORS correctly configured to allow requests from their domain. (With relative URLs, icons would start loading from their domain instead of from their CDN.)

    If you’re using Simple Social Icons 3.0.0, you can use the new simple_social_icon_html filter to strip the site URL and make the path relative if you wish. Here’s one way to do it:

    add_filter( 'simple_social_icon_html', 'sp_relative_social_icon_urls' );
    /**
     * Use relative paths for Simple Social Icons SVG URLs.
     *
     * May help to avoid security warnings if icons are served from off-site URLs.
     *
     * @param string $html The original icon HTML.
     * @return string The icon HTML with paths made relative instead of absolute.
     */
    function sp_relative_social_icon_urls( $html ) {
    	$site_url = 'https://example.com';
    
    	return str_replace( $site_url, '', $html );
    }

    That code can live at the bottom of your active theme’s functions.php.

    You’d need to replace ‘https://example.com&#8217; with your site URL, or possibly with the path to the CDN URL, depending on how early your CDN plugin adjusts the URL.

    The result will be relative URLs like this:

    Screenshot showing the path of the SVG file with the domain name and protocol stripped.

    You could alternatively ask Pressable to see if they can adjust the CORS policy of their CDN to allow the SVG files to load.

    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @brian007!

    You can change your Simple Social Icons custom CSS to look like this:

    #simple-social-icons-2 li.ssi-facebook a:link,
    #simple-social-icons-2 li.ssi-facebook a:visited {
        background-color: rgba(59,89,152,1.0) !important;
    }
    
    #simple-social-icons-2 li.ssi-facebook a:hover,
    #simple-social-icons-2 li.ssi-facebook a:active {
        background-color: rgba(59,89,152,0.7) !important;
    }
    
    #simple-social-icons-2 li.ssi-pinterest a:link,
    #simple-social-icons-2 li.ssi-pinterest a:visited {
        background-color: rgba(203,32,39,1.0) !important;
    }
    
    #simple-social-icons-2 li.ssi-pinterest a:hover,
    #simple-social-icons-2 li.ssi-pinterest a:active {
        background-color: rgba(203,32,39,0.7) !important;
    }
    
    #simple-social-icons-2 li.ssi-twitter a:link,
    #simple-social-icons-2 li.ssi-twitter a:visited {
        background-color: rgba(0,172,237,1.0) !important;
    }
    
    #simple-social-icons-2 li.ssi-twitter a:hover,
    #simple-social-icons-2 li.ssi-twitter a:active {
        background-color: rgba(0,172,237,0.7) !important;
    }
    
    #simple-social-icons-2 li.ssi-youtube a:link,
    #simple-social-icons-2 li.ssi-youtube a:visited {
        background-color: rgba(187,0,0,1.0) !important;
    }
    
    #simple-social-icons-2 li.ssi-youtube a:hover,
    #simple-social-icons-2 li.ssi-youtube a:active {
        background-color: rgba(187,0,0,0.7) !important;
    }
    Plugin Contributor Nick C

    (@modernnerd)

    Hi, @goldmaverick.

    The URL you shared appears to contain a regular WordPress gallery embedded in a post.

    Genesis Portfolio Pro is designed to display portfolio items on their own page, separate to your posts and pages. You can see an example here, but they will look different with each theme:

    https://demo.studiopress.com/minimum/portfolio/

    The plugin lets you add new images in a special portfolio section in the admin area that will then appear on your portfolio page.

    You can read more and get started using the plugin here (access to documentation requires a StudioPress account):

    https://my.studiopress.com/documentation/genesis-portfolio-pro/plugin-usage/genesis-portfolio-pro-overview/

    If you have further questions, you’re welcome to reply here, contact your developer if someone else designed the site for you, or talk with the StudioPress support team from your account area if you have access to this.

    If you just want to embed an image gallery on a regular post or page, you can continue using the WordPress gallery feature, and you don’t need to use this plugin.

    Plugin Contributor Nick C

    (@modernnerd)

    @madriverweb You’re right that the tested-with version should better reflect the tested version. I’ve opened an issue to look into ways to better keep it in sync with WooCommerce: https://github.com/studiopress/genesis-connect-woocommerce/issues/42

    > In fact, the plugin was last updated 3 months ago and only claims to be compatible with 3.3+.

    WooCommerce 3.5 hadn’t been released when this plugin was last updated, which is why ‘WC tested up to’ reads 3.4. (3.5 came out on October 23, 2018, and there hasn’t been a plugin update since then; we’re currently bumping tested versions only during updates.)

    The ‘3.3+’ you’re referring to is the minimum version of WooCommerce the plugin supports.

    Thanks for sharing your experience with Genesis Author Pro and LiquidWeb, Ken.

    I wasn’t able to reproduce this in other test environments so far — the GENESIS_AUTHOR_PRO_RESOURCES_URL constant you’ve replaced here is returning the test URL in my test environments.

    It’s possible this is specific to LiquidWeb, but thank you for documenting your solution here.

    • This reply was modified 7 years, 6 months ago by Nick C.
Viewing 15 replies - 106 through 120 (of 1,249 total)