|
Tailslide -> RE: FYi: latest cPanel update causing major problems for FP2003 generated sites (8/23/2005 4:48:22)
|
I had a look at the thread - there certainly seems to be something going on but they don't seemed to have pinned it down to a cause yet. Some of the posts: quote:
Over the past couple of days, FrontPage 2003 has suddenly started changing all my websites' home page file names from index.htm to index.html when publishing them to my server. In other words, the file names are not being changed locally on my PC, but they are being changed on the remote server as the files are being transfered. In searching for information on this, it seems to be the consensus that something has happened to the FP extensions on my server, so I reinstalled FP using the following: rpm -q frontpage chattr -R -i /usr/local/frontpage rpm -e frontpage /scripts/updatenow /scripts/updatefrontpage After reinstalling FP, I updated, all server and system software (including Apache), rebooted both my PC and my server (RHEL 3, WHM 10.3.1, cPanel 10.4.0-C160, WHM X v3.1.0), uninstalled and reinstalled FP extensions on my websites, and retried publishing FP sites with the same result (i.e. index.htm still changes to index.html on the remote server). There is also a suggestion on some forums that FP is sensing that my server default home page is index.html, so it is changing it for that reason. Given that I made no such changes to my server's defaults prior to this happening, does anyone have any idea what I need to do to correct this problem or work around it? quote:
We have the same problem. Started about a week or so ago. The only thing I can see is that each user has a postinfo.html in their www/public_html and it seems that is the file that tells the users FP what to post as. I dont know if it is suddenly being adhered to or if cpanel updates did something to make it used. I havent updated Apache on this server in a long time so I imagine it could be something CPanel is doing with FP stuff. quote:
Yes, I looked at the postinfo.html too and even changed its default from index.html to index.htm, but it didn't help. Somewhere, I assume, there's a setting that has been changed, but it's the needle and haystack routine that I'm trying to avoid. Btw, I have my server setup to do automatic CURRENT TREE updates, so I'm wondering if those updates might have done something weird to the configuration files or FP extensions. quote:
Lovely. It now appears to be doing this in the release tree. Anybody have a clue as to why frontpage would suddenly start acting this way? That's pretty much it so far.
|
|
|
|