redrocksrover2

http://codex.ww.wp.xz.cn/Creating_Tables_with_Plugins

You should be able to use jQuery’s $.getJSON(my.json)

The jQuery documentation has a few good examples of traversing through the array to output HTML:
http://api.jquery.com/jQuery.getJSON/

If your URL has a callback function you’ll have to use JSONP.

Not sure why you’re trying to redefine the wp_hash_password function. Also not sure why you need to use a different global $wp_hasher setting. Also not sure why you need a separate function at all, but assuming you do, it seems like it should be as simple as:

function hashMyPassword($plainPassword)
{
     $hash = wp_hash_password($plainPassword);
     return $hash;
}

Then just pass the original, plaintext password into the function and insert the hashed result into your DB:

$hashedPassword = hashMyPassword('origPlainPassword')

But you should be able to do it simply with wp_hash_password($plainPassword)

It’s not clear what you want to do. Are you saying that you installed the plugin into WordPress and you want the output of that plugin to be visible to visitors of your site? Or are you saying that you developed a plugin that you want users of your site to be able to use and access when they create/alter content themselves?

If you’re simply trying to make the content of an installed plugin visible on your site and it isn’t visible, any number of things could be going on: the plugin may be outdated or coded poorly and thus not outputting content correctly, or you may need to insert custom tags or shortcodes to get the plugin to output as you expect, etc.

If on the other hand you’ve developed your own plugin and you want to make it accessible to users with the ‘subscriber’ role, that may not be possible depending on the permissions that are required to use the plugin. For example, if your plugin deletes data from your blog, users are likely going to need permissions that are more lenient than the role of ‘subscriber’ (but depending on what you’re trying to do, that might not be desirable or safe – context is everything).

@billibones: With regard to the jQuery library links, if you’re doing so, you really shouldn’t manually place jQuery scripts into your templates because they can really screw with WordPress’s own script management.

See here:
http://www.ericmmartin.com/5-tips-for-using-jquery-with-wordpress/

In short: use the wp_enqueue_script(), wp_deregister_script() and wp_register_script() functions to modify and/or add your own libraries, then let WP manage the dependencies. This could help to solve your insecure/non-SSL calls, and it’ll be particularly important if you’re using plugins that rely on jQuery, too.