WordPress listens to both $_GET and $_POST when parsing a request. If your form input names are conflicting with native query parameters, you’ll send WordPress on a wild goose chase (and most likely end up with a 404). For your leisure, I’ve kindly listed them here – if any one of your form inputs uses … Read more
The page template for custom post type is not saved because it is checking whether the post type is “page” – it is not implemented for custom post types yet. The drop-down for the page templates was completely removed in 3.1. This is my way how to deal with it: /* Define the custom box … Read more
Here is a solution to remove that metabox from the edit page – this solution also assumes that the editors don’t have access to edit themes. add_action( ‘admin_menu’, ‘restrict_access’ ); function restrict_access() { if(!current_user_can(‘edit_themes’)){ remove_meta_box( ‘pageparentdiv’, ‘page’,’normal’ ); } } Hope this helps
Use wp_enqueue_scripts instead on init. This will ensure you the template is already loaded. add_action(‘wp_enqueue_scripts’, ‘maps_scripts’); Or you try to check the template using get_page_template_slug() instead of is_page_template: $tmp = get_page_template_slug($post_id); // provide page/post ID if(‘page-about.php’ == $tmp) { // enqueue scripts here } Note that you don’t need to register scripts before enqueueing them. … Read more
If you’re wanting to enable the Page Template dropdown for a custom post type, you have to enable support for “page attributes” when you define your CPT. You should currently have something like register_post_type(‘foo’, array(‘labels’ => array( … ), ); You need to add ‘supports’: register_post_type(‘foo’, array(‘labels’ => array( … ), ‘supports’ => array(‘title’, ‘editor’, … Read more
Your code will only display a list of your posts if the page that is using that template is set to be the Posts Page (in admin settings). If you want any other page to display a list of posts, then you need to write a custom query inside the template. E.g. using WP_Query: $args … Read more
Daniel, exclude parameter doesn’t accept array. Use your code this way: $exclude = []; foreach(get_pages([‘meta_key’ => ‘_wp_page_template’, ‘meta_value’ => ‘page-templates/page-noindex.php’]) as $page) { $exclude[] = $page->post_id; } $args = array( ‘exclude’ => implode(“,”, $exclude), ‘title_li’ => ”, ‘sort_column’ => ‘menu_order, post_title’, ‘post_type’ => ‘page’, ‘post_status’ => ‘publish’ ); wp_list_pages($args); I think you can refactor it … Read more
In WordPress, you should use wp_enqueue_script() to load JavaScript files, and wp_enqueue_style() to load CSS files, and the functions should be called using the wp_enqueue_scripts action hook. Additionally, the theme needs to call wp_head() (in header.php) and wp_footer(). And to enqueue a script only on specific pages, you would use a conditional tag like is_page() … Read more
To make this work with WordPress use the AJAX API. While that technically refers to Javascript it will handle any request if the appropriate values are sent. You would create a callback like this one form the Codex: add_action(‘wp_ajax_my_action’, ‘my_action_callback’); function my_action_callback() { global $wpdb; // this is how you get access to the database … Read more
I advice to use the wp built-in ajax. it allows avoiding many problems and brings many benefits. an example that I wrote to illustrate the 2 approches: Dynamically changing navigation links (next and previous) via AJAX I am here to provide with explanations good luck