formatEndpoint() error

In troubleshooting, I manually removed all rows from the clients_connections table (on both master and slave site). That enabled me to browse to the create connections page. But, when I attempted to recreate afresh through Drupal, again received the error.

Have cleared cache many times.

As noted, I am using Web Service Clients 6.x-2.0-beta3. Per the Content Push instructions :

1.1 Download:

- content push
- services 6.x-2.4
- clients 6.x-1.0-beta3 or higher
- transport services

Showing in which table?

Content Push readme.txt doesn't state needing to install the Transport dev version, so I had installed the alpha, since this will be used on a live site.

I just updated to Transport dev version (from alpha), and I now can add services. Might be good to add that to the readme.txt file.

I'd have thought as much too. Just reporting what I did.

The only thing that I did related to Clients module was to enable the PEAR Crypt Blowfish option. However, I have since disabled it because it required some additional configuration that I was not sure about -- and, the Content Push (nor Clients) didn't state it as a requirement.

When it was enabled, it was not configured (/admin/settings/crypt_blowfish). Now that it is disabled, it is not ill affecting my ability to create services. Although, I still am not able to properly connect and load node. Still troubleshooting that.

When I try to load a test node (from slave site), I get :

stdClass Object
(
    [is_error] => 1
    [code] => 404
    [message] => Not Found
)

You are saying that stdClass is wrong?

I'm trying to troubleshoot -- trying to figure out where all to look for the issues. Your readme.txt seemed very thorough.

I think Content Push will be an awesome asset, if I can get it working.

If/when I get this working, I'll create some documentation (use case) with screenshots.

Ok. good to know. Still not sure if that original error, although not displaying, is tell-tale of some of problem that remains.

Right now, Master site can connect with slave site.

Test connection

Array
(
    [sessid] => cfa2800786f57e27d940b26fa82d7f7c
    [user] => Array
        (
            [uid] => 0
            [hostname] => 99.24.111.235
            [roles] => Array
                (
                    [1] => anonymous user
                )

            [session] => 
            [cache] => 0
        )

)

But, slave site cannot connect to master site. Neither seems to pass user connect test. Result always reads "Test User".

If I try to test node load on master (yes, i know not the norm) just for troubleshooting, I get this result*:

stdClass Object
(
    [is_error] => 1
    [code] => 401
    [message] => Invalid API key.
)

Master Site:
--------------
Services Key and Connection for receiving (a/k/a slave) site -- key same for both settings.
Key same for connections on both master and slave sites*.

Slave (/Receiving) Site:
---------------------------
Services Key and Connection for master (a/k/a distributing) site -- key same for both settings.
Key same for connections on both master and slave sites*.

Seems that there needs to be a matching key for master and slave (and help text for field seems to indicate that), but I wasn't sure from readme instructions. Only that key created for Services needs to be same used in Connection.
* But, I have tried it both ways. [Master site connects in either case.]

Odd thing:

In the Admin Menu on Master site, the options include:

     Clients
          Connections
          Settings
     Keys
          List
          Create keys
     Services
          Browse
          Settings

However, on the receiving site, the Admin Menu options look like this:

     Clients
          Connections
          Settings
     Services
          Browse
          Keys
          Settings

I have double checked that all the dependent modules being used for Content Push are same versions on both sites, and same module settings.

I have enabled the same services on both sites, in troubleshooting. So, clones in every way except they have different Content Push names, and unique API keys (with unique domains, urls). Each has the same content types and same webservices role/user. I have checked permissions and even rebuilt them on both sites.

Any ideas where else to look for issues? Uninstalling all content push related modules, reinstalling, and reconfiguring being a last resort.

well, I don't know if the error that I received earlier is indicative of some other issue with the clients module, within this installation, that is causing the other failures.

I _did_ try using different keys. And, as mentioned, the master site _is_ connecting, in general...but not logging in.

I am asking how best to continue to troubleshoot. Can you move this thread to Content Push?

I have double and triple checked versions, and cleared cache several times. Even logged out and logged back in. So, all I can say to that is "Drupal, you go some 'xplainin to do".

But, in any case, I got the connection sorted out! Good test on all.

This is a damn fine functionality (and will make a nice feature)! I have a few other questions that I'll ask at Content Push.

I'll do screenshots for other visual folks who might overlook what I did.

Thanks for all the replies here. Now, I just gotta figure out how it works form here.

Indeed, I did have the release version of CTools installed before starting with Content Push et al. I did update that to the dev version. That was probably part of the resolution -- i.e., fixing the endpoint error.

Yes, I know that keys are automatically generated. I was referring to use of key in the connections configuration. You could use the same key there (same key for master and receiving site) -- that is what I had tried, in troubleshooting, when the other way was not working. [As in a common key that establishes the relationship between the two sites.] ...Just pointing that out for anyone else who might find this thread with same question.

???? On the client connections add/edit form, there is a blank for Service Key where you enter the key. Type or copy/paste.