Store the object temporarily in the database, but implement __sleep() and __wakeup() to avoid side effects. Alternatively, implement the Serializable interface and prepare the data in its methods. There is no need to store NULL values.
A more compact and WordPress-ish way, using url_to_postid(): function wpmp_switcher_exclusions_init() { $pid = url_to_postid( home_url( add_query_arg( array() ) ) ); if ( (int) $pid > 0 && get_post_meta( $pid, ‘_wp_page_template’, TRUE ) === ‘my-responsive-template.php’ ) { remove_action(‘init’, ‘wpmp_switcher_init’); remove_action(‘admin_menu’, ‘wpmp_switcher_admin_menu’); remove_action(‘wp_footer’, ‘wpmp_switcher_wp_footer’); remove_filter(‘stylesheet’, ‘wpmp_switcher_stylesheet’); remove_filter(‘template’, ‘wpmp_switcher_template’); remove_filter(‘option_home’, ‘wpmp_switcher_option_home_siteurl’); remove_filter(‘option_siteurl’, ‘wpmp_switcher_option_home_siteurl’); } } add_action( ‘setup_theme’, ‘wpmp_switcher_exclusions_init’ … Read more
The problem with calling flush_rewrite_rules() is that the rules instantly get regenerated, while your plugin’s hooks are still active. What I usually do, because it’s the simplest route to success, is delete the rewrite_rules option on activation/deactivation. The rules will then get regenerated on the next pageload instead of the current one: register_deactivation_hook( __FILE__, ‘my_plugin_deactivation’); … Read more
One way you could get the error message to your custom login page would be to use wp_login_failed hook. It could look something like this: add_action( ‘wp_login_failed’, ‘my_login_fail’ ); // hook failed login function my_login_fail( $username ) { //redirect to custom login page and append login error flag wp_redirect(home_url( ‘?page_id=4’ ) . “&login_error” ); exit; … Read more
You can pass an array of settings to the editor instance. For possible values please refer to the tinymce documentation, in your case ‘init_instance_callback’ might be helpful. https://www.tinymce.com/docs/configure/integration-and-setup/#init_instance_callback wp_editor(”, ‘sedemoeditor’, array( ‘tinymce’ => array( ‘init_instance_callback’ => ‘function(editor) { editor.on(“focus”, function(){ console.log(“Editor: ” + editor.id + ” focus.”); }); }’ ) ));
I went ahead and namespaced Stripe. Everything worked just great. And now I don’t have to worry about any one else’s Stripe library messing up my stuff. Original: namespace Stripe; New: namespace MyRadNamespace\Stripe; If anyone is interested in seeing how it’s done, feel free to browse my repo: https://github.com/Spokane-Wordpress-Development/Freezy-Stripe Cheers!
The key for that is the go_to method of WP_UnitTestCase class that you should be extending. It simulates parsing a url relative to the wordpress root (IIRC). You might need to first set posts and other info, and then call go_to to trigger the loop.
Your current function works pretty well, but it’s hooked on to a post update hook so you need to actually edit/update a post for it to run. If you want the posts to be modified automatically after the specified time then you’ll need to set up a scheduled event. I can think of two ways … Read more
Make sure your code runs in wp_enqueue_scripts action hook. Also checkout your script handle ‘owl.carousel.js’. In wp_script_is(), it is not the same than in the 2 later functions in which you enter it as ‘owl.carousel.min.js’. add_action( ‘wp_enqueue_scripts’, ‘enqueue_properties_scripts’ ); function enqueue_properties_scripts() { if ( ‘properties’ === get_post_type() ) { if ( wp_script_is( ‘owl.carousel.min.js’, ‘enqueued’ ) … Read more
You can not set cookies form site A that will be applicable on site B, therefor your “login by proxy” scheme will not work, and can not be made to work. In addition storing passwords in plain text is just a big no-no.