Andrei

Hi,

I understand what happened, and this is a downside of editing plugins or themes, then doing updates.

WordPress is prepared to handle this though, and this kind of problem can be avoided in the future.
The solution is to use WordPress hooks, by adding the custom code in a separate file, outside the If Menu plugin. Custom code can be added in _current_theme/functions.php or a new plugin, and this hooks onto If Menu plugin functionality and extends it. When If Menu has an update, the plugin itself is updated, but the extra code is never touched. This is the standard way to extend plugin functionality, and not editing plugin files.

https://ww.wp.xz.cn/plugins/if-menu/#how%20can%20i%20add%20a%20custom%20visibility%20rule%20for%20menu%20items%3F

Hope this helps,
Andrei

The latest version of the plugin uses new code from Restrict Content Pro now. If there was a problem with this integration, it should work smoothly after updating If Menu to latest version

Hi,

Thanks for letting us know about this. We’ll update the code for Restrict Content Pro integration in the next plugin update, due in a few days.

Cheers,
Andrei

Hi,

At the moment, after a successful login the plugin can do 2 redirects:
– checks URL parameter redirect_to, to redirect to page that requested authentication
– if first check is empty, is redirects to homepage

There’s no option to redirect based on type = login OR register, but this sounds like a good idea.

We’ll add this option in a future plugin update, and let you know when it will be available.

Cheers

• This reply was modified 5 years, 1 month ago by Andrei.

The choice to not open popups is made intentionally for this plugin, as custom embedded code would be needed from Google/Facebook/etc to open those popups.

Usually the custom JavaScript code is embedded in login page even if the Facebook/Google button would not be used, and sending analytics data to those providers without any interaction.

This is just an example that’s in the news https://www.vice.com/en_us/article/z3b745/zoom-removes-code-that-sends-data-to-facebook

The OAuth authentication standard works by default without the popups, using only the link redirects, and the person that signs in is always redirected back to website in case of success or failed authentication.

Hope this helps

Noticed what causes this, I guess the Twitter app requirements have changed recently.

For Callback URL, fill the website url like this:
www.website.com/wp-login.php
instead of
www.website.com/wp-login.php?quick-login=twitter

The question mark and everything after it should be removed. This is the only change needed, and the plugin should work as expected.

I’m updating the plugin today so that the Twitter instructions show the correct info & url.

This is not fixed in the latest plugin update.

There was a issue related to G Suite hosted domain, and now Google login should work fine for both regular accounts and G Suite domains.

Cheers

Hi,

Some plugins or themes are not prepared for this change in WordPress 5.4

New hooks let you add custom fields to menu items

and break functionality for menu items in other plugins.

There’s no ideal solution for this yet, but you can try one of these:
– downgrade to WordPress 5.3
– disable the theme/plugin that causes this conflict
– contact the theme/plugin developers to ask about updating it
– and as “braehler” mentioned, the code that causes this can be commented out. You can search the theme/plugin directory for wp_edit_nav_menu_walker and delete/comment-out that line of code

Hope this helps