I am using WebloginPE on a new site that has not gone live yet.
I’m trying to allow users an option to edit their profile, but, for some reason, the form will not save data back to the extended attributes table.
The form will pull data from the extended attributes table and insert it into the form fields on the page, but, will not save changes to those fields.
My form field names all match those listed for the fields of the database.
Anything special I should be doing in the call to this snippet for profile editing? Is this a common problem?
Anyone?
Someone has to have dealt with this issue before. I’ve tested everything I can think of to debug the problem and cannot figure out why it won’t save extended attributes to the database from the profile editing page. I can get it to save from my registration form no problem. In addition, I went looking online for other sites using Modx and Webloginpe and, on at least one, I was able to edit my profile and submit extended attribute data to the database (I know it saved because the information was present on the profile editing page when I reloaded it). So, I know it CAN be done. I just couldn’t see any difference between the source on that site and my own.
So, if there is someone out there who might be able to help me troubleshoot this, I’m willing to pay for the trouble. I NEED this to be completed for a business site that needs to go live very soon. Without this completed, I cannot go live.
Please. If anyone thinks they have any information that will help, let me know.
Thank you for your reply.
I was running the snippet cached (unintentionally), but calling it from an UNcached page.
I tried switching the snippet call to UNcached, but then, all I see is the snippet call.
As far as the input handler, I wasn’t aware that I needed it. I did read about it in the documentation (been through ALL of the documentation numerous times), but, it seemed that it was only necessary in certain instances, none of which seemed to fit my situation. maybe I don’t fully understand how the inputhandler works and when it’s needed.
To be honest, although I was able to get pretty far with the documentation that is available, I find it to be too focused on just the nuts and bolts with really no "birds eye view" walkthrough of how it all fits together. It makes it tough to weed through it.
I’m pulling my hair out on this profile page. Do I want to call the snippet UNcached? If so, how can I do it, since currently it’s just loading the snippet CALL instead of actually running the snippet code.
The page calls the WebLoginPE snippet which uses a chunk template, which calls the snippet in question.
Thanks so much for your assistance.
If you’re seeing the actual call, the original way you did it is right. There’s a known issue with the page/snippet cache settings in the Evolution (what you’re using) version. IIRC, that’s being fixed for Revolution (the next version of MODx currently in development).
&inputHandler is used for anything that well...needs input. Select, checkboxes, and radios use it, IIRC. Just to check, you added your custom fields under &customFields, right?
I’m using &customfields on the initial registration form, but was not using it in the call to the profile editing page. Do I need to use this there too?
Thank you so much for your assistance. That does seem to have solved the problem. I’ll let you know if I have any more issues (I’m sure you’re thrilled).
Thanks again.
