Moving to New Server

70 Posts

kevince52 Reply #1, 15 years, 7 months ago

Hi,

I know this question must have been asked and I have read and followed the documentation about moving a Revo 2 site to a new server. Tried searching forms but that’s a goose chase for this one.

Parts of my site are working but no manager (yikes), no js, no wayfinder. The site appears with the right templates but no nav. I can’t believe that this is the only way to do this.

There seems to be many files with references to paths on my dev server in them. For instance:

/config.core.php
/connectors/config.core.php
/core/config.cache.php (I did try deleting this one to see if it would be rebuilt)
/manager/config.core.php

Evolution was so easy to move. Copy files and db. Make sure all the right files and directories had the right permissions. Edit the config file to connect to the new db. Done.

I’m not sure how to phrase this question but is there something I’m missing?

Sorry for asking such a noob question but this is killing me. Thanks for any help.

24,544 Posts

BobRay Reply #2, 15 years, 7 months ago

Did you run an upgrade install at the new site?

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
2,213 Posts

AMDbuilder Reply #3, 15 years, 7 months ago

BobRay already noted the main item you missed, granted the other item to check would be the database, you should find a few lines to update there.

Patrick | Server Wrangler
About Me: Website | Tweets | MODX Hosting

70 Posts

kevince52 Reply #4, 15 years, 7 months ago

Hi,

Thanks for the replies. I do love this CMS and this community is great.

I did try running a setup but all I get is a blank screen when I go to the setup directory. I haven’t check the error log but I will.

I know the connection to the database is working because after manually editing all of those files I mentioned (minus the cache I figured this must get rewritten at some point) I can see the home page with content. Still no wayfinder or manager. I could manually edit the cache file.

Question. How many files need to be edited to move REVO 2 to a new server?

Any other suggestions? Maybe a whole other method?

Would anyone advise clean install, edit /core/config.core.php to link to existing database, move site specific files to new server, install addons...

Again that seems very clunky.

Just so you know I’ve been using Modx for a while and have successfully deployed dozens of sites with EVO (on this same production server) but this is my first production site with REVO.

Thanks for the help Bob and AMDbuilder.

Cheers,

Kevin

☆ A M B ☆
2,213 Posts

AMDbuilder Reply #5, 15 years, 7 months ago

Hello Kevin,

I am actually referring to editing the paths in the database. I think there are one or two set in the database you can change. As for the white screen, it could be due to a lack of memory or other php related issue. Care to share a little more about the production server?

AMDbuilder

Patrick | Server Wrangler
About Me: Website | Tweets | MODX Hosting

70 Posts

kevince52 Reply #6, 15 years, 7 months ago

Thanks AMD. I’ll query the database for paths. The production server is a MediaTemple DV. It’s been pretty reliable. I do have a dozen or so other site on that server but they are pretty low traffic. I did reboot the server thinking there may be some issues and Plesk usually gives me fair warning when I’m running in the red. I will check that out though.

Again I’m questioning if this is normal? Are all of these changes necessary for moving Revo 2? Seems like a step backward compared to Evo.

Cheers and thanks again.

70 Posts

kevince52 Reply #7, 15 years, 7 months ago

So I cleaned out and re-uploaded my Revo site and uploaded a clean 2.0.8 (merged directories and overwrote files). Made sure the /core/cache was writable. Went to .../setup. Blank screen. Checked the error logs and all errors relate to Smarty. I’m getting:

