Hello, how to make us so that we do not make mistakes after each update? For example, do we make changes to content-product-slider.php, secondary_menu.php and Walkers.php?
Also metrics all meet at us constantly, (header.php)
This topic has 8 replies, 2 voices, and was last updated 4 years, 8 months ago ago by Rose Tyler
Hello, how to make us so that we do not make mistakes after each update? For example, do we make changes to content-product-slider.php, secondary_menu.php and Walkers.php?
Also metrics all meet at us constantly, (header.php)
Hello,
1) content-product-slider.php can be changed using child theme – https://developer.wordpress.org/themes/advanced-topics/child-themes/
2,3) secondary_menu.php and walkers.php – can’t be edited via the child theme. Describe in more detail why do you want to edit these files, maybe we will be able to give some suggestions.
4) Use Insert Headers and Footers plugin.
Regards
1. Thanks
2. in Walkars why that line pulls the description to the main, it hurts our optimization. menu-item-descr hidden
@$ description = ‘‘. do_shortcode ($ item-> description). ‘‘;@
3. In the secondary_menu.php we simply rotate the element in Noindex, so we can do it every time when updating.
4. In the Woo file we have to remove the piece of code that duplicates the name of the card. (we can get sanctions from search engines for this)
5. The rest of the rules apply to Woocomerce.
Here we try not to rule these moments constantly.
6. Also ask to watch Quick view, the icon stopped clicking for some reason, thank you very much!
To be able to give you a reply, I need to consult with our technicians. They are unavailable due to the weekend. Please be patient.
6. Download etheme.min.js from this page https://dropmefiles.com/rTQmu and reupload it into wp-content/themes/xstore/js folder via FTP. Then clear cache and check the quick view.
Regards
Thank you, helped 🙂
You’re welcome!
2) Inspecting the site code we didn’t find any .menu-item-descr contents so please, describe what you need to do? Show it in any other way or what?
Please, provide some screenshots for a better understanding.
Lightshot screenshot tool can be used to take screenshots and share them. Or upload your screenshots here – https://dropmefiles.com/ and provide us with URL.
4) If you need to remove some code from function which has if (!function_exists(‘function_name’) ) condition then you can simply copy the content of this function to your child-theme/functions.php and make your changes without losing them after update.
Due to your screenshot of woo.php file – you can do it via child theme by adding remove_filter( 'woocommerce_loop_add_to_cart_args', 'etheme_product_loop_data_name', 10, 2 );
Regards
Thank you, I can’t take a screenshot in the code, because now these lines are removed, they appear after the update.
Here we have the data, can you make 2 questions the same code as in point 4?
Ie so that the line is also deleted: $ description = '<span class = "menu-item-descr hidden">'. do_shortcode ($ item-> description). '</span>';in the Walkers.php file
3. And if possible, make some more code to remove this line: <label class = "screen-reader-text" for = "<? Php echo esc_attr ($ input_id);?>"> <? Php echo esc_attr ($ label); ?> </label>in quantity-input.php?
Hello,
1/ We will remove this description in next update and you can simply do it in parent theme now as well (only in this case as we allowed you and changes will be included in next theme update)
2/ As you can check default woocommerce file has such label which is usefull for some web-testers that require label for some inputs -> https://github.com/woocommerce/woocommerce/blob/master/templates/global/quantity-input.php
You can rewrite this file due to documentation of using child-theme
(you need to copy woocommerce/global/quantity-input.php from parent theme to the same directory of your child-theme and make changes there )
Read more on our documentations -> https://www.8theme.com/documentation/docs/child-theme/
Regards
The issue related to '‘Save changes after storage’' has been successfully resolved, and the topic is now closed for further responses