Invalid S2member form configuration - example.com vs. www.example.com

#1

Hello,

I spent a while on different forums to identify the following issue:

The domain URL is well attached to custom URLs of forms (as in the general settings).

It works for “www.yourstage.live”.

But using only “yourstage.live” the error message “invalid form …” appears again.

I do not know where to fix this problem.

Thanks very much

Marc

#2

What form are you asking for?

#3

Dear Krum,
Thanks for your feedback.

It concerns PayPal Pro and Stripe Pro Form of s2member.

You may see the issue at www.yourstage.live compared to yourstage.live.

Thanks!

Marc

#4

yourstage.live is being redirected to www.yourstage.live so I can’t see the difference.

#5

Hi Jedi,

Thanks for your reply.

Unfortunatly it is depending on the browser and operating system.

Is there any way to force the redirecting from domain.com to https://www.domain.com?

#6

The “invalid form configuration” problem here is probably the “custom=” attribute in the shortcode. Try removing that. You still need to address your redirection issue, however. If something in your server set up is redirecting to “www” based on browser or operating system then it is not configured correctly as there is no reason to do so.

#7

My suggestion is to set redirect at server level (may need to ask your hosting for help), set both addresses in “Dashboard -> Settings -> General” to “www.” version, and then to re-build the s2M payment shortcodes.

#8

Good morning Jedi,
Good mornig Krum,

Might it be possible to remove the custom"" shortcode? If not needed this seems to be the easiest way.

On server level I might access the hosting records (CNAME, A(Addess, URL Redirect etc.).
Host Name - Record Type - Address.

How would a general redirection would look like to force only one version (www.domain.com)?

Thanks

Marc

#9

Yes, you can remove the custom="" attribute. Redirection is not my specialty so I will leave that for someone else to answer.

#10

I think you can not remove “custom” attribute, and it must contain at least the domain of your site, to be possible s2M to recognize the Paypal notification. Thus I suggest to re-build the s2M payment shortcodes after the problem with URLs are set, so it will put the right info in “custom” attribute.

Mark, the records you mentioned are DNS related. You (maybe) need settings of your WEB server software, thus I suggest you to call hosting admins. You (usually, as hosting customer) have no access to this area. Except you are on a dedicated server, but still it’s better to ask admins to help you.

Well, I am curious to know how exactly you fix the problem, so please post the solution later.

#11

Actually, you can remove the custom="" attribute or at least you could when I worked for WebSharks. If it exists, it must contain the domain, but if it doesn’t exist PayPal uses the domain. It exists to allow customization of the value.