Installed Revo in root folder, domain url doesn't direct anymore to index.html of my existing website

Hello,

I hope that somebody can help a total newbie. I installed Revo 2 x on my friend's server: 1x in a subfolder and 1x in the root folder.
The purpose is to develop the ModX site in the subfolder installation, and when it's finished to move the site to the root folder. I installed it already in the root to be sure to have 2 same revo versions (installation happens through the hosting provider, piece of a cake, but I can't chose the version). As I don't know how long it will take to finish the ModX site I want to avoid problems in the future when the hosting provider should have a more recent version of ModX Revo and therefore maybe give problems when moving the site to the root. I might be of course completely wrong with this.

There is already a working html site in the root folder, which should be staying there untill the Revo site is finished.

After the installation of Revo in the root, the url (http://www.mrrmusic.com) doesn't direct anymore to the index.html file of the existing website but to the index file of the ModX installation. If I type manually the url + the / + index.html (http://www.mrrmusic.com/index.html) no problem. But people who are searching for www.mrrmusic.com will see a blank page (the ModX index file) and won't know that the site still exists. They also won't type the complete path.

It also seems that I can't unpublish the ModX index file, which would have been a solution I suppose?

Is there anyone who can urgently advice me? Because right now it gives the impression to my friend's customers that the site has gone.

Thank you very much in advance! [ed. note: murkyred1630 last edited this post 12 years, 10 months ago.]

There is a defined order for the starting files of a website. This is done by the hosting provider. It seems that in your case the first file that is shown when you type http://www.mrrmusic.com is the index.php. Only when there's no index.php there is shown the index.html.
Your hosting provider may change this for you.
Or you do a starting page in MODX with a redirection to the index.html. In the header something like that

Hi Patstar,

Thank you very much for your reply. But meanwhile I found the (very easy) solution by just adding a line to the .htaccess file and it was done
I found it here: https://forums.modx.com/thread/16226/how-to-keep-old-site-running-while-setting-up-a-modx-site?page=2#dis-post-87663

But as mentioned in that post: I didn't rename the alias from the index.php file from ModX, as the site's start page is the html so I don't see an immediate reason to change the alias in my case. The site of my friend is showing up again, so I'm very happy

Your solution is a good one too!

Are you aware that you can set the site's site_status to "No", and then have either a site unavailable message or a site unavailable resource to show users? Manager users will see the MODx site.

In your case, the site_unavailable_page would simply be a resource with no template, and its content would be a copy of your index.html page.

Hi Sotwell,

I was searching in the settings for the site status, but I didn't find it (perhaps because I am a newbie ). I will retain your answer! Thank you!

Anyway, maybe it's now not necessary anymore to develop the site in a subfolder, as the installation in the root went fine and the old site is still showing up. Are all ModX resources in php? Because if they would also be html, that would make it more difficult to set up the ModX site in the root I suppose.

Before I installed ModX on the server, I played around with it in the ModX cloud. That should have given me a little basis of understanding.

All resources (and Elements, for that matter) are stored in the database, except for Static Resources (and elements). For Static Resources, the content field just holds a path to a file, and that is what will be used as the resource's content.

It is worth-while to take a look at your database, and especially look at the fields in the site_content table.

Hi Sotwell,

Yes, that is something which I already have done when working in the cloud with it. It's only the index.php which is localized in the root.
My problem was that I already created the whole website (it's quite a big one), when my friend asked me how he could do the updates. Then I realized that he can't work in html, and certainly not in Dreamweaver. It was a bit stupid of me for not having foreseen this.
I have never started with a website where I added the content management system after the creation of the site. ModX seemed to me the best option. It's another way of working where I still have to get used on, but it's coming, slowly. At least in the cloud I was able to see that ModX is capable of keeping the complete site structure, CSS, etc..

The only thing what still gives troubles is the way how Wayfinder handles the menu. Everything works as it should, except for the 'selected' page. But that will be something for later on, and I suppose also in another thread.

You've been most helpful, thank you so very much! I'm not a pro, never got an education in web design or web development. I'm learning it all on my own. This forum and you all are a true treasure for people like me