After a bit of research I’ve fixed the problem I had with the redirect after logout. I’ve added this code to my functions file and it will use two filters to modify the default beahviour of wordpress after an user do the logout /* Logout URL Fix */ function custom_logout_url( $logout_url, $redirect ) { $logout_url … Read more
The closest is the WP Filesystem API, but that’s mainly intended for compatibility purposes, e.g. to enable files to be written when the only access is via FTP and direct filesystem write access is unavailable. Particularly: https://developer.wordpress.org/reference/classes/wp_filesystem_base/dirlist/ However, if you are not distributing this code and only using it for yourself or known environments, you … Read more
Before saving the options the first time get_option( ‘rtwhc_settings’ ) returns false as the option doesn’t exist. Saving values, deleting them and then saving again causes the value of get_option( ‘rtwhc_settings’ ) to be an array with the field names as keys, which have empty values. You can see this, if you var_dump() the option … Read more
You haven’t really given enough information to know what options you have within the software. You may be able to use a setting or hook into the loading of your forum. But, if not, perhaps you could use a combination of html, jquery and ajax to solve this. In your header/footer you could just hold … Read more
The custom role needs the read capability to view the backend. Example: $your_role = get_role(‘your_custom_role’); $your_role->add_cap( ‘read’ ); See: https://wordpress.org/documentation/article/roles-and-capabilities/#read Ideally, this should only be done once, e.g. when activating your plugin or theme.
WARNING: There be dragons ahead Changing the allowed innerblocks of the core/buttons block can be done, but it will make your life harder and introduce lots of new problems. Note that it would be faster, easier, and safer to implement a new buttons block that only accepts your custom block. To do this you would … Read more
Using the action hook delete_user is the right way to do it, but there are a couple of things missing. The main one being that you haven’t set up any $args for the WP_Query that fetches the custom post type entries with the user-id metakey of the deleted user. add_action( ‘delete_user’, ‘delete_his_posts’); function delete_his_posts($user_id) { … Read more
So you need to check if the values for a single user meta field are different or the same as the new values? If so, you don’t need to check the current values. Simply update the meta field regardless. It will be slower to check the current values and there is no benefit to doing … Read more
The code you provided is on the right track, but it’s possible that the issue you’re facing is related to WordPress’s admin-ajax.php handling. Here’s how you can modify your code to make sure you stay on the same page after submitting the form: Change the form action to the current page instead of admin-ajax.php. Form: … Read more
wp_remote_post has a configuration option called blocking. Its description says: Whether the calling code requires the result of the request. If set to false, the request will be sent to the remote server, and processing returned to the calling code immediately, the caller will know if the request succeeded or failed, but will not receive … Read more