The correct “WordPress” way of doing it would be to use the_widget template tag to display widgets anywhere you want. so in you case you would something like this: $instance[‘account’] = ‘account name’; //Ustream channel name $instance[‘online’] = ‘http://www.online_image.URL’; $instance[‘offline’] = ‘http://www.offline_image.URL’; the_widget(‘wp_ustream_status’, $instance);
The .htaccess is parsed before WordPress is loaded, so you don’t get access to WordPress data. You can make the redirect in WordPress, in a plugin: Hook into 404_template and inspect $_SERVER[‘REQUEST_URI’] with parse_url(). You should be able to find the matching post for the image then. You did not write how the permalinks for … Read more
Simply use template_redirect filter to perform check on request you get in wordpress. add_filter(‘template_redirect’, ‘my_404_override’ ); function my_404_override() { global $wp_query; if (!$wp_query->post) { // Check if any post is found. If not its 404. status_header( 200 ); $wp_query->is_404=false; // Create post object $my_post = array( ‘post_title’ => ‘My post’, ‘post_content’ => ‘This is my … Read more
I found the answer, dropping it here in case someone need it. You need to be logged in as a user that has the edit_posts capability. With that capability, you also get access to the private query vars, including post_status. Taken from this similar issue.
Did you know you can just copy paste a youtube URL onto its own line and it transforms into a video player auto-magically via oembed? There’s no need for embed codes/shortcodes/plugins Simply create a blank line, and take the address of the youtube video and paste it into the editor: These youtube videos should not … Read more
There is a similar problem to create posts from an API and programmatically generating posts. Essentially just parse the JSON into an array, grab the fields you need, and create the post/product. You most likely need to pull the images as well. You should also consider if the post already exists in your database and … Read more
Ok, I just stumbled upon the answer buried deep in the github issues page: https://github.com/WP-API/WP-API/issues/1403 The answer is: the reason is that the terms / meta etc are different objects, and in typical REST design going a GET on a single resource, will give you that resource, not that resource and a bunch of other … Read more
The main difference is semantical. A page is something that stands by itself, while a post type in a categorization of content. This semantical difference results in different admin flow for both. The only other difference is that pages can have flexible URLs and you can basically put a page anywhere. As far as core … Read more
You are partially correct , you are not passing cat id in your parameter. Try $categories_array[ $category->term_id ] = $category->name; Now you will get category id as drop down value.
In order to have your post have a default image, you need to set your post thumbnail. In doing this you need to set the ID of the media, which isn’t readily apparent. I do most of my work in Python, so for me, the following helps: Step 1. Get the list of all your … Read more