How do I either, remove the sidebar programmatically OR change the template for that page programmatically? You can’t. Different areas on the frontend and how they’re styled are at the discretion of the person who coded the theme. There’s no standard WP framework for how to put them together and determine the layout. It could … Read more
So the ‘activate_plugin’ was a typo in the question. But even so, as a friendly reminder (for all of us), activate_plugin() is an existing function in WordPress. And you should use unique prefix in your custom functions (that are defined in the global scope): function my_plugin_activate_plugin() { … } register_activation_hook( __FILE__, ‘my_plugin_activate_plugin’ ); The Problem … Read more
Yes, WordPress checks for duplicate emails internally, but not duplicate usernames To test this I ran this several times via wp shell: wp_create_user( ‘test’, ‘password’, ‘[email protected]’ ); The result on the second attempt was: => class WP_Error#1962 (2) { public $errors => array(1) { ‘existing_user_email’ => array(1) { [0] => string(42) “Sorry, that email address … Read more
Your answer above was close but is should be add_action( ‘upgrader_process_complete’, ‘wp_answ_355114’ ); not do_action( ‘upgrader_process_complete’, ‘wp_answ_355114’ ); noting that this is only the case when a plugin is updated view WP plugin updates.
The problem is that, you have added extra white space before wp_ajax action. remove space from actions ‘ wp_ajax_my_action’ and ‘ wp_ajax_nopriv_my_action’. because of extra space before ajax request, showing the 400 bad request error. You should use : add_action(‘wp_ajax_my_action’, ‘my_action’); add_action(‘wp_ajax_nopriv_my_action’, ‘my_action’);
Currently you can not unset key because you can not find proper key from array. The issue is that you did $stamp = array($_POST[‘stamp’]); as array which is wrong. you have to remove array() from $stamp, so which look like $stamp = $_POST[‘stamp’];. then you can search value in column from array and unset it. … Read more
There’s an action hook, pre_post_update that gets executed just before updating a post. add_action(‘pre_post_update’, function($post_id, $data)){ if(!isset($_POST[‘date_start’]){ wp_safe_redirect(“post.php?post={$post_id}”); die(); } } I didn’t find any action that gets executed right before creating a post, however, I did find a filter that does and will work to validate data / abort with a redirect just like … Read more
The problem is that it’s sending JSON request headers, the old legacy Admin AJAX API doesn’t understand this. As a result these are the cause of the bad request: dataType: “json”, contentType: “application/json” Your endpoint might be able to handle that input, but WP’s admin AJAX handler can’t, so it never knows which action to … Read more
because you are using the wrong function. You should use: plugin_dir_url( __FILE__ ) . ‘images/bag.png’; Also remove the extra forward slash before images: /images
Try https://hackertarget.com/vulnerability-scanner/ it has many other testing tools as well, some are free and others paid.