Source and destination databases cannot be the same.

It sounds like either you have the two DB’s in your sites config set to the same thing for the sites in question, or in your dbs config you have two separate DB configs, but they point to the same DB.

If that’s not the case, pls post your sites and dbs config files here (omit sensitive info like passwords of course) and I’ll take a look.

siteconfig:

; <?php die('Forbidden'); ?> -*- conf -*-

	[all]
	wp_content_dir = /wp-content
	wp_plugin_dir = /wp-content/plugins
	cache = no
	caches[] = /caches/timthumb
	caches[] = /caches/something_else

	[live]
	label = SitePush Site
	domains[] = sitepushrecipient.see-villa.eu
	web_path = /homepages/33/d148208799/htdocs/see-villa-sitepushrecipient
	db = sitepush_database
	live = yes

	[dev]
	label = Beta Site
	domain = beta.see-villa.eu
	web_path = /homepages/33/d148208799/htdocs/see-villa-beta
	db = beta_database
	live = no

db config:

; <?php die('Forbidden'); ?> -*- conf -*-

	[all]
	prefix = wp_

	[sitepush_database]
  host = db488458253.db.1and1.com
	name = db488458253
	user = dbo488458253

	[beta_database]
  host = db486898713.db.1and1.com
	name = db486898713
	user = dbo486898713

I don’t see anything obviously wrong in your configs, except the indentation is a bit off… if that’s the case in your actual files, you could try making sure that none of the lines are indented.

If not, I’ll need to take a look at more detail of your setup. Could you please do the following:-

1. add a line with define('SITEPUSH_DEBUG',TRUE); in your wp-config.php file (above the “That’s all, stop editing!” line)
2. go to the SitePush options screen, at the bottom there should now be a field for debug code, in it please enter var_export($this);, and save options
3. there will be a lot of information at the top. After removing any sensitive info like passwords please could you send me that info. If you don’t want to post it all here, you can email me direct.

Hi,

Removing indents did not work. Sent the debug info to your email.

It was a bug in SitePush.

I’ve just released a new version which should fix this.