Example and class for usage You can see on my current theme, how it’s possible to use this. Also you can usage the class. See this class on Github an check the functions.php for include this. Start & init You can register your custom settings for the theme customizer via the customize_register hook: add_action( ‘customize_register’, … Read more
There is no automatic preview. You need to create the screenshot yourself and place it in the theme/child theme folder named screenshot.png The recommended image size (currently) is 1200px wide by 900px tall, however the screenshot will only be shown as 387×290. It is over-sized to allow for high-resolution viewing on HiDPI displays. Note that … Read more
OK, I found the answer to this one and its surprisingly simple but maddeningly frustrating at the same time. All you have to do is click “Screen Options” while viewing the “Custom Menu” manager and place a check beside “Posts” to show the elusive hidden “Posts” widget. Now you can add “Posts” to your custom … Read more
You just need to add the styles directly to the page head. The best way to do this is to use the ‘wp_head’ action hook, assuming you are using a theme that has the hook. Like so: add_action(‘wp_head’, ‘my_custom_styles’, 100); function my_custom_styles() { echo “<style>*{color: red}</style>”; } Check out the WP codex to learn more … Read more
Like most others, I highly recommend using WPTouch. However, it’s built more to support blogs than other website formats, so I know it’s not the panacea of mobile solutions (I run my portfolio on WordPress as well as my blog, and my portfolio looks like **** in WPTouch). So I did take a look at … Read more
In addition to the other two suggestions, there is another possible approach: move all of your custom-app functionality out of the Theme, and into a hosted web service, to which the Theme connects via API key. That way, redistribution of the Theme itself does not impact your custom app-based business model, because the app would … Read more
Usually, you don’t need it. But … there is at least one edge case: If a theme file is a template part, and it is using global variables from the calling context (parent file), and register_globals is on, and it is just using these variables without any security check … … an attacker can call … Read more
This is only used in template-loader.php, to determine whether it should load a theme file or not. The normal “boot sequence” of WordPress (started in wp-blog-header.php) loads the plugins, parses the URL, executes a post query based on the URL, and calls the theme. This main post query is typically used in “The Loop”. So … Read more
I could be wrong, but I vaguely remember that: name, email get hijacked by WordPress to do post comments, if you renamed the form elements to be contact-name and contact-email, do you get the same issue?
This function will return the theme directory URL so you can use it in other functions: get_bloginfo(‘template_directory’); Alternatively, this function will echo the theme directory URL to the browser: bloginfo(‘template_directory’); So an example for an image in the themes images/headers folder would be: <img src=”https://wordpress.stackexchange.com/questions/665/<?php bloginfo(“template_directory’); ?>/images/headers/image.jpg” />