Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Nick Ciske

    (@nickciske)

    The plugin doesn’t use login.salesforce.com. It’s only interaction with SF is via the web to lead API endpoint:
    https://www.salesforce.com/servlet/servlet.WebToLead

    That should work with any SF account with the organization ID set correctly.

    Stony Grunow

    (@stonydaddydonkeylabscom)

    You can test if this is an issue by creating a standard web to lead, and check what the URL is in the form. To create a web to lead, follow

    https://help.salesforce.com/apex/HTViewHelpDoc?id=setting_up_web-to-lead.htm&language=en

    And then take a look at the line that starts <form..

    does it look like

    <form action="https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8" method="POST">

    or does it look like

    <form action="https://myorg.my.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8" method="POST">

    If the first, then the fact you are using a custom domain shouldn’t make a difference.

    Plugin Author Nick Ciske

    (@nickciske)

    FYI – I’ll add a filter to allow you to override the API endpoint the plugin uses, in case it’s the latter URL. I’m curious to know either way though!

    Plugin Author Nick Ciske

    (@nickciske)

    OK, 2.1 (releasing this week) supports the following filter:

    salesforce_w2l_api_url
    Change the API url the plugin posts data to.

    e.g.

    add_filter( 'salesforce_w2l_api_url', 'my_w2l_api_url' );
    
    function my_w2l_api_url( $url ){
    	return 'https://my.custom-api-url.com/something/';
    }

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WordPress Plugin with Custom Domain’ is closed to new replies.