Firstly, wanted to commend you on this solution. I spent the better part of the last 8 months researching a way to manage content across a network of sites, and this works fantastically well. I will be implementing it across 20 sites over the next week now that we've had success with some beta test runs.

---

It was significantly difficult to get the correct versions of all required modules to play nice with each other. The first time I set this up was late May/early April, which worked. I then attempted to install (from scratch) the Alpha2 release (a couple weeks ago) as well as other current versions and ran into bugs and incompatibilities with different modules. I have not yet worked with alpha3 or other releases to date, but I do recommend some documentation giving a current recipe of modules that work as a set. Here's the recipe I'm using:

http://drupal.org/project/content_push content_push-6.x-1.0-alpha1
http://drupal.org/project/clients clients-6.x-2.x-dev
http://drupal.org/project/Autoload autoload-6.x-2.x-dev
http://drupal.org/project/faces faces-6.x-1.0-beta1
http://drupal.org/project/transport transport-6.x-1.0-alpha5

Hope this helps.

Comments

joachim’s picture

joachim commented
Title: Module Dependencies » add module dependencies versions to README
Category: support » bug
Status: Active » Fixed

Thanks! Great to hear this module is being used, and on a pretty large scale too!

I've added details of version numbers to the Content Push readme, though note that the Transport readme is the real authority for this -- Content Push depends entirely on Transport being happy ;)

The majority of my current development is happening on Clients module at the moment, as I'm trying to get that to a stable 1.0 release. In the last few weeks there was a big changes that had an impact further up the stack: the switch from numeric connection IDs to machine names.

The reason for the knock-on impact is the transport_entity_remote table, which stores a source key based on connection name (and this is a part of Transport which is still a bit flaky...). I've just filed #1183298: figure out how source name should work properly so I remember to deal with it...

The other big change that is coming up is the reintroduction of resources in Clients module. This may result in bit of Transport being redefined as a resource, though that'll just be a change in where configuration lives.

Any other changes to Transport will be internal -- that is, refactoring of the code, adding support for comments and input formats.

I plan on running a BoF session on Transport and Content Push at DrupalCon London, so maybe see you there. Good luck with the deployment!

Alex Andrascu’s picture

Alex Andrascu commented

I can confirm success with

http://drupal.org/project/content_push content_push-6.x-1.0-alpha1
http://drupal.org/project/clients clients-6.x-2.0-beta3 using same version on both master and client
http://drupal.org/project/Autoload autoload-6.x-2.1 using same version on both master and client
http://drupal.org/project/faces faces-6.x-1.0-beta1
http://drupal.org/project/transport transport-6.x-1.0-alpha5

Also looking forward to implement it large scale but we're still on beta testing.

wolv3rin3’s picture

wolv3rin3 commented

Thanks, joachim. Just even getting this conversation in the open is going to help. Yep, I could tell you were cranking across the board. No pressure on this end since I'm just happy to have a working recipe for now.

Won't be seeing you in London, but hope that helps you gain some momentum.

wolv3rin3’s picture

wolv3rin3 commented

Went through the new readme's today and they seemed to cover the recipe successfully. And, fwiw, here's the latest I'm running successfully:

http://drupal.org/project/content_push 6.x-1.0-alpha3
http://drupal.org/project/transport 6.x-1.0-alpha6
http://drupal.org/project/ctools 6.x-1.x-dev
http://drupal.org/project/clients 6.x-2.0-beta3
http://drupal.org/project/faces 6.x-1.0-beta1
http://drupal.org/project/autoload 6.x-2.1
http://drupal.org/project/services 6.x-2.x-dev
http://drupal.org/project/features 6.x-1.0

Status: Fixed » Closed (fixed)

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