| Re: Moving xoops. |
| by mboyden on 2007/6/23 13:47:12 It's possible, but it depends upon a number of things. Here is my short checklist. How to Deploy Existing Site to New Site 1. Export the entire database 2. TarGzip the entire site (include XOOPS_TRUSTED_PATH if appropriate) 3. Setup database on new site (if not already setup) 4. Change hard-coded local URLs in data (make relative!). 5. Import database to new site 6. UnGzipTar files and move into place 7. Fix mainfile.php with new database login, XOOPS root path/url 8. Fix .htaccess with new domain/url (likely unneeded) #4 is quite pertinent. Depending on your content, you may have some hardcoded URLs or IMG sources. The depends upon how your server is configured. You may have to do a search and replace of your SQL code prior to importing the database to fix these across your site. Mainfile has your database login info and XOOPS Root info (two places: URL and file root). If your database hasn't changed, then you don't have to worry about that. I've done this a number of times for clients because we have a development sandbox, a test/staging sandbox, and then the production environment. Each has to be easy to move. Using the above, makes it easy. |
| Re: Moving xoops. |
| by jorgendn on 2007/6/23 11:05:15 wow, that was fast... :) thank you very much! -J |
| Re: Moving xoops. |
| by jdseymour on 2007/6/23 10:44:25 Mainfile.php is the file you edit when moving a XOOPS installation. Make sure you clean the templates_c and cache folder after editing. Leave the index.html files in both folders for security. |
| Moving xoops. |
| by jorgendn on 2007/6/23 10:39:23 Is it possible to move the XOOPS installation to another folder on the webserver? what files need to be configured to tell XOOPS that the ($xoops_site) is another directory/domain? |