Forum Moderators: open
Does anybody have an idea as to what the problem is?
Can you pinpoint when the problem started? Did you install any programs just prior to that? Any major updates to security software, etc.?
I have noticed in the last few weeks that occasionally when I right click on a file that is to be published, sometimes it just sits there, or continuously publishes in an endless loop and never really publishes. I have been able to get around that by "Cancelling" the publishing, clicking elsewhere, then clicking back and republishing. It eventually worked last night, when I double clicked on the little icon before the file instead of on the filename itself.
-Rocky
Another issue at play here is the quality of the new host. How many other sites are on that server? Are you on a shared or dedicated IP? I would run some tests on the server to see if there are issues there.
I thought there may be something wrong with my Front Page Software, since it works sometimes and not others, and is beginning to get worse.
Do people have the same problems with Dreamweaver?
I have a very large website and have just begun having problems publishing my site to the web.
Large website? I checked out the Linux plan and depending on what package you chose, you may be meeting your maximum allowed storage and/or throughput, I can't really say.
Try publishing to a folder on your desktop instead. If you see the same delays, then yes, there is something wrong somewhere on your local system. If you don't see the same delays, then you need to look at the connection. If the connection is okay, then we need to look at the server. I'd be inclined to think that the upload to the server is where the problem lies. Either a throttle of some sort or some other issue related to uploading large chunks of data.
Could that be the problem?
Have you tested publishing to a local folder? Do that first so we can determine whether or not it is an FP problem or possibly an issue with the site itself.
You have four options for publishing from the Remote Web Site Properties tab. The last one in the list is for publishing to a File System. That is the one you choose and you either create a new folder or specify one that already exists and publish to that.
Create a new folder on your desktop. Call it something like 'test-publish.'
In Frontpage choose File > Publish Site...
Either the Remote Web site Properties dialogue will pop up, or you will see a message in the right-hand pane to choose that tab -- it's at the top of the pane.
In the properties dialogue choose File System and browse to the test-publish folder on your desktop.
Click OK. Click Yes when FP prompts you to create a web site at that location.
Let us know what happens.
-Rocky
-Rocky
I am noticing that it will take an unusual amount of time to pubish and sometimes it just continues to publish in an endless loop, with out really publishing anything. If I click off of it and click on it again and try to publish, then sometimes that works and sometimes it doesn't. I am now beginning to get messages saying something to the effect that it doesn't recognize the user name or it cannot publish to port 21. Sometimes it says it has timed out.
I had the exact same problem a little over a year ago. My site has over 25,000 pages and I thought the problem was everything but local. Came to find out that it was local and a new PC solved all of my problems.
What is the easiest way to do that without using many CDs? I use my PC for hours and hours everyday and it is about four years old.
Get a new drive and do a direct transfer.
I use my PC for hours and hours everyday and it is about four years old.
When is the last time you did a disk defrag?
Back to the matter at hand: With large sites FP can build up a bunch of gunk over time. It you haven't done so it might be time to clear some of it out.
The simplest fix in FP is:
Tools > Site Settings > Advanced > Temporary Files > Delete Files
This will get rid of the temp files that FP uses and does not clean out by itself.
Another fix is to clear Web Server Extensions Cache. The files here contain site and page settings and a heck of a lot of other stuff. They can get muddled and jumbled over time, especially with large sites and can affect publishing.
Be sure to do this only when FP is not active. I'm not sure what would happen if FP is running when these files are cleared out, but I have a suspicion that it might not be nice, causing a lot of confusion at least. Once cleared out and you reopen a site in FP it will rebuild the needed files.
The files have .web extensions and might be in different locations depending on whatever Win OS you use. In WIN2K Pro they're located in:
Documents and Settings > YourUserName > Application Data > Microsoft >
Web Server Extensions > Cache
Or just search for *.web
They will usually be named something along the lines of:
server_80_example.web
Delete them, restart FP, open your site, and it might run a bit faster. There are a couple of FP cleaning utilities that will do this for you, but it's simple enough to do yourself here and there, maybe once every couple of weeks or so.
<added>And a 'me too' on the disk defrag :)</added>
I had additional drives put in my same computer last summer. Are you saying to purchase some more drives and replace the initial ones that were in the machine?
And what is direct transfer? Does this mean to go into Windows Explorer and simply move them over by dragging and dropping to a new drive?
I did a disk frag about six months ago.
I did a disk frag about six months ago.
[6]YIKES![/6]
Might I suggest that you stop everything you are doing, close down all applications, restart, and perform a disk defrag. If you are using your system as much as you say you do, you should be defragging weekly, it's a Windows thing. I'm not sure if the Unix Geeks need to do this.
And, if you are using FP and other MS applications throughout your day, you definitely need to defrag once a week. That really is the only true way to keep a system running at maximum efficiency. If you have Norton System Works, you can go one step further. :)
Thank you. I wondered if there was some way in Front Page to clean up the garbage. I will definately the temporary files. Now is this done in Front Page or do I do it in Windows Explorer like have done before for other things.
I don't understand the second fix, though (to clear Web Server Extensions Cache. I have Windows Explorer for Windows 2000. I assume that I open up Windows Explorer. Then do I go to Documents and Settings in the C Drive or do I go to the drive that my website is in? Where does it ask you for my User Name? And is it the user name that I use to Publish my Front Page to IX Hosting or is there another User ID for my Windows which I have no idea of what it is, if there is one? If there is one for my Windows environment, how do I get it?
And once I open up Cache, do I delete ALL FILES in Cache?
Thank You. This is great stuff.
-Rocky
Regarding "Yikes". I didn't know how often it should be degragged. (I'll defrag tonight). I just learned what it was recently. I think there is another thing they called Disk Cleanup as well. Do I have to do that every week too?
My Norton Anti-Virus checks my system automatically every week for viruses. So, I think I am OK there.
Are there courses available with all of this stuff in them?
I would also like to learn how to keep somebody from coming into my system illegally and abstracting information from it. There is so much that I don't understand about this.
-Rocky
I've never seen anything except .web files in the Cache, usually one for each FP site. I don't for a fact know that there can't be more, though if your aren't running any other web-type applications except FP you should be fine by deleting all of the .web files. You should also be able to easily recognize the files as they should have the site's name in them.
Rocky, the first cleanup is through the FP Tools menu.
Can you believe for as long as I've used FrontPage (since it was Vermeer), I've never done any of the FP cleanup? It's never affected my work environment. I wonder if it's because I edit live at the server and publish back to local for backup?
Of course, the next 10 technical support people may say something different.
He told me it is better to use the internal publisher of Front Page.
He is absolutely correct. I wouldn't take the chance of breaking the FP Publishing Routine by using a third party product for FTP. There is much that takes place during a publishing routine and using the tools that FP provides all tie in with that routine. That's what all those _vti folders are for.
P.S. The vti stands for Vermeer Technologies Inc. Microsoft never changed this.
And the temp files are generated as you work locally. I'd assume something similar goes on when working live, though I have no idea whether they would be generated locally or server-side.
