amanda blum

Any idea why the above code would sub the svg icons correctly but NOT pull new height/width? In twenty twenty-one, I’m subbing the plus/minus in the main nav with an up/down carot. Sidenote: this was coded to a custom plugin, not to the functions file in the theme.

/* CHANGE PLUS MINUS ICONS IN MAIN NAV
================================================== */
function clitheme_twenty_twenty_one_svg_icons_ui( $icons ) {
    $icons['plus'] = '<svg xmlns="https://www.w3.org/2000/svg" viewBox="0 0 24 24" width="10px" height="10px"><path fill-rule="evenodd" d="M0 7.33l2.829-2.83 9.175 9.339 9.167-9.339 2.829 2.83-11.996 12.17z"></path></svg>';
	  $icons['minus'] = '<svg xmlns="https://www.w3.org/2000/svg" viewBox="0 0 24 24" width="10" height="10"><path fill-rule="evenodd" d="M0 16.67l2.829 2.83 9.175-9.339 9.167 9.339 2.829-2.83-11.996-12.17z" ></path></svg>';
 
    return $icons;
}
add_filter( 'twenty_twenty_one_svg_icons_ui', 'clitheme_twenty_twenty_one_svg_icons_ui' );

Note the new height/width in the code above, but the rendered output on front end still shows 18px height/width, which comes from the original svg file in classes.

svg[Attributes Style] {
    width: 18;
    height: 18;
}

• This reply was modified 3 years, 2 months ago by amanda blum.
• This reply was modified 3 years, 2 months ago by amanda blum.

I didn’t realize it was only targeting core. And I kind of can’t believe that we’re just all realizing that todayI didn’t realize it was only targeting core. And I kind of paint believe that we’re just all realizing that today – at the minimum the documentation for the plug in need to be changed immediately to reflect this so that the average use our has something to explain to them what’s going on. And then obviously since millions of people downloaded the guttenberg plug into test things as they were advice to we should have ended to also affect the plug in not just core.

I can confirm this bug weather with 4.9 or 5.0

what is your road map to Gutenberg support? the classic editor will be phased out, and unfortunately all other plugins are moving towards Gutenberg not away from it. Gutenberg support as a major decision in our purchase of an idx plugin. why would we purchase something that’s already outdated?

I wish I could have figured it out, but I wasn’t able to. But I use this plugin with some frequency because of its utility- and would love to see this feature as term meta gains usage.

So…. the rules work when used in the front end, no problem. In the themefiles… they don’t seem to want to work. Is this because the content I’m looking to hide is php rather than html output?

<?php
do_shortcode(‘[timed-content-rule id=”696″]’.get_template_part( ‘stuff’ ).'[/timed-content-rule]’);
?>

have also tried <?php
$result = get_template_part( ‘stuff’ );
echo do_shortcode(‘[timed-content-rule id=”696″]’.implode(‘, ‘, $result).'[/timed-content-rule]’);
?>

and
<?php
$result = get_template_part( ‘wdbreak’ );
echo do_shortcode( ‘[timed-content-rule id=”696″]’ . $result . ‘[/timed-content-rule]’ );
?>

Could you give a code example of this? Since you have to open and close the shortcode its a bit confusing.

Cool, thanks for responding. Have a client who will be happy to hear there’s a fix.

At the time that I posted, it was ACF pro, whatever the most current install of WP was at the time (4.1.x), twenty-fifteen theme, all plugins current. Audited all plugins one by one, and Greenhouse was the gamechanger. Without it activated, ACF will save fields, with it, you get the spinning ball of “I am processing but will never finish processing”.

and now I have. thank you!