Wordpress Ajax Json callimg

IN functions.php 

add_action('wp_footer', 'eps_footer');

function eps_footer() {

    echo "<script>var ajax_request_url = '".admin_url( 'admin-ajax.php' )."'</script>";

}

$.get( ajax_request_url,

  {

   'action' : 'get_post_title',

   'post_id' : 1

  }, function( response ){

    if ( !response.error ) {

      alert ('AJAX request made! The post title is ' + response.post_title );

    } else {

      alert ('error: ' + response.error );

    }

},  "json" );

add_action( 'wp_ajax_nopriv_get_post_title', 'get_post_title' );

add_action( 'wp_ajax_get_post_title', 'get_post_title' );

function get_post_title() {

  if ( isset($_GET['post_id']) ){

    $id = (int) $_GET['post_id'];

    $post = get_post( $id );

    header( "Content-Type: application/json" );

    echo json_encode( array('post_title' => $post->post_title) );

  } else {

    header( "Content-Type: application/json" );

    echo json_encode( array('error' => 'bad request') );

  }

  exit;

}

Where is the right place to register/enqueue scripts & styles

I am using WordPress 3.1.4 by now. I am confused with where (which hook) do I use:

• to register and/or enqueue
• scripts and styles
• on front- and back-ends?

Questions:

• Which are right hooks to use?
• All front end register/enqueue scripts/styles in init?
• Why is there no admin_print_styles-{xxx}?

hooks wp-enqueue-script wp-enqueue-style wp-register-style wp-register-script

ANSWER:-

Why registering and queuing properly matters

• it should be in time - earlier than script/style is up for being output to page, otherwise it is too late;
• it should be conditional - otherwise you are loading stuff where you don't need it and cause performance and functionality issues, for this you need WP environment loaded to late stage.

The three stages of the process

1. register - this explains WP details about script/style and makes it store that info;
2. enqueue - (often lumped together with register in one wp_enqueue_*() call) - this tells WP to add scripts/style to the queue, according to its settings (dependencies, header/footer loading).
3. print - this happens when WP processes queue, tries to load something specific for itself orwhen you explicitly do it with wp_print_*() function.

Front-end structure of functions and hooks

• wp_head()
  • wp_head
    • (1) wp_enqueue_scripts()
      wp_enqueue_scripts « this is what you need
    • (8) wp_print_styles()
    • (9) wp_print_head_scripts()
• wp_footer()
  • wp_footer
    • (10) wp_print_footer_scripts()

It goes much deeper, but this is simple and good enough for important points:

• wp_enqueue_scripts is most appropriate hook for registering and queuing scripts and styles on front end and it is there specifically for that;
• init has nothing to do with this, it will work, but - past Codex recommendation to use only it was incorrect;
• you can get away with queuing scripts (not styles) for footer at any point beforewp_print_footer_scripts() call;
• wp_print_* hooks are NOT appropriate for register/queue, they are points in code when output is already happening. They are appropriate for manual/custom script/style output.

What about admin?

Well, the functionality there is even more complex, elaborate and nested.

• for starters just use admin_enqueue_scripts hook (it gets passed $hook_suffixglobal for conditional stuff) for everything, it will do nicely for most cases;
• when you need something complex - look through admin-header.php and dig from there for appropriate hooks.

What about login?

There's a specific hook named login_enqueue_scripts.

Create more Meta Boxes as needed

I'd like users to be able to create and remove additional meta box fields as needed.

For example, say a music podcast with a variable amount of songs played per episode. The user should be able to click a button that will add additional fields to enter each song as needed.

Ideally this would be done without the use of a plugin, but coded into the functions file.

metabox

ANSWER:-

if it is what you mean the its done by creating a metabox that has simple jquery function to add and remove fields in it, and the data is saved as an array in of data in a single meta row, here you go:

add_action( 'add_meta_boxes', 'dynamic_add_custom_box' );

/* Do something with the data entered */
add_action( 'save_post', 'dynamic_save_postdata' );

