As per WordPress Codex its best to register and queue your scripts with the hook dedicated for them, even if you want your script to be added to footer. So the correct way of doing it will be: function jupload_scripts() { wp_enqueue_script( ‘jquery-ui’, ‘http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.12/jquery-ui.min.js’, array(‘jquery’), ‘1.8.6’, true ); } add_action( ‘admin_print_scripts’, ‘jupload_scripts’ );
Yes there is. Save this code as plugin and activate one. Plugin will lock all pages that has children from edit. <?php /* Plugin Name: Lock parent pages form edit Plugin URI: Description: Version: 0.1 Author: Alexey Selin <[email protected]> Author URI: http://wordpress.stackexchange.com/users/7314/alexey */ function lock_parent_pages_from_edit( $capauser, $capask, $param){ global $wpdb; $post = get_post( $param[2] ); … Read more
You can leave it or change it, it doesn’t matter as long as the theme files use the correct handle for the function. I would choose one name and convert the second version so all use the same name to keep it simple.
For a fully-working solution, you will need to modify certain hard-coded urls in core files, which is not fun to have to do each time WP is upgraded. One easier option is to protect the wp-admin folder with an .htaccess file. You could basically deny all IP addresses and whitelist the few IP’s that you … Read more
Well, someone has to be hosting it, so I recommend tracking them down. I’ve taken the liberty of doing this for you (using WhoIsHostingThis?). Your host is IX Web Hosting, contact their customer support and see if you can either get them to do the upgrade for you or, preferably, get them to give you … Read more
There is no function file in “wp-admin” folder, you do not need to edit that folder. WordPress has Plugin api to do that, http://codex.wordpress.org/Plugin_API/ Create a plugin and write function in your plugin file.
wp_enqueue_scripts is only fired on the front end, and not on admin screens. For loading scripts admin side, you’ll want the hook admin_enqueue_scripts. Passed as an optional argument is the page hook. (Examples include edit.php, for the admin edit page (which lists pages/posts/ cpt posts), post.php when editing a post/ custom post type and post-new.php … Read more
Notices won’t trigger a server 500 error. However, “fatal errors” will. From your logs above: Fatal error: Class ‘Memcache’ not found in /var/www/wordpress/wp-content/plugins/flexicache/FlexiCache/Store/Memcache.php on line 63 This means you’re running a plugin that depends on Memcache and your local system doesn’t have Memcache support. Disable or remove the FlexiCache plugin, or install Memcache. One other … Read more
Whenever in doubt about the functioning of WordPress functions, consult the Codex: http://codex.wordpress.org/Function_Reference/register_post_type There, we can see that when registering a post type the supports argument has many options, one of them custom-fields. So, this would enable the CF box for the CPT: $args = array( ‘labels’ => $labels, ‘public’ => true, ‘publicly_queryable’ => true, … Read more
WordPress like most CMS websites has 2 types of users – unknown users and authenticated (logged in users). In fact pretty much every website or analytics systems tracks users based on this user profile. Unknown users can only browse the front end and have no access to wp-admin. This is to be expected, otherwise explain … Read more