Strange behaviour on Login Welcome Page (LWP)

#1

Hi all,
After pulling my hair out over the last couple of days, I thought it could be helpfull to other users why I had a hard time changing the Login Welcome Page.
Because I switched from Stripe (just for testing) to iDeal (typical Dutch) as the payment gateway I could no longer use the Stripe Pro Forms.

So I had to find a way to get all the custom information from my clients before actually purchasing something. For this I used a modified (added custom fields by hand, like ‘middleman’, ‘company name’, ‘address’ etc.) Stripe Registration Form. So far so good.
Registration works, but I wanted the Login Welcome Page (LWP) to act a little different than it is supposed to do, because after successful registration my client needs to go to the checkout and make a payment before proceeding.

I created a custom checkout page (ideal-checkout) and set that as the default LWP. And then things got weird.
Long story short:
Using a Pro Form Registration Form, the newly created user is automatically logged-in and redirected to the LWP.
But it seems as if after registration, the return url (the LWP) is hardcoded somewhere (with the addition of a very large parameter), because they never get redirected to the page I’ve set as the LWP (ideal-checkout). After two days of testing and testing, I came up with the idea to change the slug of the original LWP to ‘welkom’ and the slug of my new LWP, which was ‘ideal-checkout’, to ‘login-welcome-page’.
And that worked!

Conclusion:
Changing the LWP to a custom page within s2Member only works if you also change the slug of that custom page because the slug needs to be ‘login-welcome-page’.

I find this very strange.

#2

This is all very interesting, Toon! At what point in your setup, and how, does the user get the membership level to access content other than the LWP?

I find that strange too. Did you try the Special Redirection URL option for the LWP?

#3

Hi Tim,

After submitting the Registration Form they get Level 1 access and some CCAP’s, so they also get access to the LWP.
I’ve also tried the Special Redirection URL, but that didn’t work either.
Everytime they where redirected to the LWP with the slug ‘login-welcome-page’.
I found that out after temporarily setting the original LWP to ‘Draft’, and choosing another page as the LWP.
Things went wrong, because the url kept showing ‘…/login-welcome-page/’ which wasn’t available anymore. It was at that point that I realised that the slug of the LWP must always be ‘login-welcome-page’, so I decided to alter the slug of my new LWP. And that worked, as stated in my original post.

p.s.: I even checked the wp-options table at some point to see if changing the LWP came through, and it did. But still …

#4

That all sounds very odd. Have you checked for a theme or plugin conflict? If that’s not the problem, I’d suggest opening a support ticket to report it because I doubt that’s the intended behavior.

#5

Tim,

I will first test and see what happens with all additional plugins disabled and a generic twentywhatever theme.
To be honest, I don’t think it has something to do with my current WP configuration. But I just can’t believe that I’m the first and only one that stumbled on this one.
I’ll keep you updated.

#6

Just tested with all additional plugins disabled and using the twenty fifteen theme.
Same strange behaviour with the LWP.
Re-activated additional plugins and changing the theme back to my Genesis Child Theme, my initial WP configuration so to say.
And guess what?
I can select whatever LWP I want.

Problem solved, I think. But I still don’t know what went wrong in the first place?

#7

Seems it was wrong (missed, or bad info) settings, saved in DB. I saw this before with other plugins and themes…