Need New Idea for Archiving Old Content

[David B.]

Greetings everyone,

I think I need a new approach to a problem I am having,
and was hoping someone here might have a thought or two.

I have a website which changes content on a weekly basis,
basicaly a website for a newspaper with newsarticles and
photos.

I want to maintain backissues on the site, and currently
do so. I had been doing it this way, publishing the
entire website to another folder /backup/06-10-04 for
example. This worked well. The only hitch is that I am
duplicating much material. The site is growing at a
steady pace of about 4 mb a week. I would like to slow
down this growth by having the graphic - database -
stucture - photos of the site centralized.

I have created subwebs containing all the graphics used on
the site. The photogallery option I am using, too was
converted to a subweb. All the common photos have been
placed in a subweb. I have made the fpdb into a subweb
also.

Making the common components into subwebs allowed me to
only publish the changes made to the html files, (so i
thought), without haveing to copy the whole sturcture.

Problem is front page wants to manipulate the links. When
I publish the web to the subweb folder, all my links get
out of wack. This is a three ring circus, with a work
computer at the office where I do the content, a home
computer that I will do late work on, and the server
computer at the ISP. When I publish the html files to the
backup subweb, all graphics and photo links get confused
as to location . . . ../../backup/6/10/04
or ../../photos/6-10-04basball1.jpg. This forces me to go
back into the back issue site and manualy set ALL the
links to the resource files by hand.

So, does someone have an idea for a more efficent way to
handle this type of archiving?

Thank you so much

David B.

(e-mail address removed)

 

[Thomas A. Rowe]

Use absolute URL between pages and images, however you will then have to manage manually as FP can
not manage them.

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

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

 

[Guest]

Exaclty! lol

That is the problem I am trying to avoid, having to manual
reset the links for each resoure file week after week
after week after week....<melodramatic pause>

I was thinking there should be a way to do this
programaticly, maybe via ASP? For example some way to set
the current weekly URLbase=something ah heck I don't know.

Just typing this messagne though has given me an idea or
two. Funny how that works.

Thanks for the reply.

-----Original Message-----
Use absolute URL between pages and images, however you

will then have to manage manually as FP can

 

[Thomas A. Rowe]

Yes, it could be done with a ASP, but all of your pages must have the .asp extensions and any FP
run-time components will need to be replaced with similar ASP based functions.

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

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

 

[Stefan B Rusynko]

Try a cleaner approach that will leave your relative links alone

Put everything back in your root web (convert the subwebs back to folders)
Create a folder just for your variable weekly content and consolidate all your common (reusable) images / media in other folders
- name the current week folder as say: Latest
- convert it to a subweb
Convert each other old week's folder (archives) into a subweb (say archive06-07-04 , archive06-14-04, etc)

At the end of a week Open the subweb Latest and publish to a new archive - say archive06-21-04
Then edit the content in Latest w/ your current info (add new variable images, delete unused images, etc)

--




| Greetings everyone,
|
| I think I need a new approach to a problem I am having,
| and was hoping someone here might have a thought or two.
|
| I have a website which changes content on a weekly basis,
| basicaly a website for a newspaper with newsarticles and
| photos.
|
| I want to maintain backissues on the site, and currently
| do so. I had been doing it this way, publishing the
| entire website to another folder /backup/06-10-04 for
| example. This worked well. The only hitch is that I am
| duplicating much material. The site is growing at a
| steady pace of about 4 mb a week. I would like to slow
| down this growth by having the graphic - database -
| stucture - photos of the site centralized.
|
| I have created subwebs containing all the graphics used on
| the site. The photogallery option I am using, too was
| converted to a subweb. All the common photos have been
| placed in a subweb. I have made the fpdb into a subweb
| also.
|
| Making the common components into subwebs allowed me to
| only publish the changes made to the html files, (so i
| thought), without haveing to copy the whole sturcture.
|
| Problem is front page wants to manipulate the links. When
| I publish the web to the subweb folder, all my links get
| out of wack. This is a three ring circus, with a work
| computer at the office where I do the content, a home
| computer that I will do late work on, and the server
| computer at the ISP. When I publish the html files to the
| backup subweb, all graphics and photo links get confused
| as to location . . . ../../backup/6/10/04
| or ../../photos/6-10-04basball1.jpg. This forces me to go
| back into the back issue site and manualy set ALL the
| links to the resource files by hand.
|
| So, does someone have an idea for a more efficent way to
| handle this type of archiving?
|
| Thank you so much
|
| David B.
|
| (e-mail address removed)
|