Specifically editing the code you provided in the original question: add_filter( ‘nav_menu_link_attributes’, ‘wpse121123_contact_menu_atts’, 10, 3 ); function wpse121123_contact_menu_atts( $atts, $item, $args ) { // The ID of the target menu item $menu_target = 123; // inspect $item if ($item->ID == $menu_target) { $atts[‘data-toggle’] = ‘modal’; } return $atts; }
It’s actually not too bad to do what you’re asking. This should take you about an hour to do your first one, and 10 minutes to do subsequent ones. Ultimately what you’re going to do is create a TinyMCE plugin. Here’s what you should arm yourself with to start: General guide to creating a tinymce … Read more
To the best of my knowledge, and having heard Nacin say it explicitly, no deprecated function has ever been removed from WordPress to date. No guarantees for the future, but it’s never happened yet. Still, avoid deprecated functions.
I think the only thing missing here is that you need to move add_action(‘wp_ajax_nopriv_ajaxlogin’,’ajax_login’); outside ajax_login_init. That code registers your Ajax handler, but when you only run it on wp_enqueue_scripts, it’s already too late and wp_ajax_nopriv_ hooks are already run. So, have you tried something like this: function ajax_login_init(){ if ( ! is_user_logged_in() || ! … Read more
Could you place the action (ajaxConversion) in your Data and check? jQuery.ajax({ type:”POST”, url: ajaxurl, data: { action: “ajaxConversion”, amount: amountToConvert }, success:function(data){ alert(data); }, error: function(errorThrown){ alert(errorThrown); } });
Well the second bit of code is technically the correct way to do it. However, at the end of the add_settings_field() you can pass arguments. Please view the WordPress Add_Settings_Field function reference. This will help you in getting the best understanding of how the add_settings_field() function really works. Now, with that said, you could use … Read more
Disable all plugins and switch to the default theme. It should be gone now. Then enable each addon step by step, until the problem comes back. You know the source now, let’s say a plugin. The plugin calls probably wp_enqueue_script too early. Find all occurrences of that function, then make sure they are bound to … Read more
You should run the code after theme setup. function osu_twentyten_continue_reading_link() { return ‘ <a href=”‘. get_permalink() . ‘”>’ . __( ‘Read on <span class=”meta-nav”>→</span>’, ‘twentyten-child’ ) . ‘</a>’; } function osu_twentyten_auto_excerpt_more( $more ) { return ‘ …’ . osu_twentyten_continue_reading_link(); } function my_child_theme_setup() { remove_filter( ‘excerpt_more’, ‘twentyten_auto_excerpt_more’ ); add_filter( ‘excerpt_more’, ‘osu_twentyten_auto_excerpt_more’ ); } add_action( ‘after_setup_theme’, ‘my_child_theme_setup’ … Read more
Checking to see if built in WordPress functions exist before calling them is for backward compatibility which IMHO is not needed. So if you see if ( function_exists( ‘register_nav_menus’ ) ) the theme author is supporting versions earlier than 3.0. You still sometimes see if ( function_exists( ‘dynamic_sidebar’ ) ) Why? I couldn’t tell you … Read more
From the Codex … Should the permastruct be prepended with the front base. (example: if your permalink structure is /blog/, then your links will be: false->/news/, true->/blog/news/). Defaults to true