One of my sites is in the order of 2500 pages and is getting rather unwieldy.

www.grayspottery.co.uk

How would the community suggest I go about splitting this to make updates more easy to manage.

Logically, I would split it along content lump guidelines, what I'd like to know - and I guess others too, is practically how would I approach this task.

btw I'm using 2.70f

Thanks all

A

If you know how many projects your main project will be broken into, copy your main project that many times, renaming each sub-project appropriately. I would keep the main project intact as a back-up.

Open each sub-project and use the Page->Page Order... menu option. From this window you can easily delete the unwanted page from each project. The windows multi-selection shortcuts (Ctrl-Click and Shift-Click) work to select more than one page at a time.

If your project uses [page] type links, read Brucee's thread about massive page link corruption before you start. I don't know how extensive a problem this is, or if it is even a problem when you break up a large project, but you should be aware of the problem when deleting pages.

Thanks Larry

Due to being paranoid I'll take a completely safe copy first.

I also seem to remember that using the cut page button on the main toolbar can also mess up one's project (it happened to me) So I understand that using the Page/Page order delete button is safer. (I read Bruceees thread - eek!)

How would you advise cross linking sections of the site. I do have quite a few interlinked pages - as opposed to only linking through the main nav. Is it possible/advisable to use relative links between sections or should one use absolute links?

I know the [page] type link is a quick and easy way to make a link to another page in your project, but I very rarely use it. Instead, I just enter the name of the page and the extension in the URL box (this is the same thing that SS does when it publishes). I have never had a manually entered relative page link get corrupted.

There should be no difference between using absolute or relative links. The servers I have experience with will convert an absolute domain link referencing itself into a relative link. Using a relative link will save you some typing and possibly a few CPU cycles on the server as it converts the absolute link to a relative link.

As you will embark on wholesale page deletions, you may run into the page link corruption bug. If you have done few or no page renames in the past you should be fairly safe -- but still it is wise to be cautious.

I also suggest that you give each new project a unique project number (Options > Project Options) as otherwise all your new projects will have the same number as the original. Without correction, this may cause SiteSpinner to have images with exactly the same name in two or more projects. Then if you upload changes to one project, you may upset the images belonging to another.

Gentlemen. Wise words as ever.

I'll pile up me courage and when there's a gap in the updates I get I'll start teasing it apart.

What I had forgotten is that there's actually only 430 SS created pages, the other 2000 are generated by a spreadsheet page builder I created. so not as bad as I thought.

Thanks again.

A