When installing Case Tracker Services there is no dependency with services.module except from the project page.

Adding a line in casetracker_servies.info would help.

dependencies = services

Comments

clemens.tolboom’s picture

Correction:

dependencies = xmlrpc_server

sime’s picture

Status: Active » Fixed

thanks clemens fixed in dev

clemens.tolboom’s picture

Version: 5.x-0.4-beta » 5.x-1.x-dev

You where right about dependencies with services.

You fixed it in dev ... you could close in for the new release :-)

clemens.tolboom’s picture

Status: Fixed » Active

casetracker_services needs the casetracker module too :-)

I'm not sure whether other ct modules must be available / dependent on.

Maybe hook_requirement runtime is useful for the other ct modules to check.

clemens.tolboom’s picture

Title: Please add dependecy to service.module » Please add dependencies to service.module

And of course xml-rpc ... my install of the client failed because of this. So dependencies should be

dependencies = services xmlrpc_server casetracker

This dependency to xmlrpc is I know for the client but it would safe a lot of hasle ;-)

sime’s picture

Status: Active » Fixed

Yes, I've updated it to have casetracker, but not xmlrpc_server... the services should be available over any server type (not that I've tested it! :)

http://drupal.org/cvs?commit=109930

Oh, an I'm considering not releasing until I do one thing. At the moment I have the cases sorting by status I think for want of a better method. I think this will suck for some people. Gotta think about a way to do this, considering the weight column in the codes table...

clemens.tolboom’s picture

Ok ... I understand that casetracker_services should work for any service type.

Maybe some note on the client side or testing the server for having xmlrpc would be nice. Becasue that is what casetracker_client uses right?

sime’s picture

yeah, this client is written specifically to use the xmlrpc server. I should put additional warnings in the client.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.