My FP2002 slowly becoming worthless...

[John Patrick]

It started several months ago with parse errors. Once my website hit about
1000 pages, I could no longer save my masthead which is included on every
page in my web. The save would work...but FP would lock and I'd get a parse
error after about 30 seconds. I learned to live with that. I have also
been plagued by FP lock-ups that result in the CPU pegging at 100%. It now
happens 6 or 8 times a day, usually (but not always) when I'm attempting to
navigate to a hyperlink target. This is where I'm at now with my 2000 page
site: I can no longer do any sort of search and replace (CPU 100%) and I
can no longer run any reports (CPU 100%). In fact, I can't even open the
web on my HD and publish it with FP. Attempting to use the "Publish"
feature results in CPU 100%. I can only open the live web, make changes,
and save (except, of course, for the included pages).

I have three FP2002-built websites on my server. Two are smallish (less
than 100 pages), one is about 2000 pages. The 2 smaller sites are flawless.
No problems. I figure the FP extensions must be fine. The large site has
become a nightmare.

Subwebs? Apparently, included pages must be from the same web, so it
doesn't look like that will work.

Does anyone here manage large sites with FP2002?

My site: http://www.motorcityrock.com

I'm open for any and all suggestions...

jp

 

[John Patrick]

I forgot to mention...

I've emptied all FP TEMP files, .WEB files (including any hidden), my IE
Cache...and I can no longer re-calculate hyperlinks (CPU 100%)

I've got over 700 megs of RAM, an 800Mghz Athlon and over 3 gigs of free
disk space. I'm running WIN2000 with all the latest updates/SP's.

jp

 

[Jim Buyens]

I can think of two solutions:

1. Subwebs. Yes, I know, you'll have to duplicate your
included content, and that's bad, but better than
the current situation.

2. Database. Why do you have 2000 pages? If it's for
2000 product listings, put the product information
in a data base and then write an ASP or ASP.NET
page that displays any item based on item number.

Similar approaches are possible with document files
and other kinds of templates. Rather than merging
content and formatting at design time, you merge
them at browse time.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Rick Budde]

You might want to consider that you are trying to "go to
the moon" (manage a 1000 page website) in a "Model T" (an
old computer).

I don't know what size hard drive you have as you only
state how many gigs you have left. My personal experience
is that hard drives (for some reason I cannot explain)
appear to slow down terribly (even when defragged
reguarly) when the reach the 25% remaining stage. I am
not sure if this is related to your problem but it is
something to consider.

 

[John Patrick]

You might want to consider that you are trying to "go to
the moon" (manage a 1000 page website) in a "Model T" (an
old computer).

I don't know what size hard drive you have as you only
state how many gigs you have left. My personal experience
is that hard drives (for some reason I cannot explain)
appear to slow down terribly (even when defragged
reguarly) when the reach the 25% remaining stage. I am
not sure if this is related to your problem but it is
something to consider.

It's an 80 gig drive, I've got 8.25 gigs left right now.

 

[chris leeds]

if I were you, regardless of the computer, I'd look at a logical way to
break it into subwebs. it'll be easier on your computer and it'll make
systematic publishing much faster.
HTH

 

[John Patrick]

if I were you, regardless of the computer, I'd look at a logical way to
break it into subwebs. it'll be easier on your computer and it'll make
systematic publishing much faster.
HTH

OK,

My site has about 2500 pages and 3-4 gigs worth of JPEGS, MP3's and WMV's.

Currently, I have a folder for the Bands. Within that folder is 611
folders...one for each band. Inside each individual band folder is separate
folders for MP3's, photos, or whatever content I have for that artist.

If I create separate subwebs for each type of media listed above, will that
make things more manageable?

jp / www.motorcityrock.com

 

[Randy Birch]

I personally wouldn't make 611 subwebs, but would consider breaking the
existing contents into separate categories, perhaps based on genre or home
state/location of a band, and making each of those a subweb. Just be aware
that shared/common elements apparently are not supported across subwebs (eg
an include file must reside in the current web).

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: : > if I were you, regardless of the computer, I'd look at a logical way to
: > break it into subwebs. it'll be easier on your computer and it'll make
: > systematic publishing much faster.
: > HTH
:
: OK,
:
: My site has about 2500 pages and 3-4 gigs worth of JPEGS, MP3's and WMV's.
:
: Currently, I have a folder for the Bands. Within that folder is 611
: folders...one for each band. Inside each individual band folder is
separate
: folders for MP3's, photos, or whatever content I have for that artist.
:
: If I create separate subwebs for each type of media listed above, will
that
: make things more manageable?
:
: jp / www.motorcityrock.com
:
:
:

 