/* Adds a box to the main column on the Post and Page edit screens */
function dynamic_add_custom_box() {
    add_meta_box(
        'dynamic_sectionid',
        __( 'My Tracks', 'myplugin_textdomain' ),
        'dynamic_inner_custom_box',
        'post');
}

/* Prints the box content */
function dynamic_inner_custom_box() {
    global $post;
    // Use nonce for verification
    wp_nonce_field( plugin_basename( __FILE__ ), 'dynamicMeta_noncename' );
    ?>
    <div id="meta_inner">
    <?php

    //get the saved meta as an arry
    $songs = get_post_meta($post->ID,'songs',true);

    $c = 0;
    if ( count( $songs ) > 0 ) {
        foreach( $songs as $track ) {
            if ( isset( $track['title'] ) || isset( $track['track'] ) ) {
                printf( '<p>Song Title <input type="text" name="songs[%1$s][title]" value="%2$s" /> -- Track number : <input type="text" name="songs[%1$s][track]" value="%3$s" /><span class="remove">%4$s</span></p>', $c, $track['title'], $track['track'], __( 'Remove Track' ) );
                $c = $c +1;
            }
        }
    }

    ?>
<span id="here"></span>
<span class="add"><?php _e('Add Tracks'); ?></span>
<script>
    var $ =jQuery.noConflict();
    $(document).ready(function() {
        var count = <?php echo $c; ?>;
        $(".add").click(function() {
            count = count + 1;

            $('#here').append('<p> Song Title <input type="text" name="songs['+count+'][title]" value="" /> -- Track number : <input type="text" name="songs['+count+'][track]" value="" /><span class="remove">Remove Track</span></p>' );
            return false;
        });
        $(".remove").live('click', function() {
            $(this).parent().remove();
        });
    });
    </script>
</div><?php

}

/* When the post is saved, saves our custom data */
function dynamic_save_postdata( $post_id ) {
    // verify if this is an auto save routine. 
    // If it is our form has not been submitted, so we dont want to do anything
    if ( defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE ) 
        return;

    // verify this came from the our screen and with proper authorization,
    // because save_post can be triggered at other times
    if ( !isset( $_POST['dynamicMeta_noncename'] ) )
        return;

    if ( !wp_verify_nonce( $_POST['dynamicMeta_noncename'], plugin_basename( __FILE__ ) ) )
        return;

    // OK, we're authenticated: we need to find and save the data

    $songs = $_POST['songs'];

    update_post_meta($post_id,'songs',$songs);
}

Custom post types, taxonomies, and permalinks

I simply want my URLs to look like this:

mysite.com/products/category1/product-name1 
mysite.com/products/category2/product-name2

But for the life of me, no matter what I do, I'm getting the dreaded 404 issue. Pages work okay, and Posts work okay, but my custom posts don't work correctly. They're showing up as:

mysite.com/products/product-name1
mysite.com/products/product-name2

Which actually works! It's just that I want to see my custom taxonomy in there, PLUS, I want to be able to access the taxonomy.php template I have setup by going to:

mysite.com/products/category1/
mysite.com/products/category2/

None of my slugs are the same, nor do I want them to be. Here is the post type and taxonomy part of my functions.php file:

///// CUSTOM POST TYPES /////


// register the new post type
    register_post_type( 'product_listing',
        array( 'labels' => array(
            'name' => __( 'Products' ),
            'singular_name' => __( 'Product' ),
            'add_new' => __( 'Add New' ),
            'add_new_item' => __( 'Create New Product' ),
            'edit' => __( 'Edit' ),
            'edit_item' => __( 'Edit Product' ),
            'new_item' => __( 'New Product' ),
            'view' => __( 'View Products' ),
            'view_item' => __( 'View Product' ),
            'search_items' => __( 'Search Products' ),
            'not_found' => __( 'No products found' ),
            'not_found_in_trash' => __( 'No products found in trash' ),
            'parent' => __( 'Parent Product' ),
            ),
            'description' => __( 'This is where you can create new products on your site.' ),
            'public' => true,
            'show_ui' => true,
            'capability_type' => 'post',
            'publicly_queryable' => true,
            'exclude_from_search' => false,
            'menu_position' => 2,
            'menu_icon' => get_stylesheet_directory_uri() . '/images/tag_orange.png',
            'hierarchical' => true,
          '_builtin' => false, // It's a custom post type, not built in!
            'rewrite' => array( 'slug' => 'products', 'with_front' => true ),
            'query_var' => true,
            'supports' => array( 'title', 'editor', 'author', 'thumbnail', 'excerpt', 'trackbacks', 'custom-fields', 'comments', 'revisions' ),
            )
);



