Sorry if I just sent a blank email, something crapped out in gmail.

Anyway, thanks for the responses... It appears it was a combination of the
refcontainers and refobjects tables , combined with a custom plugin that
wasn't allowing things to load nicely. I got it to load, but I agree with
Marco that it would be useful to have a way of checking the reference tables
without loading the application.

Part of the problem is that as I am on a shared server, I don't have access
to the ColdFusion server software a la CFIDE.

Thanks,

Tomek

On Sun, Sep 28, 2008 at 8:30 PM, <[EMAIL PROTECTED]> wrote:

>
> ColdFusion comes with a component inspector ala java docs. I think
> it's in /CFIDE/componentutils.
>
> On 9/29/08, Marco van den Oever <[EMAIL PROTECTED]> wrote:
> >
> > Blair can you please further explain this to me, what document
> > inspector and how to use that in CFIDE to look at your components????
> >
> > On Sep 29, 1:14 am, "Blair McKenzie" <[EMAIL PROTECTED]> wrote:
> >> Try using the document inspector in CFIDE to look at your components. If
> >> there are problems instantiating the content components they will show
> up
> >> there.
> >>
> >> Blair
> >>
> >> On Mon, Sep 29, 2008 at 1:09 AM, Marco van den Oever <
> >>
> >> [EMAIL PROTECTED]> wrote:
> >>
> >> > Very hard to say from here, do you get any error statement or
> >> > whatsoever? Only thing i encountered was deleting a file while there
> >> > still was a reference for, then i deleted the reference and it was ok.
> >> > I bet you have more then one references there so if you updated /
> >> > restarted the application there must be still a mismatch i believe.
> >>
> >> > Might be an idea for one of us to eventually build a sort of
> >> > "reference checker", that works outside of de project application and
> >> > which can balance reference mismatches.
> >>
> >> > I will add this as a new feature request.
> >>
> >> > On Sep 28, 3:16 pm, "Tomek Kott" <[EMAIL PROTECTED]> wrote:
> >> > > Hi All, I'm having a major problem now. I deleted the reference for
> >> > > the
> >> > rule
> >> > > that hung from container and container_abojectids tables, and was
> >> > updating
> >> > > the site (since we had added some functionality) and now it won't
> >> > > initialize. It just hangs on the onRequestStart in application.cfc.
> I
> >> > > bet
> >> > > its a COAPI metadata problem, so there must be something in the
> tables
> >> > that
> >> > > I missed. Any ideas on what this could be or why onRequestStart
> fails?
> >>
> >> > > Thanks,
> >>
> >> > > Tomek
> >>
> >> > > On Tue, Sep 23, 2008 at 9:36 AM, Tomek Kott <[EMAIL PROTECTED]>
> >> > wrote:
> >> > > > Hi All,
> >> > > > I recently changed a rule definition and found it easier at the
> time
> >> > > > to
> >> > > > just delete the table, since I didn't have any containers defined
> >> > > > with
> >> > that
> >> > > > rule....or so I thought. Apparently one of my pages still has a
> >> > reference to
> >> > > > a non-existent rule and so won't load in designmode to get rid of
> >> > > > it.
> >> > In
> >> > > > non-design mode it loads normally. I have tried fixing the
> >> > > > refobjects
> >> > table
> >> > > > etc, to no avail.
> >>
> >> > > > I know that there are container and container_aobjectids tables,
> but
> >> > also a
> >> > > > rules_containers (or something similar). I was planning on going
> >> > through and
> >> > > > trying to match up UUID's that are causing the error, but I
> thought
> >> > > > I
> >> > would
> >> > > > ask first if anyone had dealt with orphan containers before and
> how
> >> > that
> >> > > > worked out for them or what they did.
> >>
> >> > > > Thanks,
> >>
> >> > > > Tomek
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to