Views/Rendering Variable Issues? |
(10-11-2016, 12:44 PM)kilishan Wrote: We opted to be a little more secure in the handling of data this time around and to NOT save data between different view() calls by default, but require it to be explicitly passed. This is a change from previous versions. You should be able to pass [b]saveData[\b] through with a value of [b]true[\b] in the options array to have it work like it did previously, though. Thanks for your reply. Adding saveData into the options array does the trick... not sure I want to always override default behavior though... I may ponder on it a while... I may end up writing/using a template engine yet... Thanks again! |
Messages In This Thread |
Views/Rendering Variable Issues? - by enlivenapp - 10-11-2016, 11:18 AM
RE: Views/Rendering Variable Issues? - by kilishan - 10-11-2016, 12:44 PM
RE: Views/Rendering Variable Issues? - by enlivenapp - 10-11-2016, 01:00 PM
RE: Views/Rendering Variable Issues? - by kilishan - 10-11-2016, 09:35 PM
RE: Views/Rendering Variable Issues? - by enlivenapp - 10-12-2016, 08:53 AM
RE: Views/Rendering Variable Issues? - by cartalot - 10-12-2016, 12:55 PM
RE: Views/Rendering Variable Issues? - by enlivenapp - 10-12-2016, 01:11 PM
RE: Views/Rendering Variable Issues? - by cartalot - 10-12-2016, 03:28 PM
RE: Views/Rendering Variable Issues? - by sv3tli0 - 10-11-2016, 11:09 PM
|