hmcody

I managed to get everything working, but I would still like to know what the <# #> tags relate to.

• This reply was modified 1 year, 6 months ago by hmcody.

What I ended up doing was adding a role of “former” and using the um_after_user_status_is_changed_hook to change the role to former when someone is made inactive. The directory can then be filtered by role.

I am looking for the same option, preferably as an admin filter rather than one selectable by general users.

I have run into the same problem with two sites that I am converting from Oxygen Builder to Guttenberg. Imported Classic menus show perfectly in the editor but not on the front end. I used Daniel’s workaround and it fixed the problem.

Thanks!

Thanks for creating and posting the link to the plugin. It seems to do the trick!

I am using UM version 2.3.2 and the option is Enable the “Content Restriction” settings for the Gutenberg Blocks It is found on UM Settings -> Access -> Restriction Content right under the Restricted Access Message box.

I don’t see “Allow Gutenberg Block restrictions” anywhere in my settings, though they sound like the same thing. Perhaps we are working on different versions?

I was having the same problem. Part of the issue was that I needed to explicitly Enable Content Restriction for Gutenberg Blocks on the Access tab in UM settings. The Restrict Access toggle was then available for the menus. Unfortunately, the settings which had been previously set on the menu did not seem to carry over, so I still have to re-secure the menu.

Nor should you have to chase it down!

Turns out the real issue is with Relevansi and I can fix it by turning it off for Admin Searches. There IS a problem with Elementor, but given what bad luck I have had in the past dealing with their support, I probably won’t bother reporting it.

Thanks for looking at this.

Looks like it is something in Elementor. It has a function (filter_wp_link_query_args) that throws and error when wp_link_query_args is invoked.

Duh! That did the trick. Thanks.

Which leads me to believe that I have a theme or plugin conflict in my full site, since I don’t have the typo there.

Sorry, @futureyoon, I thought I had replied to you before. This is the code I use. The commented out line was what was causing the problem. Once I removed ‘index.php’ everything started working again.

//Add Login/Logout to front-end menus
add_filter(‘wp_nav_menu_items’, ‘add_login_logout_link’, 10, 2);
function add_login_logout_link($items, $args) {
ob_start();
//wp_loginout(‘index.php’);
wp_loginout();
$loginoutlink = ob_get_contents();
ob_end_clean();
$items .= ‘

• ‘. $loginoutlink .’

‘;
return $items;
}

Update: The redirect was included in my login/logout code. Once I took that out, everything is working as it should.

I am running into the same problem after updating to 5.7.1. One thing I noticed is that if I click on my login link on my main menu, it now appends
“?redirect_to=index.php”
after the login url slug. I don’t think it was doing that before. Everything is fine for accounts that have access to the backend, but accounts that only have frontend access are sent to the 404 page.

• This reply was modified 3 years, 10 months ago by hmcody.
• This reply was modified 3 years, 10 months ago by hmcody.

I ended up not using your plugin to do this, so I no longer have what I did available.

Thanks for getting back to me, though.

I’ve solved the immediate problem by eliminating to ability to select another file.

But I would still be interested to know where I could cancel the save if I need to do so.