Large Site

[Guest]

My site is well over 500 mb. I don't do a full publish. I only publish each
file as I change it. Today I got a timed out message within a few seconds of
trying to publish. The dedicated server host recalculated hyperlinks and
reinstalled extensions but I'm stil getting the same error plus now I can't
save changes in my local. They're telling me that FP 2003 can't handle sites
over 500 mb but I have trouble believing that. I'm on broadband. Thanks.

 

[Thomas A. Rowe]

No matter which version of FP you use, you should break your site into smaller more manageable
sections (subwebs/sites), as the issue can be with your Internet connection as well as how the host
server is configured, amount traffic coming into the web host, etc.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

How would that affect what's happening on my local when I try to save? I make
a change and try to save and get the error, "An error occurred accessing your
Windows SharePoint Services site files." I click OK, it asks me again if I
want to save and I say No but it goes ahead and saves the changes anyway.

 

[Thomas A. Rowe]

My response related to the timeouts when publishing.

As far as you local saving issue, when it the last time you deleted all of your temp file, recycle
bin, FP temp folder, the FP *.web cache files, run a scandisk and defrag?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

Thanks for the help. I figured my local file got corrupted somehow so I did a
reverse publish from the remote to a new folder on the local and everything
is working great from that end.

I'm on a dedicated server. It has plenty of space and my site is around 700
mb. The thing is, I only publish one file at a time so timing out is
typically not an issue. I don't know how many times the host has told me that
FrontPage can't handle large sites and that I'm bound for problems the bigger
the site gets and then they recommend that I change to a different program.
It seems to me that if I am only publishing 30-50kb files one at a time, the
size of the site itself shouldn't matter and the program I use shouldn't
matter.

I want to stay with FrontPage. What do you think of the host saying that
FrontPage can't handle a site of this size?

 

[Ronx]

When you publish a page using FrontPage, each and every page in the
web is checked to see if the published page will affect it - the page
just published may be included in another. A large site will
therefore take a long time for the process to complete, and on some
systems will time out.

The point at which time-outs become significant varies from system to
system, and is dependant on server hardware, server load, size of web,
size of files, and (possibly) phases of the moon. As Thomas said,
splitting the web into subwebs will lower the risk of time-outs, since
smaller numbers of files need to be checked in each subweb.

There is no limit to the size of web that FrontPage can handle - but
there is a limit to what the server can deal with in a specified time.

If you cannot split the web, then consider publishing with FTP. You
will lose the ability to use FrontPage extensions and everything that
that implies, but time-outs should disappear and you can continue to
use FrontPage as an editor. However, should your local web become
corrupt again, you may not be able to retrieve it from the server
without a lot of work (depends on what author time components are
being used) since using FTP does not upload some FP information to the
server.

 

[Thomas A. Rowe]

Publishing individual files is a bad idea, as only the actual file is uploaded, no references or to
anything external to the file is published or updated on the live/remote server when you use
Selective Publishing.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================