cybecom

Hi all

I also have support working on it but I did notice last night that hovering over the ? help for the Site Key said to enter a V3 Site Key and hovering over the ? help for the Secret Key said to enter a V2 Secret Key. I only entered the new V3 keys. Somehow the plugin script is confused and because half of it is expecting a different key, it is reporting a key invalid.

What I haven’t done is deactivate the plugin and delete it completely before reinstalling. I will be patient and wait for support (when they come back online) to manage that if they need to. It could be that an underlying permission problem has prevented one of its files updating which is why it’s in this half/half state. This (or something similar) might explain why only people who have moved from V2 to V3 recaptchas are having the problem. (So a complete delete of the plugin and reinstall may resolve that but be careful as you will lose forms – and probably any historic data captured by those forms – and your shortcodes will end up with a different number.)

Regards
Michelle

• This reply was modified 4 years, 11 months ago by cybecom.
• This reply was modified 4 years, 11 months ago by cybecom.

Tomas

I am getting that same error too.

ERROR for site owner: Invalid key type

Strange thing is… if v3 is secret, I wouldn’t have thought it would display any box at the bottom let alone an error.

Forgot to mention that the form (both the old one and now the new one) have V3 recaptcha set.

I am having the same issue. I tried a few days ago. Deleted the domain from Google ReCAPTCHA. Added it back in selecting V3. Generated new keys. Copied and pasted them into my form settings to no avail.

Today I did that all over again BUT I also created a new form first and am trying that but also to no avail. I keep getting (at the bottom): ERROR for site owner: Invalid key type when you go to the form.

The page did used to have a V2 form (which had stopped working properly… I was getting lots of spam through it).

The following images (part erased for security) show my keys in both Everest and Google:

Everest

Google

I think there is some sort of conflict so WordPress is simply rejecting (or not interpreting) the Additional Header information. This suggests some sort of problem parsing that syntax but it is strange it parses everything else fine.

Hi Takayuki – Everything shown in the screen grab with [email protected] replaced with my client’s email address which is also set up in their cpanel. Note there is some extra text after the [your-subject] for the Subject field. Eg.

[your-subject] – From the Restore Fitness and Wellbeing Website

And to confirm the syntax of the Additional Headers, I have copied and pasted exactly:

Reply-To: [your-email]

Regards

Michelle

Thanks @shariftk, @grex22

I hadn’t seen the https://www.ads-software.com/support/topic/salesforce-new-endpoint-with-the-summer-17-release/ post. Probably doing the change in functions.php of the child theme would be a better option although I guess it is six of one and half a dozen of the other in terms of what happens if there is a plugin update.

Further to the above, I am using the Web-to-Lead connection type.

There is lots of help here:

https://katz.co/plugins/gravity-forms-salesforce/

OK – I have just spent a couple of hours playing with this and have discovered that when I created a new form from scratch, it doesn’t duplicate. The only visual differences that I can see are:

1) For the confirmation message, I used a message and not a screen redirect; and
2) For many of the fields, I used the advanced field types instead of basic ones.

My programmers did set up a form that does have the redirect and that only submits once. And they also used the basic field type. But that form does some auto-populating behind the scenes so maybe in the process of that, it clears whatever the issue is.

It’s like the form goes through a double submit process when it duplicates; the first is correct but the second has the email address absent.

Anyway, my double submit / duplicate lead issue is resolved even though I don’t fully understand how.

Thanks

Hi there

I too am having the same problem and am using the following versions:

WordPress 4.3.1
Gravity Forms 1.9.15.3
Gravity Forms Salesforce Add-On Version 3.1.2
PHP Version 5.5.30
MySQL Version 5.5.46

I have only selected the Web-to-Lead option.

I get two leads in Salesforce; the first with all the fields correctly populated and the second with the same information minus the email address.

I have checked and made sure debugging was off (thought this might have had something to do with it).

Has there been a solution?

Thanks

All right but we are getting ahead of ourselves and off on a tangent.

A few point releases back, the plugin worked by taking the featured image and using that. Now it does not. The featured image is ignored.

I am only guessing it has something to do with og:image because it is not being set with the app even though other tags are being set. However, this might be a red herring.

The issue is that the plugin used to work by using the featured image as the image to post to facebook but now it uses the first image on the page.

How can this be fixed as it used to work?

I have tried to make the featured image one that is 280×280 and it makes no difference.

Thanks!

I think it is 180×180 but surely it isn’t that pedantic if specified?

Also, at the moment, the app is not setting the og:image tag anyway. It sets about five different og tags but not the image one. If I use another plugin I end up duplicating some of the tags and then all seem to be ignored.

This was absolutely working with the featured image pulled from the normal media image gallery recently. Now it is not. I could set a featured image and know with 100% certainty that it would appear as the image for the Facebook post. Now I can’t. The only thing I believe has changed since it was last working are two or three point releases of the plugin. In my case, there is no randomness about what image it pulls. It pulls the first image it sees on the page post which happens to be in my sidebar and not what I want to use. I’ve tried other plugins that set the og:image but they are ignored and the debugger picks up duplicate errors. For a whole lot of obvious reasons, I am reluctant to use my own code to solve this issue.