frontpage 29,000 page site?

[injured]

hi all, i have a 29K page site that i currently run through FP2003...its a nightmare!

i found a few interesting threads here that sound oh so familiar....and am wondering what wysiwyg editor can cope with as many pages? or any suggestions to make it easier.

i have a lot of seperate folders, no subwebs, the problem is i am wondering if i convert some stuff to subwebs...will frontpage DO the conversion..I tried to delete a folder with 400 pages in it last week...and FP just froze like it was in the headlights!

i have considered SSIncludes...but dont want to change all my urls to .shtml as that will wave goodbye to my google positions. I have about 7 includes on each page...so thats about 200,000 altogether and if i change one...i can drive 10 miles do some shopping and get back in time to see it finish the change.

can dreamweaver cope any better or would i be wasting my time if i changed

thanks for any and all help.... off to do some more shopping ;)

Injured :-)

[Corey Bryant]

You will always run into some problems with any editor managing that many files.

When you try to delete that folder - shut down FP and do it via your explorer. Then open FP back up, go to Tools - Recalculate hyperlinks - that should fix the problem of the missing pages.

Sub-Webs would help you though tremendously, unless you are using FP navigational structure

-Corey

[Wlauzon]

IMO 29k in one section is too much for any editor.

I don't think Dreamweaver would help that much, since the problem is the quantity of pages. A global change is a global change no matter what editor you use.

I cannot imagine a 29k page site with no subwebs...

[bhartzer]

You're probably going to be better off looking at some of the content management systems out there and "importing" all those pages into the system.

There are plenty of good CMS apps out there that will handle it. Last time I checked CNN had over 400,000 pages, and this site has over 250,000 pages indexed.

[injured]

<<Last time I checked CNN had over 400,000 pages, and this site has over 250,000 pages indexed.>>

thats what i mean...i can't picture some guy slaving away because frontpage keeps disconnecting during an upload :-)
obviously they have the financial resourses to call the shots.

so bottom line guys... i like frontpage , and i find it incredibly easy to use...its hell slow as the sites so huge.....
but you reckon NOT to change to DW as that will suffer too?

[airwhale]

I say you need a content management system, right about now. A site that huge requires some industry strength tools. I'm currently on the server operations side of some HUGE FrontPage webs with multitues of sub-webs, and it's a true nightmare. User permissions is one of the worst issues at the moment.

If you decide to stick with FP, my advice is to keep close documentation of the user rights for each part of your site. We're about to remove ALL FP-extensions for the site and re-apply it, but we're being held back because no-one really knows who does what where.

peace,
Tormod

[injured]

i had the extensions reinstalled last week..it took 3 DAYS! apparently the host tells me, and i quote..
"they just kept timing out, your site is too big"

and yet i have only used 60,000 files of my
1.1 million allowance... figures huh? how can these new systems NOT cope? whats the point in giving so many files allowed if it wont handle it....

[Wlauzon]

That brings up a question for me... How DO these huge sites cope?

For us, anything over 5000 pages gets to be a problem.

We are just now starting to look at some CMS programs, but are pretty clueless so far as to what to even look for.

[bhartzer]

Since you're obviously stuck on using a Microsoft product, have you looked into using SharePoint? You can still use Frontpage, but Sharepoint seems to be able to handle that many pages.

[bill]

i have considered SSIncludes...but dont want to change all my urls to .shtml as that will wave goodbye to my google positions.

I'm not exactly sure how you do this on IIS, but with *nix servers you can set the server to handle all .html pages as .shtml. This means you could keep your current page names, but just have the server parse them for includes.

However, 29K is pretty large. bhartzer's suggestion may be a good one...SharePoint.

[injured]

i know 29,000 pages sounds like a lot,

but its only 540 folders with 50 pages in each,
and some image folders.

...it hardly sounds like rocket science,
although putting a man on the moon sounds easy right now.

regarding SSI....i was informed previously that in order to run them, all files had to end with .shtml
if there IS a way to keep them as .htm as mentioned in this thread, i am keen to know.

[Nutter]

What web server does your host use (Apache, IIS, other)? If it's Apache, I can help. IIS - never used it, can't help.

[Corey Bryant]

You can contact your hosting company to ask them to parse HTML as SHTML files actually

-Corey

[jk3210]

injured-

I run a site that passed 10,000+ pages last year and I hit the same problem.

I did a "Convert to Web" on numerous 1,500 page folders and it helped *tremendously*. Once you do that, FP no longer checks those pages during a publish, so it *usually* won't freeze on you.

If you go to make changes to the folders you've converted, FP will open that folder as a new web (no biggy).

[europeforvisitors]

The short-term solution is just to divide the site into a lot of subwebs (500 to 1,000 pages per subweb is a good limit). If necessary--e.g.,if "convert to subweb" freezes--try rebuilding the site's structure without the content and importing the pages into that.

Once your subwebs are of reasonable size, you'll be able to publish any of them quickly. (Although, if you want to publish all 29,000 pages in a single morning or afternoon, you may have a problem even with subwebs!)

[cooldoug]

Usually when I am working with large files, I do it overnight. Just tell it to upload, turn off the screen, and go to bed. For really big files(1gig+) I split it up. Half tonight, half tomarrow night.