To have the theme listed: style.css With at minimum this: /* Theme Name: Minimum Theme Description: Test Author: Test Version: 1.0 */ For the theme to be functional: index.php index.php must have a post loop, so this would be the bare minimum functional index.php <html> <head><?php wp_head(); ?></head> <body> <?php if ( have_posts() ) { … Read more
Late to the party but this will do the trick: $wp_customize->remove_control(‘blogdescription’); You want to remove just that control, not entire section as suggested above.
Try deregistering that stylesheet – add_action( ‘wp_print_styles’, ‘my_deregister_styles’, 100 ); function my_deregister_styles() { //wp_deregister_style( ‘amethyst-dashicons-style’ ); wp_deregister_style( ‘dashicons’ ); }
I think some of your questions are too wide. You still cannot break down each answer in hours. Some of the questions I ask: Are there widgets? Which? Which theme options are needed? Details? Colors, text fields, image uploads etc. Custom post types and taxonomies? Very, very detailed. How are the comments displayed? This one … Read more
You can also hook into the core update routine. (I’m looking for tutorial links, but my Google-fu is failing me this morning.) EDIT: See if this tutorial helps. It explains how to implement automatic upgrades for private/commercial (i.e. non-repository-hosted) Plugins.
If you know the menu’s slug, then things are easier, otherwise you can use this function to get the menu at a specified location. <?php function wpse45700_get_menu_by_location( $location ) { if( empty($location) ) return false; $locations = get_nav_menu_locations(); if( ! isset( $locations[$location] ) ) return false; $menu_obj = get_term( $locations[$location], ‘nav_menu’ ); return $menu_obj; } … Read more
No, they should not. If a plugin has vulnerabilities just because someone might see its directory structure it is broken. These bugs should be fixed. Security through obscurity is a bug for itself. It’s up to the site owner to allow or forbid directory browsing. A second issue is performance: WordPress scans all PHP files … Read more
Yes it works well. It’s a very simple function but never found a mobile device not recognized by it. It recognize the 90%+ of mobile devices. Main difference from mobiledetect.net is that doesn’t differe from phone and tablets. See the code
What you’re looking for is wp_localize_script function. You use it like this when enqueing script wp_register_script( ‘my-script’, ‘myscript_url’ ); wp_enqueue_script( ‘my-script’ ); $translation_array = array( ‘templateUrl’ => get_stylesheet_directory_uri() ); //after wp_enqueue_script wp_localize_script( ‘my-script’, ‘object_name’, $translation_array ); In your style.js, there is going to be: var templateUrl = object_name.templateUrl; …
Use a custom walker, remove anything you don’t need and add your classes. Here is a walker I use to get a list with clean markup: T5_Nav_Menu_Walker_Simple. Your could also filter ‘nav_menu_css_class’ or ‘wp_nav_menu_items’. But a walker class is easier to understand and to control in my opinion.