When you set a child theme, basically WP looks into 2 directories to see if there are some overriding to make. So it adds some impact on performance. The use of @import in child CSS can also have some bad impact on performance grade. Most of the time, it depends on the parent’s theme quality. … Read more
Unfortunately this isn’t covered in that codex page. These previews of the themes aren’t auto generated. You will need to take a screenshot of your theme, and upload that screenshot to your root folder as ‘screenshot.png’. This screenshot will be automatically used then as a theme preview pic for your theme. I quote from the … Read more
I think you’ve nothing in the index.php file. So what is happening that the child theme is calling the child theme’s index.php over parent theme’s index.php. And you have nothing on index.php. So the site is showing nothing. Delete the child theme’s index.php. You’ll see the site live.
Of course there’s a function for that (Codex): switch_theme( $stylesheet ) It: Switches current theme to new template and stylesheet names. Accepts one argument: $stylesheet of the theme. ($stylesheet is the name of your folder slug. It’s the same value that you’d use for a child theme, something like twentythirteen.) It also accepts an additional function signature … Read more
For cases where you want to require/include PHP files, but still allow child themes to replace those PHP files outright, then you should use the locate_template function. Example: Parent does this: locate_template( ‘admin/file.php’, true ); This finds the admin/file.php file in either the child or the parent theme, then does a require on it (that’s … Read more
You need to flush and regenerate your permalinks everytime you modify/add/remove custom post types or taxonomies. Going to the permalinks page and saving should be enough ( Also your custom post type code should be in a plugin, not the theme, else the user is stuck using that theme forever )
You simply need to run your code on a higher priority than what the parent theme is, the default on add_action function is 10 so you can use: function s157343_unregister_widgets() { unregister_widget( ‘Chocolat_Widget_New_Entrys’ ); } add_action( ‘widgets_init’, ‘s157343_unregister_widgets’, 20 ); This will unregister that widget. Of course, you can still create a new class that … Read more
It looks like the plugin doesn’t want you do access the APP_Registration instance, so you can try this: add_filter( ‘register_url’, function( $url ) { // Adjust this to your needs $url = site_url( ‘wp-login.php?action=register’, ‘login’ ); return $url; }, 11 ); to override the plugin’s modifications, where we use a priority > 10.
It depends entirely on a) what functions and template files you’re talking about, and b) how those functions are defined, or template files are called, in the Parent Theme. If the Parent Theme uses get_template_part(), then you’re golden. If the Parent Theme uses get_stylesheet_directory_uri() or STYLESHEETPATH, then you can override, with caveats. If the Parent … Read more
I would like to thank very much cybmeta for pointing me tho the other thread where I could find a solution to my problem. All works perfectly now and I am glad I received help so fast. I have modified my child functions.php like below: <?php function mytheme_scripts() { if ( ! is_admin() && ! … Read more