lllor

Just doing those changes “on-the-fly” using the inspector fixes the issue

Wrong bootstrap classes. You’re actually dividing the row in three columns.

Replace col-md-4 with col-md-3 for each widget areas in footer-widget.php

EDIT: There’s also an empty space between widget area 3 and 4. You should remove it.

• This reply was modified 4 years, 2 months ago by lllor.

I tested on Firefox 80.

Btw, it works also on Chrome 85, IE11 (windows). Also on Chrome and Samsung Internet Browser for Android (latest versions).

Ops, wrong suggestion. Priority of the remove_action must be the same of the add_action command.

But…You cannot successfully remove the action before it has been added. So, if you’re executing remove_action before add_action, it doesn’t work.

Are you working on the child theme of functions.php? Well, it is executed before extras.php

wrong class…

.navbar-brand > a > img {
border-radius: 50%;
}

Try to set priority to 1.

Yes, it’s in italian.

Still happening with 5.0.3.1.

any opinion?

Cheers

add_filter('pods_meta_groups_get','pods_group', 10, 3);

function pods_group($groups, $type, $name) {
    
    global $user_id;
    
    if (is_super_user($user_id) ) {//custom function that verifies if the user has managing capabilities
        $groups[0] = null;
    }
    
    return $groups;
}

that works in profile.php and user-edit.php (which define a global $user_id). I’m not so sure in terms of software architecture is the right solution, but it works.

I don’t think it’s related to the current user, but to the user’s usermeta I’m (as admin – the *current* user) inspecting. I can (as admin) edit its custom fields (and that’s good!).

Anyway, thanks for the hint: I will look at pods_meta_groups_get to see if I can manage some sort of workaround. In case of success, I will write here the solution.

Cheers.

btw, I would not rely on is_super_admin since it verifies only if the user can delete other users (which sometimes is true also for non-admin roles). See ticket 4738 https://core.trac.www.ads-software.com/ticket/47338 (opened by me…)

Thanks for your reply, Yes I’m comfortable with php. Which pods hooks should I aim?

I’m not expert of pods internals, but I don’t get why I must look at the current user, shouldn’t I control the user I’m creating?

any suggestions?

cheers

Thanks for the pull request. Nobody replied to the issue on github, therefore I opened the issue in this forum…

Thanks!

https://github.com/GM-Alex/user-access-manager