Blog Sections Open
Letting WebLoginPE Users Save Project Data in Their Account
User dashboards become much more useful when the account stores structured project data instead of only profile fields.
This donor described a common progression for account areas in Evolution CMS: WebLoginPE already handled authentication, but the project needed users to create and save their own records inside the account area.
What Changes When You Add Project Data
- The account becomes an application workflow, not just a login form.
- Structured fields need validation and persistence rules.
- Data must reappear correctly after the next login, not only after the first save.
Recommended Direction
Keep authentication separate from domain data. Let WebLoginPE manage the user session, then attach a clean storage model for the project records the account needs to create or edit.
That separation keeps the login system stable and prevents the account area from turning into an unmaintainable mix of profile code and project-specific business logic.
Resolving AjaxSubmit and jQuery UI Datepicker Conflicts
How to restore datepicker behavior after AjaxSubmit validation rewrites part of the booking form DOM.
Writing Calculated Values into a TV from Another Table
A practical workflow for calculating a value from a separate table and storing it in a TV field for sorting or manager visibility.