it kills my client sites

I do need to clean up the error stuff, when I do that what you will get is a message saying why the communication to the server failed.

Ie. there is a test area on that settings page, and it's trying to connect to the server and gather some version info.

Interested if you have any luck with the latest dev version, we've fixed a number of problems.

And a quick fix for 'killing the client' is removing the line in 'casetracker_client' calling function 'dsm'

OK....I took out that dsm line and the client site is active again....but of course, the Case Tracker shouldn't work right?

And the blank white screen obviously meant the test communication failed? Any reason?

I'm using the Beta now and will look for the dev version and try it and report back here

I got this error after installing the dev version:


*

An error occurred while getting https://www.vibecomputing.com/services/xmlrpc/KEYABCDEF...
Arguments:
- https://www.vibecomputing.com/services/xmlrpc/KEYABCDEF....
- casetracker.css
- KEYABCDEF

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

*

An error occurred while getting https://www.vibecomputing.com/services/xmlrpc/KEYABCDEF
Arguments:
- https://www.vibecomputing.com/services/xmlrpc/KEYABCDEF
- casetracker.projects
- KEYABCDEF

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

but it made me realize the error....the 'vibe' site is the server, but its on http, not https. The server setting seemed to default back to https (which doesn't exist), thus the error.

I tried changing it to http but then I got the dreaded white screen again.

So what can I do? Do I have to set the server up on an https site? My server has that of course, but I've never used it....not sure what the difference is (I know the 's' stands for 'secure'). I 'suppose I could set up a separate Drupal site just for the case tracker server....but I'd rather avoid it if I could...last thing I need is another stray Drupal site to maintain! :)

Hi, I edited your comment and removed your keys - might not be a problem but they are used for security.

https is recommended but *not* required. So for you the https is failing in a simple way and this error is reporting ok. The http is probably succeeding, but there is a problem with the return value and it's white-screening.

Please try this for me. Inside casetracker_client_settings() in casetracker_client.module modify the first couple lines thus:

I thinks this is a dub from #244875: Having the server side not granted access to any project the client shows white screen when going to support

I don't think so.

On the server side, I created a service key for the client, created a project, and assigned that project to that client....that is all there is to it on the server side right? That 'should' give the client access?

Then on the client side I install the casetracker services but when I enable it it directs me to /admin/build/modules/list/confirm which is the blank white screen. I'm not sure what it'd be asking to enable as the case tracker services module doesn't have any dependencies does it?

I don't even get to the part where it would ask me for the service key generated on the server...

fwiw

I just installed casetracker_services (5.x-0.4-beta) on a new site. Then I enabled casetracker_CLIENT (5.x-0.4-beta)

Did you by accident enabled casetracker_SERVICES on the client?

The path admin/build/modules/list/confirm maybe asking for a dependency and got screwed somehow?

on the server:
- created a project
- created a services key
on the client
- admin/settings/casetracker_client added the key
- connection test went ok

No white screens. But I forgot to grant access to a project. So still cannot create a case :-/

What are your settings on the server for admin/build/services/settings ?
- i have only keys checked.
- no strict (gives wrong number of param error but not a white screen)

Cheers

hm. I installed it just now on a third (client) site of mine and WAS able to enable th module and get to the screen to enter the key from the server site.

After entering the key, I clicked on the 'test settings' drop down....nothing happened other than the arrow opening up, to reveal nothing....should it show some sort of approval?

I now see the Support menu in the Navigation....I entered a case on the server for this client's project and it doesn't show in the client's support queue....how often should this sync?

This time I did make sure I enabled the CLIENT part....I'm going to go back and reinstall on the other sites to see how it works.

and I just went to create a new issue from the client's site and got this error:

* warning: Invalid argument supplied for foreach() in /var/www/vhosts/soga.ca/httpdocs/sites/default/modules/casetracker_services/casetracker_client.module on line 361.
* warning: array_shift(): The argument should be an array in /var/www/vhosts/soga.ca/httpdocs/sites/default/modules/casetracker_services/casetracker_client.module on line 372.
* warning: Invalid argument supplied for foreach() in /var/www/vhosts/soga.ca/httpdocs/includes/form.inc on line 949.
* warning: Invalid argument supplied for foreach() in /var/www/vhosts/soga.ca/httpdocs/includes/form.inc on line 949.
* warning: Invalid argument supplied for foreach() in /var/www/vhosts/soga.ca/httpdocs/includes/form.inc on line 949.

I am guessing the test has failed but didn't tell me it failed.

Does the syntax of the server matter? need "http://"? need the "www."?

And the Case Tracker server still isn't on https....not sure if that is an issue or not.

Grrrrr! I just killed the client again...I went and changed the Server from https:// to http:// and it went white...killed the site again.

How do I start over?

I guess https is required?

so how can I clear the case-tracker client preferences? Cuz to revive my site, I had to just delete the case_tacker services module folder. I then recopied the module over. Then I could see the module listed in the modules list...and it was active but there were no menu items (site settings or the services menu) so I disabled it in the module list, re-enabled it and it went white again...

I just installed it without adding the protocol on the client.

I got this white screen too ... but hit back ... added http ... and it all went ok

I use the dev version!

What version of php are you using? dunno whether that's important.

I can't get the Services portion to work on that first site at all.....something is completely buggered...

I tried it on yet another site....and was hoping to just disable using keys on the server (at least for testing), but the client says it REQUIRES a key. Should I not be able to get away with not using keys on the client?

What security issue does that raise?

on this newly installed site, once I've set up the server with a key for this new site, created a project, assigned it to that client and then enter the server settings (with key) on the client site, I go to add a new issue (from the client site) and it shows me these errors:

And none of the status, type or priority drop-downs have anything in them.

I'm assuming the communication with the server isn't working but I tried to add an issue anyways. And I get these errors:

I did enter 'http' on the client side and no white screen this time. Nothing happens when I click on 'test connection' button....I'm not sure what is supposed to happen.

I installed the Server part on a fresh Drupal install as I REALLY want to get this working...and now I can't get that working. I'm going to open a new Support Request...

Well...I got some bugs worked out of the Server side so I thought I'd take a crack at getting the client side of things to work. When I go to enable the Casetracker Client module in the list of modules, it goes to some sort of confirmation page (asking to activate a required module?) but the entire page is blank white (no errors).

After that, the entire site is inaccessible and I have to delete the casetracker_services module to get it back up and going.

I even just tried to install the Services module in case it was looking for that module(s) when enabling the casetracker_services module but no luck. I'm at a loss...I've never had such trouble with a module before.

I'm frustrated - any help is greatly appreciated.

I just looked back on the recomendations above and tried the dev version. It didn't white-out my site when I enabled it but the admin links weren't in existence.

wtf! :)

Any updates on this??

I can't get this mod working for the life of me either. Followed the instructions, setup on numerous sites including clean installs, all to no avail.

Errors like these:

Error
stdClass Object
(
[is_error] => 1
[code] => 302
[message] =>
)

all over the place

Let me know,

TIA

txcrew

I was having similar problems. Had to downgrade my copy of the Services module to version 5.x-0.91 (http://drupal.org/node/272522).

After cleaning things out (disabled and then removed Services module and Case Tracker Services module) on both the server and client sites, I reinstalled Services using this version, then added Case Tracker Services back in (using the beta version), following the docs.

Removed the reference to 'dsm' that had been giving some others problems. (http://drupal.org/node/244057)

After that, everything worked.

If you need more info, let me know, and I'll post things like user permissions, Services settings, etc.

Yes sirr!

Followed your suggestions and you are 100% correct. Seemed to be rolling back to the Services module 5.x-0.91, that did the trick.

I spent hours struggling with this one and you have saved the day! Thanks so much!

txcrew