Community & Support

how to move drupal on production server?

i'm not sure this is right section for my question, but i want to get help from the community with issues related to moving my drupal site from dev server to production.
i thought that creating same database and privileges to it and checking out all the code from svn repository to the DocumentRoot would be enough, but it's not so.
And of course i've corrected /sites/default/setting.php for the DB requesits.
But when i try open my site i see errors about unexistent tmp path and i'm sure there are another errors but my site works very slow, i cannot even open module list, or configure any − blank page. I think it because of memory limit on production.
Thus i want to turn on drupal caching abilities, those where disabled in my dev version.
Should i have passed through installation process on a production? Is installation obligatory?
Thank you.

Comments

any number of things

If your target site is significantly different from the dev site, then yes, there could be any number of problems.
Yes, all the prerequisites need to be checked. You could have different OS, different paths, different PHP versions, different MySQL versions, different php extensions... no clean_url support ... anything.
Anyway, each of your issues need to be addressed individually.

Fix the temp path in the settings - file settings. On a cheap shared host, you may have to set it to sites/SITENAME/files/tmp.
Fix the mem limit in the normal way (see docs). Caching will not work around your mem limit.

.dan.

basic steps: 1. export and

basic steps:

1. export and import the mysql
2. copy and upload all files in druapl
3. adjust sites/default/settings.php (db setting)

A. if u have copied all the files, there should not be any tmp file missing issue.
unless u have some temp files NOT under drupal folder

B. but if u are using a non-professional hosting, u may face file access issue. The drupal (or say apache) does not has the right to read/write the files u uploaded.

in this case, u may call the hosting support OR move to another hosting.

We go the drupal way. How about you?
http://www.drupalway.com

nobody click here