You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allowed for actions to be called from within an action in a controller's code. Perfect for our purposes.
However, after successfully calling and executing the action, the framework somehow proceeds to call the default routed action as well, in the background. I know it's the default, catch-all action, since I changed that value in the app.js a couple of times in my tests prior to this post. Each time, the correct action would be called, then followed up by the default action.
That default action call goes on in the background somehow, not replacing the contents of the screen. An alert snuck away in the default action's code does get shown however.
For now I'm just making the default action something harmless, but of course this is no solution.
Any idea on where the routing might go wrong? My understanding of mvc.js is insufficient to go digging in it myself.
I'd be happy to offer you more information or do some more testing though. Let me know what to do.
The text was updated successfully, but these errors were encountered:
Hi John,
Last week you posted an updated mvc.js, based on our discussion at
http://johnkalberer.com/2011/09/13/appcelerator-mvc-routing/#comment-69
This allowed for actions to be called from within an action in a controller's code. Perfect for our purposes.
However, after successfully calling and executing the action, the framework somehow proceeds to call the default routed action as well, in the background. I know it's the default, catch-all action, since I changed that value in the app.js a couple of times in my tests prior to this post. Each time, the correct action would be called, then followed up by the default action.
That default action call goes on in the background somehow, not replacing the contents of the screen. An alert snuck away in the default action's code does get shown however.
For now I'm just making the default action something harmless, but of course this is no solution.
Any idea on where the routing might go wrong? My understanding of mvc.js is insufficient to go digging in it myself.
I'd be happy to offer you more information or do some more testing though. Let me know what to do.
The text was updated successfully, but these errors were encountered: