A customer was reporting their funds had run out yet they hadn't.
1) I checked their account via edit profile. Funds are shown, but their membergroup "shows" they are a group 2 which is why they're being shown warning messages about adding more funds.
2) I change the usergroup to 8 which is what they're suppose to be. No change on client's member home. When I edit the profile again it STILL shows they're in group 2. Now I changed that IF tag on the edit profile that said IF not INTEGRATION because I need to edit/assign usergroups when I'm giving away promo packages. But I don't think that changed much, it just allowed me to see the usergroup field which is basically unchangeable.
3) Checked DB, which says they are in group 8 as they should be but the members home area is showing them code as if they were group 2.
So somewhere the forum members table is still being used when it should be using the links member's table?
If I don't get a response in 5 hours I have to delete the forum because I'm leaving for a trip and I can't have my site in this state while I'm traveling. Customers are finally surfing the site without my prodding.
Now all of a sudden my client is reporting that everything is fine. I may not have refreshed the page after but now I'm getting errors in the WSNLINKS admin overview page.
An error occoured at /admin/index.php?show=main on 2009-06-19 16:00:21. Please relay this data to support. Error #2: 'file_get_contents() [function.file-get-contents]: couldn't resolve host name' in /home/xxxx/public_html/xxxx/includes/filefunctions.php on line 513.
When you integrate, you have to map any custom usergroups in the host script onto usergroups in the integrating script. Any un-mapped groups are considered to be group 2, regular members. scripts.webmastersite.net/w...system_integration-75.html
Post #2: That says your server is unable to read my server. Possibly my server was down.
0/5
1
2
3
4
5
Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.
Comments on Cannot change usermembergroup
Forum Regular
Usergroup: Customer
Joined: Nov 25, 2003
Total Topics: 70
Total Comments: 211
WSNLINKS 5.0.52 with WSNFORUM 5.0.52
A customer was reporting their funds had run out yet they hadn't.
1) I checked their account via edit profile. Funds are shown, but their membergroup "shows" they are a group 2 which is why they're being shown warning messages about adding more funds.
2) I change the usergroup to 8 which is what they're suppose to be. No change on client's member home. When I edit the profile again it STILL shows they're in group 2. Now I changed that IF tag on the edit profile that said IF not INTEGRATION because I need to edit/assign usergroups when I'm giving away promo packages. But I don't think that changed much, it just allowed me to see the usergroup field which is basically unchangeable.
3) Checked DB, which says they are in group 8 as they should be but the members home area is showing them code as if they were group 2.
So somewhere the forum members table is still being used when it should be using the links member's table?
If I don't get a response in 5 hours I have to delete the forum because I'm leaving for a trip and I can't have my site in this state while I'm traveling. Customers are finally surfing the site without my prodding.
Thanks!
Forum Regular
Usergroup: Customer
Joined: Nov 25, 2003
Total Topics: 70
Total Comments: 211
Now all of a sudden my client is reporting that everything is fine. I may not have refreshed the page after but now I'm getting errors in the WSNLINKS admin overview page.
Are you in there taking a look?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
When you integrate, you have to map any custom usergroups in the host script onto usergroups in the integrating script. Any un-mapped groups are considered to be group 2, regular members. scripts.webmastersite.net/w...system_integration-75.html
Post #2: That says your server is unable to read my server. Possibly my server was down.