Hi Dan,
I may very well look at doing this once the final core build of the site is complete. We're aiming to launch in a few months so I'd probably do this fairly late on. At the moment MG2 is providing everything I need, but I must admit I haven't fully looked into the new feature set yet so will plan to do that at some point soon. I have a new project I'm aiming to start shortly so will probably jump straight to MG3 from the start of that one. Cheers, James. --- James Allen E: [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Dan Wilson Sent: 08 April 2009 14:17 To: [email protected] Subject: [Model-Glue] Re: Model Glue 2 and SES Url James, Our goal is 100% backwards compatibility. I've been able to make it work on every application I've converted. I'd be interested to hear your experience. DW On Wed, Apr 8, 2009 at 9:13 AM, James Allen <[email protected]> wrote: I know it's not directly related but regarding MG3, is it completely 100% backward compatible with MG2? I have a big site running in MG2 at the moment and was wondering how safe it would be to upgrade it to version 3. --- James Allen E: [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Dan Wilson Sent: 08 April 2009 14:08 To: [email protected] Subject: [Model-Glue] Re: Model Glue 2 and SES Url Bud, I'm no expert on SES URLS so I can't really help you in that respect. I can say that you'd be saving yourself a lot of time by migrating to the MG3. I can understand your preference for working with MG once it hits beta. Frankly, the codebase for Alpha IS the beta, minus the scaffolding piece. So, if you aren't using scaffolding right now, then go for MG:3. It was designed to work with SES URLS. DW On Wed, Apr 8, 2009 at 8:58 AM, Bud <[email protected]> wrote: Hi. I'm new at MG. I'm trying to get MG 2 to work with search engine safe URLs. I've built a simple method to add to the controller that is called onRequestStart. The method uses the event.setValue() function to set the name/value pairs. They all get set properly, however the event-handler does not call the correct event. If I use page.cfm?event=test the event handler "test" is called. But if I use page.cfm/event/test/, the default event handler is called, even though a dump of event.getAll() shows that event has been set to "test". Why is this? A developer comment inside the Controller says "Any function set up to listen for the onRequestStart message happens before any of the <event-handlers>." Any workaround with this? I see that MG 3 has a URL manager but I'd prefer to wirk with MG 2 until MG 3 is out of beta. Thanks. I'm looking forward to getting my feet wet with MG. I've been hacking my way through without any real structure for about 10 years, so it's way overdue. Bud -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
