You don’t. In Magento’s MVC approach, it’s not the responsibility of the controller to set variables for the view (in Magento’s case, the view is Layout and blocks). Controllers set values on Models, and then Blocks read from those same models. In Magento’s view of the world, having a Block relying on the controller doing … Read more
ViewData/ViewBag – valid only for the duration of the current request. You set it in a controller action and use it in the view, then it disappears. The difference is that the first is a dictionary whereas the second is just a dynamic wrapper around this dictionary. Both point to the same data though. ViewBag … Read more
The correct syntax for this is: Session::set(‘variableName’, $value); For Laravel 5.4 and later, the correct method to use is put: Session::put(‘variableName’, $value); To get the variable, you would use: Session::get(‘variableName’); If you need to set it once, I’d figure out when exactly you want it set and use Events to do it. For example, if … Read more
Got it. Quite stupid, actually. It worked after I removed & added the SessionStateModule like so: <configuration> … <system.webServer> … <modules> <remove name=”Session” /> <add name=”Session” type=”System.Web.SessionState.SessionStateModule”/> … </modules> </system.webServer> </configuration> Simply adding it won’t work since “Session” should have already been defined in the machine.config. Now, I wonder if that is the usual thing … Read more
As @Thariama said, there’s no limit on the number of variables; also, there’s no limit on the amount of data you can store in a session (I’ve seen sessions tens of MB in size). As the size of a session gets larger, you’ll run into various quirks though: PHP 5 deserializes the whole session into … Read more
You will never get unanimous opinion on anything in any large group of people. That’s just human nature. Part of that stems from the Dunning-Kruger Effect which states that the less someone knows about a subject, the more likely they are to over value their expertise in that subject. In other words, lots of people … Read more
Is there a difference? There is. Session.Remove(key) deletes the entry (both key & value) from the dictionary while Session[key] = null assigns a value (which happens to be null) to a key. After the former call, the key won’t appear in the Session#Keys collection. But after the latter, the key can still be found in … Read more
Sessions are stored on the server, which means clients do not have access to the information you store about them. Session data, being stored on your server, does not need to be transmitted in full with each page; clients just need to send an ID and the data is loaded from the server. On the … Read more
Another option would be modifying web.xml. Prior you must call grails install-templates Then edit src/templates/war/web.xml and add/modify after servlet-mapping: <session-config> <session-timeout>60</session-timeout> </session-config> The value of session-timeout uses minutes as unit.
HttpContext.Current.Session[“…”] HttpContext.Current gets you the current … well, Http Context; from which you can access: Session, Request, Response etc