Unanswered: Destroy View, Controller Errors Because the View is Gone. (MVC)
I'm assuming I'm not adhering to the best practice here. Here's my scenario:
I have a container view, which contains a few views concerning login (login, forgot password, support, etc...).
Upon successful login, I destroy this container view to conserve resouces.
The trouble I'm getting is that the controller for these views still exist. The controller is throwing an error because (obviously), it can't find the view in the application.
What's the best practice here?
Tags for this Thread