How do you move Revo out of subdirectory after new site is developed?

This is assuming an existing static site exists:

Aside from moving the files and folders manually, are there other steps involved with the process? I usually just create a temporary template page, fill it with the existing sites index.html code, apply the template to a resource, and set that resource as the index page. [ed. note: mmcgee last edited this post 13 years, 2 months ago.]

hope see what replies you get on this

You will need to edit the three config.core.php files (root, connectors, manager) and the core/config/config.inc.php file. You can even change the names of the main folders (manager, assets, etc) if you like, making sure to edit the config.inc.php file to reflect your changes. For example, instead of /manager/ you can have /whatever-you-like/ to confuse hacker-bots.

Make sure to manually clear the core/cache/ folder and clear your browser cache and cookies for the domain.

Don't forget to edit the .htaccess file's RewriteBase line (or whatever rewrite method your web server uses) if you're using friendly URLs and rewrite rules.

You rock Susan! Thank you for being so very helpful. I like the tidbit about changing the manager directory. Very clever.

In this instance... I got antsy and went ahead and dumped everything into the root. Learned some command line stuff in the process. Installing MODx and a virtual server and having to use Terminal for a lot of steps with unzipping and moving files arounds. Nerve-racking to say the least. Fortunately the support have been above and beyond—providing tips, instruction and remaining very patient with me.

Now is the real test as I begin to run the setup.

Semi-related here. Perhaps I need to create a new post?

I just installed MODx on Apache/2.2.3 (CentOS) Server. I hit a few snags with folder permissions. Initially, the setup only displayed the contents of the setup folder. So I then set
core/cache was 757 and I changed it to be 777. I also change core/config from 757 to 777 as well.

Got the installer to run, and all went well until the very end Thank You part. 3 items listed
The message said that I needed to create an assets folder and make it writeable. So I created the directory 'assets' and made it 777
The message said that I needed to create a components directory inside assets and make it writeable. So I creates 'assets/components' and made it 777
The message said that I needed to create a components directory inside core and make it writeable. So I creates 'core/components' and made it 777

Went ahead and clicked Login (with the box checked to delete the setup directory and it's contents). Instead of the MODx interface I only get the list of contents of the manager.

I'm stumped. Is there a reason that the manager is not displaying. Should I go ahead and click on index.php in the manager?

OK....couldn't wait. My clicker was chomping at the bit. I clicked index.php and got the login screen. Logged in, and now all seems OK... so far.
Deleting the setup folder now.

Making all those folders 777 though... is that a problem security wise. Or is that the normal setting for those. This permission stuff throws me sometimes.

I don't fully understand who the titles are referring to. Who is the OWNER? Who is the GROUP? And who is OTHERS?

There was already a resource 'Home' in the MODx resources column and it's alias is index. However, when I navigate to the index.html page using my browser, the existing websites home page shows up. I kind of expected there to be a blank page.

Is this some kind of server issue? I'm not getting any error message?

Usually, I quickly copy and paste the existing sites index.html code into a template page and then publish the resource.

I checked system settings and site_start is set to resource 1, so I expected the home page to be blank until I could copy in the html code.

index.html displays the existing site's home page.
index.php however, displays the blank MODx page.

Maybe I can just leave the index.html in place while I develop? I don't ever remember having to delete the index.html though. [ed. note: mmcgee last edited this post 13 years, 2 months ago.]

Yikes! so many questions.

Good thing is. MODx installed. It's lightening fast! The clients existing site is still functioning And I didn't melt down the virtual server in the process.

MODX is only mimicking the index.html in the output, you're still requesting index.php initially when viewing a page served by MODX. When index.html is requested it will show that actual file from your root. As long as that file exists, MODX will not take over your static site.

You should be able to develop right along side the static site. I'd turn FURL's off while doing this, which will prevent loading of any pages you create that might match your static file names.

This is one of the perks of MODX that I really like. Not that moving a site from a sub-directory is really that difficult, but doing it this way sure is convenient. When you're ready to launch, rename the index.html file turn on FURL's and off you go.

I like your thinking about working right along side of the existing site. I changed the name of the ht.access, to .htaccess and that remedied the index.html / index.php issue. Also allowed the manager login page to display rather and an index listing of the manager directory.

Thanks for the feedback. Much appreciated.