I'm trying to have a new go at integrating WSN Gallery into my existing member database. I used a customized integration script I created to link the members fields to similiar fields, but I have many fields that can't be linked to similiar fields (there were a total of 4 fields that transfered).
It seems like it might have worked but, I'm at a loss for many details:
1. I cannot figure out how or where VARIABLES get assigned their values. How do I assign my existing database memberfields to variables that I can then display in profile pages, etc.,? Also, where (in what files are these variables stored? I have searched the templates for MEMBERNAME and the like with no success.
2. I don't use MD5 encryption on my passwords (or any other encryption), how do I integrate the gallery on my membership database of over 4000 members and their existing user names and unencrypted passwords?
That should be enough for now. I appreciate any help you provide.
What fields are you talking about, and if they don't have equivilant fields then why would you want to integrate them with a native WSN Gallery field in the first place? Surely it'd be bad to integrate fields that don't serve the same purpose, you should want to keep their distinct functions.
As for displaying in profiles and the like, simply use the name of the field. If you have some field named nothingtodowithgalleries then you use {MEMBERNOTHINGTODOWITHGALLERIES} to display it.
Unencrypted passwords would be an encoder file (see the vbulletin one for example) which just contains
Thanks, that's what I was looking for. I have all these unique fields and I couldn't figure out how to call them into the templates. So, if I want to call my personal_description field, I would enter {PERSONAL_DESCRIPTION} in my templates without needing anything else?
One other question. Does it matter if the fields that I use an integration script for are structurally different? Say my name field is a VARCHAR 40 and the gallery name is text?
knotworking wrote: I would enter {PERSONAL_DESCRIPTION} in my templates without needing anything else?
No. You need to follow the same scheme as all other fields. The 'title' field for images is {IMAGETITLE}. The 'name' field for members is {MEMBERNAME}. The 'personal_description' field for members would therefore be {MEMBERPERSONAL_DESCRIPTION}.
Say my name field is a VARCHAR 40 and the gallery name is text?
It makes no different unless you're getting input to the field longer than 40 characters (which would be ignored).
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on Painful Integration
Experienced
Usergroup: Customer
Joined: Mar 31, 2004
Total Topics: 20
Total Comments: 83
I'm trying to have a new go at integrating WSN Gallery into my existing member database. I used a customized integration script I created to link the members fields to similiar fields, but I have many fields that can't be linked to similiar fields (there were a total of 4 fields that transfered).
It seems like it might have worked but, I'm at a loss for many details:
1. I cannot figure out how or where VARIABLES get assigned their values. How do I assign my existing database memberfields to variables that I can then display in profile pages, etc.,? Also, where (in what files are these variables stored? I have searched the templates for MEMBERNAME and the like with no success.
2. I don't use MD5 encryption on my passwords (or any other encryption), how do I integrate the gallery on my membership database of over 4000 members and their existing user names and unencrypted passwords?
That should be enough for now. I appreciate any help you provide.
Experienced
Usergroup: Customer
Joined: Mar 31, 2004
Total Topics: 20
Total Comments: 83
Is it that my question didn't make sense or, is the support forum on holiday?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
What fields are you talking about, and if they don't have equivilant fields then why would you want to integrate them with a native WSN Gallery field in the first place? Surely it'd be bad to integrate fields that don't serve the same purpose, you should want to keep their distinct functions.
As for displaying in profiles and the like, simply use the name of the field. If you have some field named nothingtodowithgalleries then you use {MEMBERNOTHINGTODOWITHGALLERIES} to display it.
Unencrypted passwords would be an encoder file (see the vbulletin one for example) which just contains
Experienced
Usergroup: Customer
Joined: Mar 31, 2004
Total Topics: 20
Total Comments: 83
Thanks, that's what I was looking for. I have all these unique fields and I couldn't figure out how to call them into the templates. So, if I want to call my personal_description field, I would enter {PERSONAL_DESCRIPTION} in my templates without needing anything else?
One other question. Does it matter if the fields that I use an integration script for are structurally different? Say my name field is a VARCHAR 40 and the gallery name is text?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
knotworking wrote:
I would enter {PERSONAL_DESCRIPTION} in my templates without needing anything else?
No. You need to follow the same scheme as all other fields. The 'title' field for images is {IMAGETITLE}. The 'name' field for members is {MEMBERNAME}. The 'personal_description' field for members would therefore be {MEMBERPERSONAL_DESCRIPTION}.
Say my name field is a VARCHAR 40 and the gallery name is text?
It makes no different unless you're getting input to the field longer than 40 characters (which would be ignored).