Hello -
I am just getting started with creating a website that will be a membership-based website that will collect specific information on a member that will then be used in the creation of a back-end database.
The use case of the site is that a user becomes a member, inputs all of their specific professional credentials in our database and that database will then be used for “match making” to other businesses. Once a member signs up (which will involve collecting their data), chooses their membership level, I want them to be able to view and edit their profile.
I have started with the sign up form that Wix creates. This form appears to store data in the PrivateMembersData database. It appears I can’t do much with this data once a member signs up other than allow them to modify their Name, Phone, email and address via the edit Profile. So, I have created a collection per the suggestion of this article: https://support.wix.com/en/article/corvid-tutorial-building-your-own-members-area. What I can’t seem to figure out is how to link my new collection to the Private MembersData database. Perhaps I am thinking about this wrong, but it seems that the collection is essentially adding a table to a relational database with the PrivateMemberData table being the parent table.
Am I going about this the wrong way? Should I be scrapping the PrivateMemebrsData database and start everything from scratch (including the sign up page?
Any help/suggestions would be greatly appreciated.
Matt
Thank you so much for the reply. I will give this a shot and report back.
Thank you again. This worked great. And now I have a custom registration page and profile view/edit screen. One issue I am running into is the fact that my Member collection doesn’t link back to the data that is stored in the PrivateMembers dataset (where the email and password are stored). So, what I am running into is that Member1 is seeing Member2’s data in the collection when I click the view/update profile (the custom Dynamic form I created).
Is there a step that I missed to link these two databases together?
Thank you again for all the help!
@mattacollins
Since you use 2xDATABASES —> PMD and your own Member-DB, you always will have to update the information in your own DB when something changes in PMD.
That means, for example if a user do a registration, you have to save/update the new DATA in PMD and also in your own DB.
If a user changes his Profile-Pic you will also have to save it simultaniously in your own DB, so that your own Member-DB is always UPDATET ! ! !
@russian-dima
Thanks for the very quick response. Quick follow up…do I even need to use two databases? It seems I can write to the PMD, and I am OK not using it at all and just using my members database. Is that an option? Or do I have to use PDM for emails and passwords?
Thanks again!
Matt
@mattacollins
Yes you should better use the PDM for e-mail and passwords.
There you will have a E-mail-verification-option to verify your Email for example.
You will need the update of your own db only if something changes in PDM.
If nothing changes in PDM, then you can work just with your own DB.
You need the PDM for wix-system processes like…
-registration
-log-in
-e-mail verification
-User & owner-ID
-crm
and other to this PDM-DB connected wix-features and tools like (Wix-Shop-WixForum-WixForm and so on)
@russian-dima
Wow. That is a super helpful explanation. Thank you for taking the time to help me with this.
So, it sounds like I just need to use code to push the ID from PDM into my own database, so I have the same ID between the two databases. Is that how that is typically done?
Thanks again!
@russian-dima
I did some further digging into this and it seems that the “Owner” field on my custom collection links back to the ID field on the PDM. It seems like it would be easiest to filter my member-only pages by the ID/Owner combination. I can’t seem to figure out how to apply this filter since it will only let me filter by non-system fields. Maybe I am thinking about this all wrong (I am looking at it through the lens of a relational database where the PDM is the parent table and my collection is the child).