I hear you. I’ve been very disappointed with almost every theme I’ve ever purchased. That includes multiple Theme Forest themes, one from MOJO, Elegant Themes, and more. The only theme foundry I like is…wait for it, this is so poetic…The Theme Foundry. The quality of their themes is underscored (not to be confused with _s) … Read more
It might look more elegant, but you don’t want to nest hooks in this way. You’re now ending up with actions added inside a logic check inside another action hook. Instead, keep your functions as granular and atomic as possible and only hook them in where needed. Your first technique isn’t inefficient at all, it’s … Read more
bloginfo() is using echo, you need a function that returns its value: get_bloginfo(). In this case you could also use just the function get_bloginfo() is using: get_template_directory_uri().
If you look at that code carefully, the only thing it ever prints are sticky posts: if(is_sticky()) : ?> <div class=”slide”><a rel=”bookmark” href=”https://wordpress.stackexchange.com/questions/92193/<?php the_permalink() ?>”><?php echo the_post_thumbnail(‘full’); ?><h2><?php the_title(); ?></h2></a></div> <?php endif; You stand a better chance of having sticky posts on page 1 of the index than on any page thereafter. 404 pages don’t … Read more
It fails because there is already a theme with that name on the server. So the obvious solution is to remove the theme before you upload the new version. If you’re wanting to use an update mechanism like the theme repo, but on a custom theme, there are udpater classes you can add, such as … Read more
The Navigation Menus system is adding a lot of classes, including matching current page (rather intelligently, it will even try to detect custom URLs, that were input explicitly). The simplest class to make use of is current-menu-item, but there are quite a few more dealing with parents/ancestors and more. Codex has them documented at wp_nav_menu() … Read more
Actually you shouldn’t add JS and CSS files to your header.php, but make use of the functions wp_enqueue_script() and wp_enqueue_style() to add them there. Example taken from the codex page: /** * Proper way to enqueue scripts and styles */ function theme_name_scripts() { wp_enqueue_style( ‘style-name’, get_stylesheet_uri() ); wp_enqueue_script( ‘script-name’, get_template_directory_uri() . ‘/js/example.js’, array(), ‘1.0.0’, true … Read more
That’s the Jetpack Stats image, it’s necessary to track the stats. You can disable it by disabling Jetpack Stats but it shouldn’t be full width, that will be a CSS problem
You can get the original sizes of the image being uploaded: list( $uploaded_width, $uploaded_height ) = getimagesize( $_FILES[‘u_img’][‘tmp_name’] ); Then you can use those values to size the image as you like: $height = 300; $image = wp_get_image_editor( $_FILES[‘u_img’][‘tmp_name’] ); $image->resize( $uploaded_width, $height, true );
When using wp_enqueue_script, you probably passing true for in_footer parameter. If so, then check that your search.php is calling get_footer() function at the bottom.