This means that if you host multiple sites on one box you should follow 
that technote to avoid what I call "class clash."  Most ISPs/hosting peeps 
will already have followed that technote...

~Todd


On Tue, 13 Aug 2002, Shawn Grover wrote:

> Does this mean that if I host my CFM pages on an MX server, I can't easily
> delete/modify my site files?  I ask cuz in most cases, I'd imagine an end
> user wouldn't have permissions to the folders in question...  (I'm not using
> MX yet, so may be showing my lack of knowledge).
> 
> Shawn Grover
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 13, 2002 1:51 PM
> To: CF-Talk
> Subject: RE: Ok.. Now THIS is REALY StRaNgE!
> 
> 
> Delete the class files from:
> CFusionMX\wwwroot\WEB-INF\cfclasses
> 
> And follow these direction:
> http://www.macromedia.com/v1/Handlers/index.cfm?ID=23179&Method=Full
> 
> These will resolve your caching issues.
> 
> ~Todd
> 
> On Tue, 13 Aug 2002, Lee Fuller wrote:
> 
> > Where?  And is this something that we're going to have to worry about
> > each time a customer deletes files?
> > 
> > This is our only MX box.. So I'm not sure if it will be a problem on
> > others we put together.
> > 
> > Thanks.
> > 
> > | -----Original Message-----
> > | From: Brook Davies [mailto:[EMAIL PROTECTED]]
> > | Sent: Tuesday, August 13, 2002 12:34 PM
> > | To: CF-Talk
> > | Subject: Re: Ok.. Now THIS is REALY StRaNgE!
> > | 
> > | 
> > | Try Deleting the compiled class files.
> > | 
> > | 
> > | At 12:13 PM 13/08/02 -0700, you wrote:
> > | >Here's the scenario:
> > | >
> > | >         1 - Shared IIS5/CFMX server
> > | >         2 - About 20 sites on this server -- 4 of which use CF.
> > | >         3 - Site in question has no special setup..
> > | Standard "site" in
> > | >IIS.
> > | >         4 - Site has no "data-driven" pages.. i.e., nothing that
> > | >builds a page based on DB criteria.
> > | >         5 - Client deleted some pages from the site.  All 
> > | of them were
> > | >static pages, but were .CFM's.
> > | >         6 - IIS continues to deliver these pages as if they were
> > | >there, except that it DOES recognize that the images associated with 
> > | >those pages are not there. (I.e., it shows them broken.)
> > | >         7 - If we recreate a page by the same name, and put just 
> > | >static text into the page, IIS delivers up the page with only the 
> > | >static text. (I.e., it displays exactly correct.)
> > | >         8 - If we then delete that page, the OLD content that was 
> > | >there in the page that was (and still is) deleted comes back.
> > | >         9 - This occurs over several dozen locations, many of which 
> > | >have never been to the site, prior to the deletion of the pages.
> > | >         10 - The Application.cfm file has nothing in it but 
> > | standard
> > | >control info.  Nada that would redirect or cause cache data to be
> > | >delivered.
> > | >
> > | >Ok.. So anyone have any ideas?
> > | >
> > | >TTAIA
> > | >
> > | >
> > | 
> > 
> 
> 
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to