This is challenging, because showing something would require page not to be private. It is more common to leave page public, but make it produce conditional output depending on if user is logged (is_user_logged_in()) in or other criteria.
There are two options to use forms in a dashboard widget: Use the parameter control_callback. See the Codex wp_add_dashboard_widget( ‘my_id’, // $widget_id ‘my_name’, // $widget_name ‘my_render_widget’, // $callback ‘my_control’ // $control_callback ); function my_control() { // print some form elements, WordPress will handle the <form> tag. } If you want to use a form in … Read more
No, not really. You’re assuming the function that called wp_insert_post() has already performed those checks. But wp_insert_post() may be used in other pages too, not just the edit page, by plugins, or even themes (many of them with security holes). That’s why you should ensure that your code runs only where you want to by … Read more
WordPress is inherently quite secure software, because of open source, extremely wide installation base and reasonably fast security updates. There is no such thing as security plugin that magically increases security, while causing no conflicts. Security plugins either act to monitor situation and inform you after the fact (important, but it’s not prevention measure) or … Read more
$wpdb->prepare() doesn’t actually fully support sprintf() placeholders. From the Codex: The query parameter for prepare accepts sprintf()-like placeholders. The %s (string), %d (integer) and %f (float) formats are supported. It’s not entirely obvious from that but the argument swapping formats (e.g. %1$d) are not supported (in any case you have the incorrect syntax: it should … Read more
As @toscho says you need an endpoint. Note code is untested. /** * Flush rewrite rules */ function install_my_plugin() { my_plugin_endpoint(); flush_rewrite_rules(); } register_activation_hook( __FILE__, ‘install_my_plugin’ ); /** * Flush rewrite rules */ function unistall_my_plugin() { flush_rewrite_rules(); } register_deactivation_hook( __FILE__, ‘unistall_my_plugin’ ); /** * Add the endpoint */ function my_plugin_endpoint() { add_rewrite_endpoint( ‘action’, EP_ROOT ); … Read more
Let’s imagine you got a dropdown like the following // The template tag that you place in your … template function WPSE116198PerPageSelect() { $selected = <?php <select name=”woo_per_page” id=”woo_per_page” size=”3″> <?php foreach ( array( 24, 36, 48 ) as $val ) { ?><option <?php value=”<?php echo $val; ?> selected( get_query_var( ‘woo_per_page’ ), $val ); ?>> … Read more
This is not a WooCommerce question. Once the user is registered you use WordPress functions to verify whether the user is logged in and to retrieve the user’s info. Assuming you are saving the user info correctly, then this should show a user’s first name to the user, and a generic message to a non-logged-in … Read more
The “Customizing checkout fields using actions and filters” page in the WooCommerce Codex might help you.
As an alternative to editing the meta template, you can prevent the meta information from being displayed on single product pages at all. This can be handy if you also don’t want to display the SKUs. Here is how to do it: remove_action( ‘woocommerce_single_product_summary’, ‘woocommerce_template_single_meta’, 40 ); It goes to your functions.php.