This topic has 4 replies, 3 voices, and was last updated 5 years, 6 months ago ago by Olga Barlow
Hello
In XStore’s updated child theme, I noticed the following code snippet:
if ( is_file($upload_dir['basedir'].'/xstore/options-style.min.css') && filesize($upload_dir['basedir'].'/xstore/options-style.min.css') > 0 && !is_customize_preview() ) {
$custom_css = $upload_dir['baseurl'] . '/xstore/options-style.min.css';
I use custom theme folder names instead of xstore and xstore-child, i.e. mysite and mysite-child. In the past, I have not seen code explicitly mentioning the path that includes the xstore folder name like this. I am worried that this might somehow break my site if I update. Can you please advise me if the changes to your child theme functions.php, naming the path of the original xstore folder will cause me a problem if I upgrade to v5.0.2? Ou will appreciate that I do not want to name the theme folder xstore.
Regards
Hello,
The following code doesn’t have any effect on your website, this is for saving custom css from theme options and there is no difference of what theme folder name you have.
Regards.
Hello Rose
Aaah! I see. Thank you for reassuring me. 🙂
Warm regards
You are welcome!
Regards
The issue related to '‘XStore v5.2 worrying change to child theme functions.php advice needed’' has been successfully resolved, and the topic is now closed for further responses