Hi,
I have been working on a development site on my laptop and am now in the process of transferring it to my desktop PC using the Backup and Migrate module.
I have an identical file structure on the desktop and have imported the database over to the desktop PC without any problems using the restore option. The site functions as it should, however as soon as I try and do anything in terms of administering the site i.e. modifiying the content, adding content, modifiying any kind of settings and click (for example) the "save settings" button, drupal responds by doing apsolutely nothing! There is not even an error message! It doesn’t crash, it just sits there as if I havent told it to do anything.
Even when I log out, it won’t let me log back in. I click the "log in" button and nothing happens. Not even an error message saying I have the username or password wrong. I have then been deleting the database and all drupal files and starting the process again but to no avail.
My steps involved were:
1) Clearing cache (at all stages).
2) Export data base using backup and migrate from my desktop PC.
3) Copy the exact drupal 7 files from my laptop into my www directory of the WAMP (server) folder on my desktop.
4) Set up a new database on my desktop using phpmyadmin (even use the same name).
5) Create a new settings.php file.
6) Install the new site on the desktop.
7) Enable the backup and migrate module on the new site.
8) Restore the backed up database to the new site.
I was successful with the above steps in setting up an identical site on a second virtual host on the same laptop. So I doubt it’s because I’m using development versions of modules.
The only differences I can see between the two systems is that my laptop runs windows 7 (32bit) with Wamp v2.0 whilst my desktop runs Windows 7 (64bit) with Wamp v2.1. I can’t see this being the issue.
Anyone got a clue as to whats wrong with my setup?
Cheers.
p.s. I have just realised that my laptop is running MySQL version 5.1.36 and my desktop is running version 5.1.53. Could this be an issue? I have little knowledge of MySQL.
Comments
Maybe you don't have the
Maybe you don't have the mod_rewrite() module turned on in apache. Without it, clean URLs won't work, and if you are migrating from a system with clean URLs, everything will stop working.
Contact me to contract me for D7 -> D10/11 migrations.
Fixed!
Thanks Jay. It was indeed the rewrite_module.
Cheers!
Thanks!
Thanks for posting your solution. It worked for my problem as well.
Thanks
Thanks, this worked and presented a new problem.
( ! ) Fatal error: Unsupported operand types in C:\webs\drupal7\modules\field\field.info.inc on line 293
Call Stack
# Time Memory Function Location
1 0.0006 369088 {main}( ) ..\index.php:0
2 0.4154 24308880 menu_execute_active_handler( ) ..\index.php:22
3 0.4314 25685472 call_user_func_array ( ) ..\menu.inc:501
4 0.4314 25685608 views_ui_list_views( ) ..\menu.inc:0
5 0.4314 25685704 theme( ) ..\admin.inc:16
6 0.4391 26119832 template_preprocess_views_ui_list_views( ) ..\theme.inc:845
7 0.5025 28923776 drupal_build_form( ) ..\admin.inc:84
8 0.5025 28925360 drupal_retrieve_form( ) ..\form.inc:315
9 0.5026 28926216 call_user_func_array ( ) ..\form.inc:771
10 0.5026 28926448 views_ui_list_views_form( ) ..\form.inc:0
11 0.5028 28929344 views_fetch_base_tables( ) ..\admin.inc:287
12 0.5028 28929584 views_fetch_data( ) ..\admin.inc:3945
13 0.5032 28929648 _views_fetch_data( ) ..\views.module:856
14 0.5293 29962128 module_invoke_all( ) ..\cache.inc:40
15 0.5326 30005504 call_user_func_array ( ) ..\module.inc:817
16 0.5326 30005640 field_views_data( ) ..\module.inc:0
17 0.5326 30005760 field_info_fields( ) ..\field.views.inc:20
18 0.5326 30005880 _field_info_collate_fields( ) ..\field.info.inc:594
19 0.7174 31440560 _field_info_prepare_instance( ) ..\field.info.inc:222
Not sure if they're related but its causing issues.
Seems a it's not being passed an array
You'll get Unsupported operand types in this line if the variables used aren't arrays. There are a few places in the field.info.inc where this is assumed.
Probably an upgrade problem with a module.