[Sun Mar 27 13:37:13 2011] [error] [client xx.xx.xx.xx] PHP Warning: rename(/tmp/wrtSs9bBn,/var/www/vhosts/domain?.ca/httpdocs/core/cache/setup/smarty/5316fcfbe4b14ab560fd76c3edf5e65a5f4c816e.file.footer.tpl.php) [<a href='function.rename'>function.rename</a>]: Permission denied in /var/www/vhosts/domain?.ca/httpdocs/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 42 
[Sun Mar 27 13:37:13 2011] [error] [client xx.xx.xx.xx] PHP Warning: chmod() [<a href='function.chmod'>function.chmod</a>]: No such file or directory in /var/www/vhosts/domain?.ca/httpdocs/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 44 
[Sun Mar 27 13:37:13 2011] [error] [client xx.xx.xx.xx] PHP Warning: Smarty_Internal_Template::include(/var/www/vhosts/domain?.ca/httpdocs/core/cache/setup/smarty/5316fcfbe4b14ab560fd76c3edf5e65a5f4c816e.file.footer.tpl.php) [<a href='smarty-internal-template.include'>smarty-internal-template.include</a>]: failed to open stream: No such file or directory in /var/www/vhosts/domain?.ca/httpdocs/core/model/smarty/sysplugins/smarty_internal_template.php on line 422 
[Sun Mar 27 13:37:13 2011] [error] [client xx.xx.xx.xx] PHP Warning: Smarty_Internal_Template::include() [<a href='function.include'>function.include</a>]: Failed opening '/var/www/vhosts/domain?.ca/httpdocs/core/cache/setup/smarty/5316fcfbe4b14ab560fd76c3edf5e65a5f4c816e.file.footer.tpl.php' for inclusion (include_path='.:') in /var/www/vhosts/domain?.ca/httpdocs/core/model/smarty/sysplugins/smarty_internal_template.php on line 422

Any ideas?

☆ A M B ☆
2,213 Posts

AMDbuilder Reply #8, 15 years, 7 months ago

Hello Kevin,

The MediaTemplate servers really don’t jive well with MODX Revolution. I’ve had to move several sites (different clients) off their servers due to bad performance and general functionality issues. The above issue sounds almost identical to the issue we had with the first client.

I don’t think the issue is actually with MODX, but somehow with their configuration. I haven’t spent a lot of time debugging the issue as the clients wanted their sites functional. (It was case of MT didn’t have backups, wanted to change client for backups (that were older than clients backups), and was third or so time their site died on MT servers)....

Anyways, If I recall correctly the issue is must actually set the php version to use in the htaccess, by default it uses php4 instead of php5 (Despite control panel setting... idk why), but anyways, give that a try and see if it helps. Also check the default memory setting, you want to have at least 32-64mb (64mb preferred).

AMDbuilder

Patrick | Server Wrangler
About Me: Website | Tweets | MODX Hosting

70 Posts

kevince52 Reply #9, 15 years, 7 months ago

Hey AMDbuilder,

Thanks so much for the reply. I was beginning to suspect MT setup as being a possible issue. I saw a few mentions here in the forums and this is too weird of an issue for it to be just Modx. I’ve been thinking of moving from MT for a while for other reasons. This may be just the push I need.

If i do figure out what went wrong I’ll post here just in case anyone else has the same problem.

Cheers,

Kevin

70 Posts

kevince52 Reply #10, 15 years, 7 months ago

I’ve had some success with this site. The issue seemed to be related to the fact that I when I develop a site I’m one directory up from my web root. In other words web_root/sitename/modx_root. I also had to change the site path in the database in a few places. Here’s what I did in case anyone runs into the same issue:

1. Clear cache on development site.
2. Move files to production server. (I used Transmit on my mac because gunzip crapped out on my production server)
3. Edit any path in all config.core.php files. (root, /manager/ and /connectors/)
4. Edit config.inc.php (All references to old path and server)
5. Delete all files in /core/cache/ and make sure it is writeable (777)
6. Edit all references to the old path in database. (I used phpmyadmin, searched for the old path and manually replaced with new path)
7. Logged into the new manager and cleared cache again. (Just in case I looked at the site during the previous steps. May not be necessary.)

This worked for me and I was able to get the site working. I’m certainly no guru so take this with a grain of salt. Some of this may not be necessary. I just wanted to share in case anyone else was struggling with it.

Thanks again to Bob and AMDbuilder for the help.