espo74

Ha!

I’m not holding my breath. Instead of doing the addition to functions.php I edited those lines in the plugin file and have had no issue. My thinking there was that if they ever actually did up date the plugin to include this functionality I wouldn’t have to remember to go back to functions.php to remove the code.

So far no issues with SFDC leads.

@curtisl my question is why not modify the plugin code directly instead of adding another filter to the functions file?

Modifying the plugin code directly and replacing ‘www’ with ‘webto’

This plugin has not been updated in over two years and one would assume any updates at this point would include this change in SF functionality.

@abdiyohan Thanks, but my question is why not modify the code directly instead of adding another filter to the functions file?

Modifying the plugin code directly and replacing ‘www’ with ‘webto’

			// Use test/www subdomain based on whether this is a test or live
			$sub = apply_filters( 'gf_salesforce_request_subdomain', ($test ? 'test' : 'www'), $test );

Question @abdiyohan: why add this to functions.php instead of just editing the file directly? This plugin has not been updated in over two years and one would assume any updates at this point would include this change in SF functionality. Seems as though this modification would save a little by not adding additional lines/calls to functions.php

• This reply was modified 7 years, 6 months ago by espo74.

Hi there–Any updates on this? THANK YOU @curtisl for providing this workaround.

@abdiyohan @webvixn Did either of you have success in validating this functionality?

Too bad. Future functionality request! also–to add an “active” tag when clicked.

thanks. great reply/support

Thanks Andy–super fast! Thanks.

Yes, I get this functionality…but some users are saying that they don’t understand this functionality. That it isn’t readily apparent to them.

Was hoping to be able to add/append a Toggle which removes the sort.

I would like to encourage this request as well. We have multiple clients logging in and they continually forget their passwords. While I am fine with locking them out for these errors we ran into the situation where a client had the same IP range as the main office. We were all locked out…It would be great to be able to specify ip address/range that were exempt from the rules.

OR–I would be fine with being able to manually add/edit the htaccess (or other) to create a list which is exempt to the plugin lockout rules.

i would pay instantly for the export to .csv from front end based on the search/filter.

In fact, i’ll pay you to send me some code that would handle that right now!

Thank you so much! Easy fix to implement and signing up for an API took all of 2 minutes (i have a slow connection). Thank you for being on top of this fix.

Thank you so much! Easy fix to implement and signing up for an API took all of 2 minutes (i have a slow connection). Thank you for being on top of this fix.

Hi–I’m experiencing this as well. Although I agree that one should never close a browser without logging out I cannot control how my users behave.

We have enabled the “Rename Login Page” feature and have set sessions to expire after XX amount of time. When a session does expire there are times when we receive the same “403 Forbidden” error that bramroos mentioned.

“Forbidden
You don’t have permission to access /wp-login.php on this server.”

Is there a setting to send the user to a custom page rather than receive the 403 error?

This happens for ALL user accounts. This happens in ALL browsers.

Ours just stopped working…not sure how some were having issues 10months ago and we are only just experiencing the issue.

Anyhow–
Hmm. Something went wrong with your Google authentication!
The error message was: 401: Unauthorized

Hopefully this plugin will be updated. it is fantastic.

Any updates on this–I’m having a really hard time with this right now as well.

sent some some beers your way. Thanks for all your help with all of these questions.