Blog Sections Open
Prefilling eForm Fields with Logged-In User Data
When a logged-in customer opens an order form, you can prefill the form from their profile instead of making them type the same data again.
Evolution CMS stores enough user data to make forms friendlier for authenticated visitors. In shop and account flows, the usual goal is to prefill eForm fields with profile data so repeat users do not need to retype everything on every request.
Classic PHx-style pattern
[*phx:input=`&_PHX_INTERNAL_&`:userinfo=`fullname`*]
That was a common approach in older Shopkeeper and Personalize flows.
Modern recommendation
Whether you use PHx or a lighter helper, keep the prefill logic explicit and tied to authenticated user data only. That makes order forms more convenient without turning the form layer into parser spaghetti.
Running Heavy Snippets Through AJAX in Evolution CMS
If a snippet is slowing down page rendering, moving it behind an AJAX request can improve perceived speed without changing the snippet’s core logic.
Building Nested Menus with Wayfinder
Wayfinder can build multilevel menus cleanly, but only if you prepare the template chunks for nested output instead of treating every item as flat markup.