You can do exactly that by creating Child Theme. It depends on specifics of theme you want to customize and amount of changes how complex will it be to implement, but it is definitely most solid way to implement customization and preserve update capabilities.
If you don’t want to develop/maintain your own Theme, then yes: choose an existing Theme, and make modifications to it via Child Theme. If, on the other hand, you are comfortable with developing/maintaining your own Theme, then either create a new Theme, or make a derivative of an existing Theme. Since, as you state, you … Read more
This looks flawed: add_theme_support( ‘post-thumbnails’, array( ‘post’ ) ); add_theme_support( ‘post-thumbnails’, array( ‘page’ ) ); Do you see the post thumbnail box on pages? If so, you have just overwritten the support on posts with the second declaration. Better: add_theme_support( ‘post-thumbnails’, array( ‘post’, ‘page’ ) );
Assuming this array for example usage: $options = array( “name” => __(‘Font’,’mytheme’), “desc” => __(‘Change the font face)’,’mytheme’), “id” => “mytheme_font”, “std” => array(‘size’ => ’10px’, ‘face’ => ‘Arial’, ‘color’ => ‘#000000’), “type” => “text”, ); For question 1, to reference nested arrays, just reference them directly. echo $options[‘std’][‘size’]; In the form input, if using … Read more
Refer to the Template Hierarchy in Codex. If you have assigned a static front page, the template that will take priority for that page is front-page.php, and the template for the posts (blog) page is home.php.
If you want to keep your changes while allowing Mog theme to keep updated you will need to create a child theme. This will ensure your changes are kept.
I think that the default themes are there to be used. These themes are coded to the standards that should be used and excellent example for new theme authors to learn from. They are also all under the GNU General Public License. I would really think that these are excellent basis to work from when … Read more
Actually, what you have described is the correct way to do things and there shouldn’t be any noticeable impact on site speed and performance. Using child themes also has the benefit of allowing your changes to persist through theme upgrades.
Sure, just upload them to their directories with ftp. After all, updating themes is not much more than copying the files. If you update the active theme in this way, some unexpected results may occur for pages that are generated halway the uploading, part by the old theme, part by the new theme.
The problem is in the folder structure. The child theme should be in the same directory as the parent theme. That is: E:\xampp\htdocs\wordpress\wp-content\themes\panoramic-child Not: E:\xampp\htdocs\wordpress\wp-content\themes\panoramic\panoramic-child Also you don’t need this line in the header comment of a parent theme’s style.css: Template: panoramic It is used only in a child theme.