You don’t need to copy the inc/icon-functions.php file and include/require it from the child theme — remember that the parent theme will also load the same file/functions and that would result in a PHP error if you did not rename the functions in the copied file. So try these: (You’ve already done this properly, as … Read more
Sorry to say, but it’s not possible, because none of the elements from the SVG are read in the DOM, so CSS and Javascript don’t see them. All it sees is the <img> block, none of its contents. You have to import your SVGs into the page to have them be able to be manipulated. … Read more
Ok, this is what I did: First, I replicated classes/class-twentynineteen-svg-icons.php to the child theme. Renamed to class-mytheme-svg-icons.php. Added a extend with my New_SVG_Icons class: class New_SVG_Icons extends TwentyNineteen_SVG_Icons { /** * Gets the SVG code for a given icon. */ public static function get_svg( $group, $icon, $size ) { if ( ‘ui’ == $group ) … Read more
You’ll also need to add “svg” to the list of valid extensions in WP_Customize_Image_Control: $wp_customize->add_control( new WP_Customize_Image_Control( $wp_customize, ‘themeslug_logo’, array( ‘label’ => __( ‘Logo’, ‘themeslug’ ), ‘section’ => ‘themeslug_logo_section’, ‘settings’ => ‘themeslug_logo’, ‘extensions’ => array( ‘jpg’, ‘jpeg’, ‘gif’, ‘png’, ‘svg’ ), ) ) );
I agree with Tom J Nowell on the use of SVG, but if the upload is an actual image, you can tap into the attachment attributes using, as you suggested, wp_get_attachment_image_src. Those dimensions are actually already recorded and stored when using the WP media uploader, it’s likely that the plugin you’re using makes use of … Read more
It’s because that’s not how you should include an SVG in PHP, include_once is used for including PHP files. Reason behind this error: PHP Parse error: syntax error, unexpected version (T_STRING) is that PHP was unable to parse the beginning of the SVG file at the point where the XML version was defined: <?xml version=”1.0″ … Read more
Found your question as I was searching for an answer. I tried experimenting a bit more with wp_kses and found that lower-casing viewbox in the arguments seems to fix the issue. You don’t have to put the actual attribute on the SVG in lowercase, just the wp_kses() argument. This may be more than you need, … Read more
[*] Unfortunately the colon is a TinyMCE control character Forces the attribute to the specified value. For example, ‘border:0’ …hence the switch to xlink=href. The only apparent solution is the wildcard use[*] Use the control character ? which “separates attribute verification values” i.e. use[xlink?href] [*]
Per the thread below, a temporary solution would be to add this code to your wp-config file: define( ‘ALLOW_UNFILTERED_UPLOADS’, true ); https://wordpress.org/support/topic/wp-4-7-1-kills-svg/page/3/
This article has a bunch of great answers to your questions. I highly recommend checking it out to learn more about the scale of this issue, but I can give a quick rundown. SVG, since it’s XML based, makes it really hard to decipher what is and what isn’t malicious. At one end, it opens … Read more