|
|||||||
| View Poll Results: Do you want index.html or index.htm to be the first page to load? | |||
| index.html, thats the industry standard and the way it has been until just recently |
|
26 | 92.86% |
| index.htm, I have a lot of old school people still using FrontPage |
|
2 | 7.14% |
| Voters: 28. You may not vote on this poll | |||
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Which page do you want to load first index.html or index.htm?
Which page do you want to load first index.html or index.htm?
As some of you may have noticed index.htm no takes precedence over index.html Mind you, index.html is the industry standard, and was the first page to load with cpanel for the last at least 6 years. Tech support said they now make index.htm load first to accomodate the shrinkingly small number of FrontPage users out there, even through FrontPage is an obsolete piece of software (Expression Web has been Microsofts new design tool for years) Even if you change httpd.conf and run the distiller, it does not save you directory index order if you have changed it to load index.html first. This causes sites of my clients not to load if they have a index.html and index.htm page. Please vote on the poll whether you want index.html to load first or index.htm. |
|
||||
|
Why not just set the directory order to be whatever you want it to be in WHM -> Service Configuration -> Apache Setup -> DirectoryIndex Priority?
__________________
Want our technical analysts to login to your server to assist you? You can contact our technical analysts at: http://tickets.cPanel.net/submit |
|
|||
|
It says I need to recompile apache after doing that:
For your changes to take effect, the Apache configuration must be rebuilt and Apache restarted. I have quite a few servers, so that would take some time to do. Why do you make the everyone have to change it back to the industry standard to satisify the very few people who complained that frontpage wants index.htm to load first? Shouldn't they be the ones that should have to go in and change it away from the industry standard if they want index.htm to load first? Also it must be only a problem with some people who use frontpage, because I have never had any users having that problem, so you are deviating from the industry standard to convenience a minority group of a minority group of people (the people who actually had the problem out of the people who are actually still using the out of date frontpage) and inconvenience everyone else. Does that make sense? Last edited by BianchiDude; 03-27-2008 at 05:17 PM. |
|
|||
|
Not to mention that half the time when recompiling apache you have to hold your breath and hope that everything restarts OK again.
|
|
|||
|
Quote:
it's really a pain and I can't understand why this was done (the vast majority was more afected by this change than by leaving this alone) at least that's what I think. |
|
|||
|
We have a large number of servers, and changing the DirectoryIndex Priority on all of them would take a considerable amount of time to do. Not to mention the unreliability of EA3 and the fact that it's overwritten every compile means that it would take even more time.
The change on your end probably involves moving an l from one end of a line to another, which is a lot easier than altering settings on dozens of servers and recompiling Apache on them, which would probably be more prayer to recompile Apache than code. Also, the poll mentions .htm for FrontPage. It's no longer being sold by Microsoft, and the FP extensions on our servers only actually work properly once in a blue moon. Kindly reconsider your decision to change the default priority. |
|
||||
|
Quote:
It was NOT a problem. Anyone that has a problem with Frontpage and it's use of .htm is just someone who doesn't understand the basics of the 'index' page. Why deviate from the 'Standard' for those few who don't know the basics? |
|
|||
|
Quote:
|
|
|||
|
Quote:
You do *not* have to rebuild apache by any means. All you have to do is push the 'Rebuild Configuration and restart apache" button below that statement you referenced. I just did it on a server and pressing takes about 2 seconds before its done. HTH |
|
|||
|
Quote:
Will create a case internally for the httpd.conf generation folks to fix that. Will update here once its fixed. |
|
|||
|
Quote:
Also, the running the distiller does NOT save that change either: # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Direct modifications to the Apache configuration file may be lost upon subsequent regeneration of the # # configuration file. To have modifications retained, all modifications must be checked into the # # configuration system by running: # # /usr/local/cpanel/bin/apache_conf_distiller --update # |
![]() |
| Thread Tools | |
| Display Modes | |
|
|