The class WC_Checkout is assigned to a member of the class Woocommerce. So maybe something like this could work: add_action( “plugins_loaded”, “wpse_91273_custom_checkout”, 999 ); function wpse_91273_custom_checkout() { $GLOBALS[‘woocommerce’]->checkout = new Custom_Checkout; }
You can echo the return value of a function: <a href=”https://wordpress.stackexchange.com/questions/102196/<?php echo plugin_function(); ?>”> But without seeing the actual function, there is no way to give a more specific answer.
above code does not works for me, is not correct or any mistake from my side? And it didn’t work for me either. Because it throws this fatal error: PHP Fatal error: No code may exist outside of namespace {} in … And that’s because the PHP manual says: No PHP code may exist outside … Read more
You should use the template_redirect action instead of wp_loaded. It’s a good practice add die(); after wp_redirect() to.
You’re missing a ‘ in your code and your function name is different. function my_maybe_add_redirect( $entry, $form ) { wp_redirect( ‘https://www.google.com/’, 301 ); exit(); } add_action( ‘admin_post_submit_images’, ‘my_maybe_add_redirect’, 10, 2 );
There can be a case that theme implements hooks via do_action(“action_name”) but it’s not forced to bind actual actions to it, as theme’s developers might just did it to make theme more extensible, and in fact never use it inside theme. So you can just bind your own code via add_action(“colormag_before”, “your_function_name”) in a child … Read more
Think about what you’ve written: The acction hook stop working if i move it from plugin file to theme’s functions.php file And: bp_includes is buddypress action and hooked on plugins_loaded The problem is that the code stops working when you move the code to functions.php, which is a theme file. The theme loads after plugins … Read more
Here is nicely described what and when is loading and why. I recommend also this awesome plugin Query Monitor that helped me also to fix performance issues. in short: muplugins_loaded registered_taxonomy registered_post_type plugins_loaded sanitize_comment_cookies setup_theme unload_textdomain load_textdomain after_setup_theme auth_cookie_malformed auth_cookie_valid set_current_user init widgets_init register_sidebar wp_register_sidebar_widget wp_loaded parse_request send_headers parse_tax_query parse_query pre_get_posts posts_selection wp template_redirect wp_default_scripts … Read more
I was looking at the wp-login.php file and noticed that there’s an action location : <?php do_action(‘login_footer’); ?> available… to use. So add_action(‘login_footer’, ‘my_addition_to_login_footer’); function my_addition_to_login_footer() { echo ‘<div style=”text-align: center;”><a href=”#”>link</a></div>’; }
The publish_{post-type} action is triggered only when the post change from any post status (not published) to published; for example, if the post is already published and you edit it, the publish_{post-type} action is not triggered. I think you need to hook your function to save_post_{post_type} action, which is triggered every time a post is … Read more