This is a bit more complex solution than what I think your looking for right
now, but might be helpful to you when you start doing your redesign and
start using the FuseBox way...
I accomplished what your talking about by breaking the content of a site up
into what I call ContentObjects. Each object is a FuseBox application
comprised of the following pages: act_Insert, an optional act_processing to
deal with form validation, act_Update, dsp_Add, dsp_Display, dsp_Update,
qry_Query, and an index page that let's you browse the records and has a
standardized layout to add an object, add related links to an object,
update, delete, and view an object. The display page has processing in it
dependant upon attributes sent to it by a custom tag that interacts with
each of the object fuses so that you can (for example) either display news
headlines or a news story on the actual website just by sending an attribute
to the fuse. There is security in place so that you have a ContactID of the
person performing an action on an object. Each time an action like add,
display or update happens the person that performed the action and the date
and time is stored in the same table as the object. That way you know the
original date it was entered, who entered, when it was last updated, and who
last updated it. Pretty soon I'm going to be able to take it to the level
of entering a table name and having the object fuse built automatically
using generic templates based on the structure of the database so that the
only actual code you have to write to introduce a new object is special
processing and tweaking the display page.
It's a bit more complex a solution than what I think your looking for right
now, but might be helpful to you when you start doing your redesign ...
-----Original Message-----
From: Allen Hudson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 17, 2000 9:42 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: last modified date of file
I recently took over maintaining some websites where there is a requirement
to have a "last modified" date at the bottom of every page. This is
currently accomplished by the <cfinclude> of a footer template which has a
date hard coded into it. However, some of the pages change more frequently
than others so I want to implement a way (other than hard coding it if I
can) of checking the main template's date and displaying that.
Our particular site is hosted at a public ISP on a shared NT box (CF4.01)
where it appears the CGI server side includes are turned off. (my web server
knowledge is not great so please correct me if I have made some wrong
assumptions.)
I attempted to use the simple javascript in the footer. (My javascript
skills are basically at the cut-and-paste level)
<script language="javascript">
document.write(document.lastModified);
</script>
Netscape gives me Dec 31, 1969 while IE displays the footer's date. Putting
the code in the main body of the template gives the date I want in IE but
Netscape(4.61) says we're starting the 70's again (a horrible prospect IMHO)
Any suggestions as to how I might proceed or what I may be doing wrong?
An additional question - given that I am a fan of the fusebox methodology
(though our current sites are not coded to such, the new ones will be), how
could one satisfy the last modified requirement on each page without
hardcoding the date?
Al Hudson
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
