heavymark

Looks like it was another plugin interfering.

Awesome, thanks rpb1001!

Just to add, this item is marked as “resolved”, however the issue still exists, and rather someone simply provided a temporary solution which is to lower your google account security to get this plugin which uses lower security methods to work. I’m grateful for the suggestion since it buys us sometime while the plugin author fixes the issue or time to find an alternative plugin.

Would be great to hear an update from the plugin author on when the plugin will be updated to support googles security protocols so that we can re-enable full security in our google accounts, also since that Google setting is most likely temporary during the transition and I imagine Google eventually will remove the option entirely in the future.

While that is certainly a great temporary option for all of us, would be great to hear a timeline on when a long time solution will be available. That is when the plugin will be updated to use the proper secure method so we can re-enable higher security in our Google accounts again. Or does anyone have any recommendations on alternative plugins that use the proper required Google security protocols?

I’m having the exact same issue. It looks like you posted this under plugin hacks though rather than on the actual plugin support page which is probably why it hasn’t received any replies. I’ve just posted their on the plugin support page, so hopefully they will have a response soon.

The plugin currently uses “SoapClient” so will have to have that enabled on your server.

The other option would be that the plugin is recoded to not rely on SoapClient. The developer may eventually do that if enough people request but doubtful. Or switch to a host that supports it.

What version of PHP are you using? As long as it’s relatively new it should be fine. The link I sent was instructions for 5.3.5 but if your using an older version you’d simply have to google enable soap on php (insert your version here). Or google how to enable/install a module on your particular version of php.

Yes, you have to compile php on your server with Soap extension. Several people on the form have noted the blank setting issue but he continues to assert that the issue is fixed when it’s not. Until he does, if you have root access to your server I followed these instructions and now the extension works:

https://kb.mediatemple.net/questions/1947/Configure+PHP+with+SOAP#dv

Unfortunately this was not resolved. *Noted in the other post as well.

When enabling error reporting it shows:

Fatal error: Class ‘SoapClient’ not found in /var/www/vhosts/ma-smartgrowth.org/httpdocs/wp-content/plugins/gravity-forms-salesforce/developerforce/include/SforcePartnerClient.php on line 44

According to Google it seems that that means on the server we have to enable “Soap Client” in Apache. This was not noted to my knowledge anywhere on your plugin requirements.

Same issue here.

The site is installed locally and works fine. An exact copy of the site on a DV server however the settings page is blank. Screenshot here: https://cl.ly/LKos.

And yes, I like the others reporting the problem am using a fresh copy of 2.1.1.

To note, I looked in my local computer’s error logs and that last time it showed, “[08-Nov-2012 21:10:48 UTC] PHP Warning: extract() expects parameter 1 to be array, boolean given in /Users/myname/Sites/example.org/app/wp-content/plugins/gravity-forms-salesforce/salesforce-api.php on line 536”

Was on Nov 8th. So while the 2.1.1 may have fixed that one warning, the bug that prevents users from accessing settings on some live servers (such as mine and the other posters still exists).

And I do not have the members plugin installed.

Wait think I figured it out. While one would assume the highlighted “disabled” button or “deploy” button would refer to the enabling or deploying the plugin, I’ve discovered its referring to disabling or deploying preview mode. Very confusing interface for that section. The button should be called “disable preview” and “enable preview” etc.

Unknown, but it’s happening now in the latest beta version. It may be a bug that was overlooked in the stable version.

To add, when clicking that arrow a red line appears that shouldn’t.

Just changed the new page I created to have the same slug as the title I entered on the reading page and now the dropdown appeared. And that dropdown now lets me create new pages from there.

Based on trac it looks like this page is being worked on which is why it’s probably currently buggy. I’ll check back later!

Also wondering if this page is broken: https://cl.ly/K77M using 3.5-beta1-22204.

The dropdowns to select a page for the static homepage appear to no longer be there or for the blog post. It allows you to type a title name but not select a page. Clicking save reports an error even if you try typing the name of a page that exists.

Thanks!