Mostly the parent theme might be enqueing the child theme’s style.css, if so you can dequeue it by using handle and then enqueue with proper dependency. If the child theme’s handle is child-theme-style, then dequeue it using wp_dequeue_style(‘child-theme-style’) then enqueue it as needed like so. wp_enqueue_style(‘child-theme-dep’,get_stylesheet_uri(),array(‘bootstrap-handle-here’)) We can easily know the child theme stylesheet url … Read more
I like to do this as follows: Go to underscores.me, fill out the theme name, and download the theme. Strip out the parts of this (somewhat clean) template that don’t want to use. Start building your own template with the functionality that you wrote. This way you will have a clean template to start with, … Read more
First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked. So the long-term solution would be to: Check the version of modified theme. Download that version from … Read more
There are probably several solutions to this, but this is what I would do: First set a static front page. This can be done in Settings->Reading. This will cause the menu item (page) selected to have the CSS class current-menu-item and also to display any sub-menu items you have. Then you just CSS them to … Read more
Start with “view source” of rendered HTML and then work backward from that, building a new theme by pulling whatever css, php files and functions from the parent as needed. (footnote – thank you for the pointer to the ‘dust me’ utility, I will check that out).
I think I found a solution, but before a little Premise load_theme_textdomain() and load_child_theme_textdomain() are basically equal, the only difference is the default path they use: they get the current language (using get_locale()) and add the relative .mo file to the path passed as argument; then they call load_textdomain() passing as argument both the textdomain … Read more
As said, it is bad practice to make modifications to any theme/plugin you are not the author of, the simple reason been, if you ever update that theme/plugin, all chnages will be lost. You should always create a child theme or a functionality plugin You said that you cannot get the parent’s stylesheet. There are … Read more
You are using get_stylesheet_uri() which links directly to your stylesheet, then your adding /style.css which is resulting in an invalid url. So you need to remove the /style.css. Or use get_stylesheet_directory_uri() and leave the /style.css on there.
This is the proper way to load a custom javascript in your child theme, wp_localize_script is only necessary if you need to exchange data between JS and PHP (Client and server). function assets() { wp_register_script(‘ajax_filter’, get_stylesheet_directory_uri() . ‘/js/ajax-filter-posts.js’, [‘jquery’], ‘1.0’, false); wp_enqueue_script(‘ajax_filter’); wp_localize_script( ‘ajax_filter’, ‘mdu’, array( ‘nonce’ => wp_create_nonce( ‘mdu’ ), ‘ajax_url’ => admin_url( ‘admin-ajax.php’ … Read more
I think it might be possible, try adding this to your child theme’s functions.php add_action(‘init’, ‘remove_plugin_image_sizes’); function remove_plugin_image_sizes() { remove_image_size(‘image-name’); } Here is the documentation: https://codex.wordpress.org/Function_Reference/remove_image_size