Login widget redirect ISSUE

Hi people,I have problems with the redirect function of the login widget.

Here some details:

• -not using any other profile plugins (example Buddypress)
• -already checked video tutorial and the Hidden field for “redirect” is not present
• -already checked WP Admin -> Appearance -> Widgets -> s2Member Pro Login Widget -> Redirection After Login
• -plugin up to date
• -WP up to date

For the moment I’m using a workaround, a function on my theme that redirects to homepage every user !not admin.

Any help is appreciated.

Thanks for the info. So you set the redirection after login in your widget settings, but it’s not working, is that it?

Could you try all these? Knowledge Base » Common Troubleshooting Tips

Hi,
Now it seems that the issue is affecting only the user of level 0. It works for the others (1,2)

The only point that I coul address was the one on the “s2Member files is missing or corrupt”. I had two tips on the server scan by S2 that told me to re-install s2member and s2member pro. I did it and re-scanned. Now I passed all the checks (all has a beautiful green check :) ).

Do you know why the login redirect doesn’t work for user level “0” ? Can you suggest a way to fix or a function to hack this?

Now I have a problem with the “Edit profile” link in the login widget. The %automatic% doesn’t work and the Custom link neither. It seems that is taking the “Membership options page” link. It has the same link now.

I solved the “Edit profile” link issue.

Now it remains the level “0″ redirect.

What’s your setting for the redirection after login in the widget?

Can you show me a screenshot of the widget’s settings and the Login Welcome Page’s?
[hilite path]Dashboard -> Appearance -> Widgets -> s2Member Pro Login[/hilite]
[hilite path]Dashboard -› s2Member® -› General Options -› Login Welcome Page[/hilite]

Hi, it seems to work now. Didn’t change anything for sure! by the way I had just taken the screen sohts:

http://www.screencast.com/t/wTS6XPRU95nV

http://www.screencast.com/t/PPqHxLFuy

I’m glad it’s working now! Maybe you were getting the cache and now it udpated with the correct settings. In any case, I’m glad you solved it. Thanks for the update! :)