Pull webform submissions in different webistes to one end-point

Question

hypothetical example:

website1 has 2 webforms, I need to access the submissions of the 2 webforms in another website2

So if an user send the webform in website1 I need to log in as admin in website2 and see that submission. In few words, pull the webform submissions to one endpoint website (without the necessity of click a button or run a command), Master-Slave where the slave is the endpoint website that is only going to show results of webforms.

is this possible?

My use case: I have a lot of surveys in different websites hosted in different servers, I need an endpoint where to collect all the results and show it to my users, so I need have the submissions stored in my endpoint website for show results to my users.

Thanks

Answer 1

A stupid and simple approach (that scales badly) would be to use drush sql-sync.

Since you can give it the --tables-list option, you can get it to transfer only the appropriate tables. And because drush will use rsync for transfer, the network transfer is not going to be very large, since only changes well be moved.

It will however drop and recreate the tables everytime, and this might not be acceptable.

Answer 2

Ultimately, there are several ways to accomplish a 'sync' across multiple sites. However, without more technical information the options are generic at best. Webforms that include uploads or images may require additional work to configure.

Bottom line, the webform data lives in a table in the database, on each site. The best solution may not be a module but rather a cron job pulling that data and serializing it on a collection site. This would be a custom script collating and creating webform content on the collection site. As such, the webform Node ID would not necessarily be preserved.

Another approach, if the cron job is not preferred... might be to use the built-in mail function from webform, or to create a Rule to send the webform data to a mailbox. The collection site can be configured to create node content processed from that mailbox. One benefit is that this could be a non-webform content type. As such, you can add fields and act on that data in a way to manage it and you could also in this way preserve a record of the original Node ID so that a reference to the source site is possible. Other fields might be the site URL, notes, if action is required... and so forth.

Here are some references that might be useful in the latter approach:

• Add content to your site via email using https://www.drupal.org/project/mailhandler - Mailhandler
• http://drupal.stackexchange.com/questions/69134/send-mail-to-email-addresses-from-webform-when-a-content-is-saved - Send mail to email addresses from webform ...
• https://www.drupal.org/project/webform_rules - Webform Rules module

Of course, it matters if you're using D6 or D7. Mailsave & Mailhandler are both included in one popular approach using D6 and Mailsave doesn't have a D7 version.