professor99

This one is definitely a bug. I think wpuf_user_edit_profile_form() should be $edit_profile->show_form() in wpuf-editprofile.php.

To change yourself find the file wpuf-edit-user.php and change the function wpuf_edit_users() to this:

function wpuf_edit_users() {
    global $edit_profile;

    ob_start();
    //if user is logged in
    if ( is_user_logged_in() ) {

        //this user can edit the users
        if ( current_user_can( 'edit_users' ) ) {

            $action = isset( $_GET['action'] ) ? $_GET['action'] : 'show';
            $user_id = isset( $_GET['user_id'] ) ? intval( $_GET['user_id'] ) : 0;
            $userdata = get_userdata( $user_id );

            switch ($action) {
                case 'edit':
                    //if user exists
                    if ( $user_id && $userdata ) {
                        $edit_profile->show_form( $user_id );
                    } else {
                        printf( __( "User doesn't exists", 'wpuf' ) );
                    }
                    break;

                case 'wpuf_add_user':
                    wpuf_add_user();
                    break;

                default: wpuf_show_users();
            }
        } else { // user don't have any permission
            printf( __( "You don't have permission for this purpose", 'wpuf' ) );
        }
    } else { //user is not logged in
        printf( __( "This page is restricted. Please %s to view this page.", 'wpuf' ), wp_loginout( '', false ) );
    }

    return ob_get_clean();
}

Hi ivomasterche,

Actually Tareq (the author of Frontend) has already fixed it in the github repository https://github.com/tareq1988/WP-User-Frontend and it is included in the development version I am working on http://wordpress.org/support/topic/frontend-updates-2rrr-fork.

Tareq would be very interested in a Bulgarian translation. He can be directly contacted via his website tareq.wedevs.com

Cheers
TheProfessor

See http://wordpress.org/support/topic/dashboard-denies-deletion-of-posts-you-are-not-the-post-author-cheeting-huh

Hi leoly,

If you want help you firstly have to provide specifics.

ie.

Server
——-
WordPress Version
Apache Version
PHP Version
MySQL version
Versions of all other installed WordPress plugins.
error messages

Client
——–
Platform (IBM PC/MAC etc)
Browser Version
error messages

All
—
Outline of how the error occurred plus steps to repeat it.

We may also ask later for a private email and test site URL and a login but don’t post these here as this is a public site.

Cheers
The Professor

PS. This plugin works fine for WordPress 3.3 -> 3.4.2, PHP 5.2.4 and higher, MySQL 5.0 and higher, and most popular browsers released within the last 3 years. WordPress 3.5 has just been released and this hasn’t been tested yet but should be fine. Some other plugins may cause problems with WP USer Frontend

This very much depends on how that plugin is filtering the categories.

Frontend uses two standard wordpress calls to get the categories.

For dropdowns it uses wp_dropdown_categories().

For checklists it uses wp_terms_checklist().

Try the various Frontend category display options in case Restrict Categories Plugin already filters one of these.

Else this is really a question for Restrict Categories Plugin support.

eg Does Restrict Categories Plugin filter wp_dropdown_categories() and wp_terms_checklist()? If not what WordPress category functions does it filter?

With that info you could code Frontend (or Restrict Categories Plugin) to suit