So did you replace all paths in the MachII core with "app_MachII" since you're 
not using the supported path? Mapped paths for common frameworks on shared 
hosts is a big no no anyways. Your host should really have a policy against it 
or use a "username_MachII" approach for mappings or use app specific mappings 
(if using CF8 or other engines).

I suspect your application is not being reloaded as you suspect it is. 
You might consider setting a local development machine with CF8 dev editition 
(free) and Apache. It's much easier to test / develop apps locally.

.Peter


-----Original Message-----
From: David D-V Tran <[email protected]>

Date: Sat, 22 Aug 2009 14:19:35 
To: <[email protected]>
Subject: [Mach-II] Re: dtd



I'm on a shared hosting service...
yeah someone else already mapped machII on my server so I had to name
it app_machII...

On Sat, Aug 22, 2009 at 2:16 PM, Matthew Woodward<[email protected]> wrote:
> David D-V Tran wrote:
>>
>> There is no output on resultArg, but there is one for resultkey. and
>> It doesn't recognize that arguments.event.getArg("title") exists... I
>> converted the listeners invokers :
>
> Did you restart your CFML engine?
>
> I also notice you have "app_MachII" instead of just "MachII"--you sure
> you're pointing to the right stuff?
>
> --
> Matthew Woodward
> [email protected]
> http://www.mattwoodward.com/blog
>
> Please do not send me proprietary file formats such as Word, PowerPoint,
> etc. as attachments.
> http://www.gnu.org/philosophy/no-word-attachments.html
>


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to Mach-II for CFML list.
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/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets: 
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
-~----------~----~----~----~------~----~------~--~---

Reply via email to