Views/Rendering Variable Issues? |
(10-11-2016, 09:35 PM)kilishan Wrote:(10-11-2016, 01:00 PM)enlivenapp Wrote: Thanks for your reply. Adding saveData into the options array does the trick... Possibly, but more secure data handling is usually a good idea. If there's a way to handle/pass the data to multiple views in a singe view/template call more securely, it might be best to prescribe that way... if not, someone would need to know (docs?) the need to pass saveData = true when building their template engine or calling view(). @sv3tli0 Quote:...some time to play around with it today for giggles. |
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
|