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” />
You may try Eazy Po. From file menu select “New from source code files..”. In xgettext Command Manager window; Press “Browse folder” to select base source folder. In Build pane press “Execute Command” button to generate Pot file.
As of WordPress 4.5 you can use: get_post_type_archive_link( ‘post’ ); This handles the logic of getting the correct URL regardless of whether posts show up on the homepage or in a specified page.
Use wp_enqueue_script() in your theme The basic answer is to use wp_enqueue_script() in an wp_enqueue_scripts hook for front end admin_enqueue_scripts for admin. It might look something like this (which assumes you are calling from your theme’s functions.php file; note how I reference the stylesheet directory): <?php add_action( ‘wp_enqueue_scripts’, ‘mysite_enqueue’ ); function mysite_enqueue() { $ss_url = … Read more