This feels pretty sad after all the great reviews of the module - but it just isn't working!

I'm trying to move a new site from MAMP on my Leopard mac to a liveserver. The first weird thing (which may not be related, just adding for completeness sake) was creating the backup the first time... I used adminmenu to go directly to backup/export, got a blank page. Then use admin menu to go the top level backup/migrate page, got this message:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_backup_migrate_export' was given in /Applications/MAMP/htdocs/frolympia/includes/menu.inc on line 346.

This still happens when I try to go directly to the backup/export page using adminmenu. If I go to the top level and then click backup/export from there I have no problems.

Reloaded the page and everything was dandy.
Saved backup successfully. No compression.

The problems began when I went to the livesite, with the module installed. Went to import, got a success message ("1,345 (or whatever) mysql entries made" (or whatever)) no errors, but NOTHING CHANGED on the site. Not. One. Thing. No users imported. The theme didn't change. No content at all.

Realized I was trying to bring a 6.3 site to a 6.4 install, so upgraded the local site. Backed up. Tried importing. Still nothing.

Read through the issues, didn't see anything similar, but saw the instructions to enable all modules and themes, so I did that. Made sure the same modules and themes were enabled on both sites. Tried again. Still no change.

What's going on? Please help!

Comments

ronan’s picture

ronan commented
Status: Active » Postponed (maintainer needs more info)

Hi there,

Sorry you're having trouble. The first issue seems to be an error in my menu declaration code. I don't use admin menu myself, so I've never uncovered it, but I don't imagine it'll be too hard to fix. I'll take a look at it as soon as I can.

As for the second issue, It's strange that it's not working. Are you using table prefixes at all? If so are they set to be the same on both sites? Have you tried emptying the cache (under admin/settings/performance) on the live site? Do you have access to the mysql db through another tool such as phpMyAdmin? Can you look and see if there's anything odd going on there (extra tables etc.)

Thanks

rafaeldwan’s picture

rafaeldwan commented
Project: Backup and Migrate » backup
Version: 6.x-1.0 » master

Thank you for your prompt response.

We did a fresh install on the livesite, avoided the adminmenu conflict, and made sure all the modules corresponded the first time and it worked as advertised!

Wish I could help figure out what happened, I've asked the person who did the fresh install if she did anything different this time, and I'll let you know if she did. I'm just happy now that I can say along with the rest:

Great module! Thank you!

hansrossel’s picture

hansrossel commented
Title: Migrate doesn't work! » Error when using admin menu - compatibility problems
Project: backup » Backup and Migrate
Version: master » 6.x-1.0
Priority: Critical » Normal

I had the same white screen & error message and it was solved by disabling temporary the Administration menu module.

On the other hand I took backups before on that installation with backup & migrate + admin menu enabled without problems and when I re-enable admin menu I could also take a backup. Memory is ok and no apache errors in the log.

AltaVida’s picture

AltaVida commented

The problem seems to be this code in hook_menu() (I'm also using the administration menu module but this doesn't seem to have anything to do with that).

  $items['admin/content/backup_migrate/export'] = array(
    'title' => t('Backup/Export DB'),
    'description' => t('Backup the database.'),
    'page callback' => '_backup_migrate_export',
    'access arguments' => array('perform backup'),
    'weight' => 0,
    'type' => MENU_DEFAULT_LOCAL_TASK,
  );

The function "_backup_migrate_export" simply doesn't exist.

Replacing the line:

    'page callback' => '_backup_migrate_export',

With:

    'page callback' => 'drupal_get_form',
    'page arguments' => array('backup_migrate_backup'),

Seems to solve this problem.

AltaVida’s picture

AltaVida commented

Oops, ignore my comment above. This seems to be fixed in the dev version.

devinhedge’s picture

devinhedge commented

Likewise. I can confirm that it seems to have fixed the issue.

ronan’s picture

ronan commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

This is now in the stable release.