Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: open
I don't own or use FrontPage myself, I'm a Notepad/Homesite/Dreamweaver/FTP kind of person. Is there anything I need to watch out for? I vaguely remember a problem with Front Page extensions clobbering changes made outside of FP with previous versions of a page ... or am I hallucinating?
I don't want to make any major changes as this is just temporary ...
You need to ask the current webmaster if they "Publish" or use FTP. If they use ftp, you will be safe enough.
The problem is that whoever normally does it will have a copy of the website on their computer, so any changes that you make will probably be over written next time they publish.
That is easily dealt with by the regular Webmaster publishing all changed pages/files back to his/her HDD on handover/takeover. It is only a problem if you are unaware that someone else has been editing the site.
Also, highly unwise though it is (madness actually), some webmasters edit pages live on the server and either never, or only occasionally backup to their own computer.
Would it be possible for me to shut off the FPSE while I'm maintaining the site, then have the original webmaster republish the site and turn them back on if/when they return? Or would it be difficult for them to do that? This is an extended absence due to an illness.
Anyone know if Dreamweaver has a way of maintaining FPSE compatibility? I'm pretty sure Contribute does, but that's so limited ...
Would it be possible for me to shut off the FPSE while I'm maintaining the site, then have the original webmaster republish the site and turn them back on if/when they return?
Depends what control is available to you at server level. If you have access to a Control Panel, you can usually do it yourself quite quickly and easily. If not, you'd have to ask the host to do it for you.
However, the ease or difficulty in removing FPSE is not the primary problem. IF the site has any components which are dependent on FPSE, they will break (not function or even be completely removed from all the pages e.g. navigation bars) if you uninstall the FPSE. Do not attempt to do it without "publishing" with FP, a complete backup to an off-site location first. As you don't have FP, that might be difficult.
Also, if removing the FPSE does break the site, you'd need access to FP to republish the backup after reinstalling the FPSE.
Here is the lists of components that are dependent on FPSE to function:
Commonly used ones are: Forms, search, navigation bars, sub-webs, DRW (database) etc.
Seriously, I think you'd be playing with fire to attempt to remove FPSE.
Anyone know if Dreamweaver has a way of maintaining FPSE compatibility?
Dreamweaver relies on ftp to get changed files on to the server. As I mentioned earlier, using ftp can corrupt the FPSE. And if you don't have access to FrontPage to publish a backup, the site would remain broken until the original Webmaster is able to do it.
(followed by a stream of unprintable expletives describing how I feel about Frontpage)
I could use the income from another account too <sigh> - but not badly enough to buy and install FP. I've taken over former FP sites, uninstalled the FPSE (after copying the site to my machine) and managed the site without problems but the possibility of having to put this one back is the issue ...