Hi,
Hope someone can help I've installed cms made simple on a server where there is a current site already using index.php. This site will eventually be replaced by the one I'm building but for the time being the client wants to keep it up while we build the new site. So I need to change the name of the index.php file in cms made simple - I've done this (changed to index2.php) and installed it all and it all works fine apart from you can't navigate around the site because when you click on one of the pages it uses the query string index.php instead of index2.php - is there a way to change this?
Thanks for your help!!
Change name of index.php
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Change name of index.php
No there isn't.
The better mechanism to work with 'staging' sites is to put the install into a sub directory and then when time comes to move it live just move the files up one level and change the config.php and clear the cache.
The better mechanism to work with 'staging' sites is to put the install into a sub directory and then when time comes to move it live just move the files up one level and change the config.php and clear the cache.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Change name of index.php
Ok thanks for the prompt reply. I've actually figured out a work around for the time being I've used this in the menu manager:
menutext}">{$node->menutext}
Basically hardcoding in the name of the page, I will then alter the menu manager once the site is up and running.
Cheers
Jon
menutext}">{$node->menutext}
Basically hardcoding in the name of the page, I will then alter the menu manager once the site is up and running.
Cheers
Jon
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Change name of index.php
That's only part of the solution.
You may have problems with links created by modules, and other plugins which all use a standard mechanism to create URLS.
Working in a subdirectory is the best solution.
You may have problems with links created by modules, and other plugins which all use a standard mechanism to create URLS.
Working in a subdirectory is the best solution.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Change name of index.php
@calguy - I agree that separate development and production environments are the preferred way to go.
However, what do you think of adding a config variable in config.php, something like "$cms_index_page", where the user could force a sitewide homepage change? For example, setting this variable equal to "index2.php" would then allow the core at least to use index2.php to build urls, etc. Obviously 3rd-party modules would have to support this separately, and that would be up to the module developer. I'm just thinking out loud, and there are probably reasons this is not a good idea...
However, what do you think of adding a config variable in config.php, something like "$cms_index_page", where the user could force a sitewide homepage change? For example, setting this variable equal to "index2.php" would then allow the core at least to use index2.php to build urls, etc. Obviously 3rd-party modules would have to support this separately, and that would be up to the module developer. I'm just thinking out loud, and there are probably reasons this is not a good idea...
