[mk_fancy_title tag_name=”h4″ color=”#444444″ size=”18″ font_weight=”bold” txt_transform=”capitalize” letter_spacing=”1″ margin_bottom=”0″ font_family=”none”]Child theme and shortcode override changes[/mk_fancy_title][mk_divider style=”thin_solid” divider_width=”custom_width” custom_width=”25″ align=”left” thin_single_color=”#fe5320″ thickness=”3″ margin_top=”5″]
If you have ever overridden Jupiter shortcodes in a child theme, there are a couple of things you need to do before migrating to Jupiter V5!
In V4.X and older versions the folder structure for shortcodes was as follows: shortcodes/shortcode_name.php
In V5.X we have changed it to “architecture by feature” meaning that its configurations, styles, scripts and shortcode options stay on the same folder. You can also override its assets and options as well (which was previously not possible).
Old Method :
jupiter/shortcodes/mk_button.php
New Method :
jupiter/components/shortcodes/mk_button/mk_button.php
jupiter/components/shortcodes/mk_button/mk_button.css
jupiter/components/shortcodes/mk_button/vc_map.php
jupiter/components/shortcodes/mk_button/config.php
[mk_image src=”http://demos.artbees.net/jupiter5/wp-content/uploads/2015/12/components-shortcodes-mk-button.jpg” image_size=”full” title=”Shortcodes Architecture” desc=”Overriding shortcodes in Jupiter V5 is a different process” caption_location=”outside-image” align=”center”][mk_padding_divider size=”60″]
Sorry, the comment form is closed at this time.