//hook into the init action and call create_book_taxonomies when it fires
add_action( 'init', 'create_product_taxonomies', 0 );
//add_action('admin_init', 'flush_rewrite_rules');

//create two taxonomies, genres and writers for the post type "book"
function create_product_taxonomies() 
{
  // Add new taxonomy, make it hierarchical (like categories)
  $labels = array(
    'name' => _x( 'Categories', 'taxonomy general name' ),
    'singular_name' => _x( 'Category', 'taxonomy singular name' ),
    'search_items' =>  __( 'Search Categories' ),
    'all_items' => __( 'All Categories' ),
    'parent_item' => __( 'Parent Categories' ),
    'parent_item_colon' => __( 'Parent Categories:' ),
    'edit_item' => __( 'Edit Category' ), 
    'update_item' => __( 'Update Category' ),
    'add_new_item' => __( 'Add New Category' ),
    'new_item_name' => __( 'New Category Name' ),
    'menu_name' => __( 'Category' ),
  );    

  register_taxonomy('product_cat',array('product_listing'), array(
    'hierarchical' => true,
    'labels' => $labels,
    'show_ui' => true,
    'query_var' => true,
    //'rewrite' => true,
    'rewrite' => array( 'slug' => '%category%', 'with_front' => true ),
  ));

  // Add new taxonomy, NOT hierarchical (like tags)
  $labels = array(
    'name' => _x( 'Scents', 'taxonomy general name' ),
    'singular_name' => _x( 'Scent', 'taxonomy singular name' ),
    'search_items' =>  __( 'Search Scents' ),
    'popular_items' => __( 'Popular Scents' ),
    'all_items' => __( 'All Scents' ),
    'parent_item' => null,
    'parent_item_colon' => null,
    'edit_item' => __( 'Edit Scent' ), 
    'update_item' => __( 'Update Scent' ),
    'add_new_item' => __( 'Add New Scent' ),
    'new_item_name' => __( 'New Scent Name' ),
    'separate_items_with_commas' => __( 'Separate scents with commas' ),
    'add_or_remove_items' => __( 'Add or remove scents' ),
    'choose_from_most_used' => __( 'Choose from the most used scents' ),
    'menu_name' => __( 'Scents' ),
  ); 

  register_taxonomy('scent','product_listing',array(
    'hierarchical' => false,
    'labels' => $labels,
    'show_ui' => true,
    'query_var' => true,
    //'rewrite' => array( 'slug' => 'scents' ),
  ));
}

I also have another custom taxonomy of "scents" that I'd ideally like to have some kind of friendly url but I'm more open on this. I'd like to maybe access a list of all scents by going tomysite.com/products/scents but they don't have to be category specific.

Can anybody help me? I've been going crosseyed for hours. Thanks!

custom-post-types custom-taxonomy permalinks

ANSWER:-

Change slug in your post type arguments to products/%product_cat%, and slug in your taxonomy arguments to just products, then flush your rewrite rules. WordPress should now handle /products/my-product-cat/post-name/!

Now finally, we need to help WordPress a little with generating permalinks (out of the box, it won't recognise the permastruct tag %product_cat%):

function filter_post_type_link($link, $post)
{
    if ($post->post_type != 'product_listing')
        return $link;

    if ($cats = get_the_terms($post->ID, 'product_cat'))
        $link = str_replace('%product_cat%', array_pop($cats)->slug, $link);
    return $link;
}
add_filter('post_type_link', 'filter_post_type_link', 10, 2);

One thing to note, this will just grab the first product category for the post ordered by name. If you're assigning multiple categories to a single product, I can easily change how it determines which one to use in the permalink.

Lemme know how you get on with this, and we can tackle the other issues!