[John Patrick]

Randy,

Thanks for the reply. I wasn't thinking of making 611 subwebs. Rather, I
was thinking of making a subweb for the MP3's, a subweb for the JPEG's,
etc...

I was wondering if separating the HTML pages from the multimedia stuff will
resolve my parsing problems.

jp

 

[chris leeds]

well, see, here's the thing. FrontPage keeps each subweb as a separate
entity so you'd have to break it down in a way that makes tactical sense.
give me a link to your site.

 

[Randy Birch]

I'd think the difficulties in creating and maintaining each page and
navigating between subwebs for the different data a page might contain would
negate any organizational benefit. Besides, while FP will automatically
update the file URLs when a site (web) is reorganized, I don't believe FP
will track changes occurring in subwebs, as these are seen as individual
entities.

For example, when all files are in the same web files can be repositioned
anywhere in that web and FP will dutifully track and update all URLs
pointing to that original file (ie \wombat\wb3.mp3 is moved to
\mp3s\wombat\wb3.mp3). If mp3 was a subweb and the file is moved, the page
pointing to the original mp3 file would remain unchanged.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: Randy,
:
: Thanks for the reply. I wasn't thinking of making 611 subwebs. Rather, I
: was thinking of making a subweb for the MP3's, a subweb for the JPEG's,
: etc...
:
: I was wondering if separating the HTML pages from the multimedia stuff
will
: resolve my parsing problems.
:
: jp
:
:

 

[John Patrick]

www.motorcityrock.com

 

[John Patrick]

If mp3 was a subweb and the file is moved, the page

pointing to the original mp3 file would remain unchanged.

Randy,

I just verified this. Would re-claculating the hyperlinks on the main site
correct this?

jp

 

[Randy Birch]

No. Once the file is located in another subweb ... from FP's POV it might as
well live at www.yahoo.com. It's outside the current web, so FP no longer
tracks changes to the file's location. A recalculate - while never a bad
thing - won't compensate for this issue.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: > If mp3 was a subweb and the file is moved, the page
: > pointing to the original mp3 file would remain unchanged.
:
:
: Randy,
:
: I just verified this. Would re-claculating the hyperlinks on the main
site
: correct this?
:
: jp
:
:

 

[John Patrick]

So,

I_can_ move MP3's and other multimedia content to subwebs, but I would have
to be careful to manually update links on the main web if I rename or move
files in the subwebs.

My question: would using subwebs in this fashion stop the parsing errors and
allow me to better manage my sites HTML?

jp

 

[Steve Easton]

fwiw.
Yep, it was a slow day at the office.
There are a few html errors on the home page which if corrected will speed
things up.

<link rel="stylesheet" type="text/css"
href="http://www.motorcityrock.com/main.css"><style fprolloverstyle>A:hover
{text-decoration: underline}

also there's another set of style tags right below the body tag.

<body bgcolor="#000000">
<style>
a { text-decoration: none }
</style>

And the extra closing quote in line 43 valign="top"" is causing 79
consecutive errors the browser has to parse to display the page.

However, to me your web directories look fairly well structured and
shouldn't cause problems

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

 

[Thomas A. Rowe]

Good idea to move the media files to their own subweb, this way FP doesn't
have to manage them, and you can then use a FTP application to upload them.

To set this up, move the media files to their own folders from within FP,
this will update the paths to them, once this is done, then select the
folder and convert to web (subweb).

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[chris leeds]

what I'm thinking Steve, is if he can make his biggest folders subwebs he'll
have a much better experience with the publishing.
you may have some short term hassles making sure the necessary images are
within the subweb they pertain to but once all that stuff is done it'll be a
better way to maintain it.
I'd also think if there is a section that gets updated frequently that'd be
another good candidate for turning into a subweb too.
IMHO

 

[Randy Birch]

I also found restricting the folders that index server indexes for the
search page, if any, also shortens the overall upload & updating times.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: what I'm thinking Steve, is if he can make his biggest folders subwebs
he'll
: have a much better experience with the publishing.
: you may have some short term hassles making sure the necessary images are
: within the subweb they pertain to but once all that stuff is done it'll be
a
: better way to maintain it.
: I'd also think if there is a section that gets updated frequently that'd
be
: another good candidate for turning into a subweb too.

 

[chris leeds]

I think there is just too much "stuff" for fp to try to organize and manage
for this guy. it'd be different if the computers on both ends were cutting
edge but even then why beat on them when some good "subweb architecture"
would make it easier all around.

Randy,
I see where you're a VB MVP. Any Suggestion (book, link, or other) to
someone who wants to start using that app and has no experience with it?