Just figured it out… It was the positioning of the define statement. I added the below above the /* That’s all, stop editing! Happy blogging. */ line define(‘FORCE_SSL_ADMIN’, true); define(‘FORCE_SSL_LOGIN’, true); Thanks!
Check all credentials in wp-config.php. And don’t forget about table prefix.
Here’s the way I have always done it. All of this code goes in functions.php. Of course this adds a whole new section to the user profile. add_action( ‘show_user_profile’, ‘be_show_extra_profile_fields’ ); add_action( ‘edit_user_profile’, ‘be_show_extra_profile_fields’ ); function be_show_extra_profile_fields( $user ) { ?> <h3>Extra Contact Information</h3> <table class=”form-table”> <tr> <th><label for=”contact”>Contact Number</label></th> <td> <input type=”text” name=”contact” id=”contact” … Read more
The problem is where you place the add_action of your wp_ajax_* Try to put it at the start of everything, and ensuring that it is being loaded in a /wp-admin/ route. Try your url: http://xxx/wp-admin/admin-ajax.php?action=your_action until it gives you something different than zero.
You’ve got your action/filter names slightly off: // For registering the column add_filter( ‘manage_posts_columns’, ‘custom_posts_table_head’ ); // For rendering the column add_action( ‘manage_posts_custom_column’, ‘custom_posts_table_content’, 10, 2 );
You can do that with jQuery. We can open this link in new tab/window by adding target=”_blank” attribute dynamically on link which has URL https://www.example.com. Here is the example function for that. function wpse_my_custom_script() { ?> <script type=”text/javascript”> jQuery(document).ready( function($) { $( “ul#adminmenu a[href$=’https://www.example.com’]” ).attr( ‘target’, ‘_blank’ ); }); </script> <?php } add_action( ‘admin_head’, ‘wpse_my_custom_script’ … Read more
After some fiddling and sparring with @t-todua I found the issue: With the Fetch API fetch call you must manually set to send cookies with a request. After setting the credentials option properly the cookies were sent and the AJAX endpoint recognized the current user. So the JS becomes: var msg = ”; // I’m … Read more
You need to register custom menus in your theme – https://codex.wordpress.org/Function_Reference/register_nav_menu You first need to register your menu in functions.php like so: add_action( ‘after_setup_theme’, ‘register_my_menu’ ); function register_my_menu() { register_nav_menu( ‘primary’, __( ‘Primary Menu’, ‘theme-slug’ ) ); } Then, where you want your menu to appear – usually header.php – you call the function: wp_nav_menu()
In my case, it ended up being some kind of adverse interaction in the nginx wordpress config that I had. Something about not passing along the naked arguments: location / { original line: try_files $uri @php; new line: try_files $uri $uri/ /index.php?$args; } And the associated upstream was wrong. Used the config suggested here: https://www.nginx.com/resources/wiki/start/topics/recipes/wordpress/ … Read more
You can use the function unregister_widget to remove widgets. E.g. you can remove the Calendar widget with: function my_widgets_init() { unregister_widget( ‘WP_Widget_Calendar’ ); } add_action(‘widgets_init’, ‘my_widgets_init’); To add widgets, use the Widgets API.