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
Some useful 'protected' methods (like frontendController->loadObj) are declared in controllers, not available from components. How to use them?
A. make them 'public' in controllers, and let them be 'tokens', not available if called directly through urls.
B. create a public wrapper for these methods, then let it be a 'token', not available if called directly through urls.
Both A and B allow components to call specified methods (calls like: $this->Controller->loadObj ...).
The text was updated successfully, but these errors were encountered:
From a design perpsective calling controller methods from components is not a good thing.
Maybe that logic should reside in models or elsewhere.
At this point we need to handle however situations where public methods may not be called from urls, so I would go with solution A. @batopa what do you think?
Commit above for solution A. Frontend methods involved: "loadObj","loadObjByNick","loadSectionObjects","loadSectionObjectsByNick","objectRelationArray".
Some useful 'protected' methods (like frontendController->loadObj) are declared in controllers, not available from components. How to use them?
A. make them 'public' in controllers, and let them be 'tokens', not available if called directly through urls.
B. create a public wrapper for these methods, then let it be a 'token', not available if called directly through urls.
Both A and B allow components to call specified methods (calls like: $this->Controller->loadObj ...).
The text was updated successfully, but these errors were encountered: