Joined: Apr 06, 2006 Posts: 2415 Location: Iowa, USA
Posted:
Sat Jul 07, 2007 9:48 pm
Dump the structure of your users table with phpMyAdmin and post it here....or compare it to the one in RN 2.10.1 just to make sure they aren't different.
I am actually having the same problem. The only difference between my tables and the installation tables is that I added Approve Membership to the bunch. All the rest of the users tables are exact.
I had approve membership installed first time round, but it only caused more problems with RN then when i originally used it phpNUKE 7.9, that is why I took it out and made sure that nuke_user table was identical between what i have and RN.
Make sure you don't have SQL error of having primary and index keys the same, I know i did and when i dropped one (the one that wasn't registered with RN) my 2nd key, everything worked fine after that.
I cannot remove AM at all. This site I am making is for a group and I cannot have outsiders in the members areas. I'll take a closer look at the tables.
Here's the SQL Table:
Code:
CREATE TABLE `nuke_users` (
`user_id` int(11) NOT NULL auto_increment,
`name` varchar(60) NOT NULL default '',
`username` varchar(25) NOT NULL default '',
`user_email` varchar(255) NOT NULL default '',
`femail` varchar(255) NOT NULL default '',
`user_website` varchar(255) NOT NULL default '',
`user_avatar` varchar(255) NOT NULL default '',
`user_regdate` varchar(20) NOT NULL default '',
`user_icq` varchar(15) default NULL,
`user_occ` varchar(100) default NULL,
`user_from` varchar(100) default NULL,
`user_interests` varchar(150) NOT NULL default '',
`user_sig` varchar(255) default NULL,
`user_viewemail` tinyint(2) default NULL,
`user_theme` int(3) default NULL,
`user_aim` varchar(18) default NULL,
`user_yim` varchar(25) default NULL,
`user_msnm` varchar(25) default NULL,
`user_password` varchar(40) NOT NULL default '',
`storynum` tinyint(4) NOT NULL default '10',
`umode` varchar(10) NOT NULL default '',
`uorder` tinyint(1) NOT NULL default '0',
`thold` tinyint(1) NOT NULL default '0',
`noscore` tinyint(1) NOT NULL default '0',
`bio` tinytext,
`ublockon` tinyint(1) NOT NULL default '0',
`ublock` tinytext,
`theme` varchar(255) NOT NULL default '',
`commentmax` int(11) NOT NULL default '4096',
`counter` int(11) NOT NULL default '0',
`newsletter` int(1) NOT NULL default '0',
`user_posts` int(10) NOT NULL default '0',
`user_attachsig` int(2) NOT NULL default '0',
`user_rank` int(10) NOT NULL default '0',
`user_level` int(10) NOT NULL default '1',
`broadcast` tinyint(1) NOT NULL default '1',
`popmeson` tinyint(1) NOT NULL default '0',
`user_active` tinyint(1) default '1',
`user_session_time` int(11) NOT NULL default '0',
`user_session_page` smallint(5) NOT NULL default '0',
`user_lastvisit` int(11) NOT NULL default '0',
`user_timezone` tinyint(4) NOT NULL default '10',
`user_style` tinyint(4) default NULL,
`user_lang` varchar(255) NOT NULL default 'english',
`user_dateformat` varchar(14) NOT NULL default 'D M d, Y g:i a',
`user_new_privmsg` smallint(5) unsigned NOT NULL default '0',
`user_unread_privmsg` smallint(5) unsigned NOT NULL default '0',
`user_last_privmsg` int(11) NOT NULL default '0',
`user_emailtime` int(11) default NULL,
`user_allowhtml` tinyint(1) default '1',
`user_allowbbcode` tinyint(1) default '1',
`user_allowsmile` tinyint(1) default '1',
`user_allowavatar` tinyint(1) NOT NULL default '1',
`user_allow_pm` tinyint(1) NOT NULL default '1',
`user_allow_viewonline` tinyint(1) NOT NULL default '1',
`user_notify` tinyint(1) NOT NULL default '0',
`user_notify_pm` tinyint(1) NOT NULL default '0',
`user_popup_pm` tinyint(1) NOT NULL default '0',
`user_avatar_type` tinyint(4) NOT NULL default '3',
`user_sig_bbcode_uid` varchar(10) default NULL,
`user_actkey` varchar(32) default NULL,
`user_newpasswd` varchar(32) default NULL,
`points` int(10) default '0',
`last_ip` varchar(15) NOT NULL default '0',
`user_login_tries` smallint(5) unsigned NOT NULL default '0',
`user_last_login_try` int(11) NOT NULL default '0',
`custom1` varchar(255) default NULL,
`custom2` varchar(255) default NULL,
`custom3` varchar(255) default NULL,
`custom4` varchar(255) default NULL,
`custom5` varchar(255) default NULL,
`custom6` varchar(255) default NULL,
`custom7` varchar(255) default NULL,
`custom8` varchar(255) default NULL,
`custom9` varchar(255) default NULL,
`custom10` varchar(255) default NULL,
`custom11` varchar(255) default NULL,
`custom12` varchar(255) default NULL,
`custom13` varchar(255) default NULL,
`custom14` varchar(255) default NULL,
`custom15` varchar(255) default NULL,
`custom16` varchar(255) default NULL,
`custom17` varchar(255) default NULL,
`custom18` varchar(255) default NULL,
`custom19` varchar(255) default NULL,
`custom20` varchar(255) default NULL,
`custom21` varchar(255) default NULL,
`custom22` varchar(255) default NULL,
`custom23` varchar(255) default NULL,
`custom24` varchar(255) default NULL,
`user_show_custom1` tinyint(2) NOT NULL default '1',
`user_show_custom2` tinyint(2) NOT NULL default '1',
`user_show_custom3` tinyint(2) NOT NULL default '1',
`user_show_custom4` tinyint(2) NOT NULL default '1',
`user_show_custom5` tinyint(2) NOT NULL default '1',
`user_show_custom6` tinyint(2) NOT NULL default '1',
`user_show_custom7` tinyint(2) NOT NULL default '1',
`user_show_custom8` tinyint(2) NOT NULL default '1',
`user_show_custom9` tinyint(2) NOT NULL default '1',
`user_show_custom10` tinyint(2) NOT NULL default '1',
`user_show_custom11` tinyint(2) NOT NULL default '1',
`user_show_custom12` tinyint(2) NOT NULL default '1',
`user_show_custom13` tinyint(2) NOT NULL default '1',
`user_show_custom14` tinyint(2) NOT NULL default '1',
`user_show_custom15` tinyint(2) NOT NULL default '1',
`user_show_custom16` tinyint(2) NOT NULL default '1',
`user_show_custom17` tinyint(2) NOT NULL default '1',
`user_show_custom18` tinyint(2) NOT NULL default '1',
`user_show_custom19` tinyint(2) NOT NULL default '1',
`user_show_custom20` tinyint(2) NOT NULL default '1',
`user_show_custom21` tinyint(2) NOT NULL default '1',
`user_show_custom22` tinyint(2) NOT NULL default '1',
`user_show_custom23` tinyint(2) NOT NULL default '1',
`user_show_custom24` tinyint(2) NOT NULL default '1',
PRIMARY KEY (`user_id`),
KEY `uname` (`username`),
KEY `user_session_time` (`user_session_time`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;
hmm, why not just use group memberships or subscribers to enter that particular zone, rather then selecting who can be registered and who can't, i did something similar at one point where even if people registered they couldn't see anything as it was for specific group that i had to manually add them to it.
as for your tables, you only need 3, primary, uname and user_session_time, all others are added by different mods you may have applied, i deleted everything else from it and viola. AM never worked after that but i didn't care..
Hmmmmm.... Well I am not using RN on my other site and am using the AM Full Version. I really wish there was a full AM for Raven but it's not ready yet. I need to use the information from the extra profile info when they register (the new stuff you can add with AM full).
I really do not want to mess with Non-Members of my club with User accounts with my website. If I have to, I'll edit the profile link to the "Your Account" section for nuke but the problem there is people cannot have images in their signatures if I do that.
unfortunately I can't help you there, as it seems your problem is different to the problem i had. Although, before i sorted the table in my sql, I uploaded a new file for registration, that cleared first problem, but i got a different error with sql in a different file again. I uploaded that file a fresh and cleared up my table at the same time and it all worked after that. So i cannot really say where my exact problem was but those 3 things fixed it in the end.
Joined: Aug 29, 2004 Posts: 9136 Location: Arizona
Posted:
Wed Jul 11, 2007 6:52 am
boham, if you do not need to have all the extra fields and only need to approval piece, I have what I call "Approve Membership Lite for RavenNuke" in my downloads. It requires NO database changes to the core RavenNuke tables.
montego, It is AM lite that I am using but now that you say that, I really do not know how the customs from the full version got dumped into my user tables. But in all honestly, the extra fields would make my job for this site ALOT easier!
shane, what exactly did you replace to get yours working?
hmm, I can't really remember per se, but try this, when you get the error reporting for the sql table like i did, first time it said there was an error on line whatewer in File: usercp_register.php, so i replaced that file.
When I went to update the the profile again to see if that solved the problem i received the same sql error statement but this time error was caused from a different file and i can't remember which one it was.. so i changed that file too.
Basically, keep looking at the bottom of the error message and it will tell you which files are causing error and change that file name, put a fresh one in and see what else is causing error. However, like I said, my AM never worked after that, but it didn't bother me. Maybe once you have sorted all that out you could try reinstalling AM and see if it really is something to do with AM, as i also had problems with lstAdmin, which I also removed from my site.
lol, I got it shane. I basically threw the installation files for RN back to the site and under the SQL install, I removed all tables but the users table. I ran the install script and the darn thing works again. jeez, I don't know what I initially did but at least it's fixed. Thanks bro for your help.
yeah i think in the end that solved my problem, when i dumped and reinstalled the RN user table, but like i said, i did so many different things to solve it it was hard to establish what actually ended up making it work
Joined: Aug 29, 2004 Posts: 9136 Location: Arizona
Posted:
Wed Jul 11, 2007 8:52 pm
Yes, do NOT confuse "AM Lite" with the full version because the full version is what adds all the custom fields to nuke_users table and nuke_users_temp.
I am having a similar issue with rn2.10.01. I do have cnbya 442 fixed by fade2glory to use captcha installed. I have the same setup on a site running rn2.10.00 without this issue. I have turned on debugging but am not smart enough to find where the errors are output.
The members can update their profile from the forum/profile link but not their account update info link.
Joined: Aug 30, 2005 Posts: 3186 Location: near Albany NY
Posted:
Fri Oct 12, 2007 5:50 pm
If you modify the base RN tables in any way, thru CNBYA or AM or anything else, you are asking for trouble. And, as I have mentioned in another thread, the Nuke code (either RN or base Nuke for that matter) does nothing about reporting SQL errors. They just blithely lie there in the background, mostly being "caught" and then ignored by the mysql.php file in the /db directory. As far as I know, none of the means of turning on error reporting that we make available in RN2.10 or that has been available in any previous version of RN or Nuke itself will do a darned thing to help you. Hopefully this is going to change when we put RN2.20 out and admins will have the option to capture SQL errors. Even there it is only going to point you to where the problem is, not fix it.
I understand that part. What I am wondering, what changed from rn 2.10.00 t rn2.10.01. Did the db change any? Would I be able to downgrade from 2.10.01 to 2.10.00?
Joined: Aug 30, 2005 Posts: 3186 Location: near Albany NY
Posted:
Fri Oct 12, 2007 7:29 pm
I don't have time to check for absolute sure, but I am almost positive that there were no changes from 2.10 to 2.10.01 that would be causing this. There is probably a readme file with the 2.10.01 that details the changes.
Joined: Aug 29, 2004 Posts: 9136 Location: Arizona
Posted:
Sat Oct 13, 2007 8:04 am
kevinkap, there were no structural changes between 2.10.00 and 2.10.01. You may need to dump the structure of each and run a compare against them to see what might be different.
Or, its possible you have not fully implemented CNBYA the same in each.
Never mind, I now see that you have another thread and have figured this out.
Was this for me montego? If so, the group issue I did get resolved but not the updating profile issue. I am sure it is in the cnbya mod that I am using that fade2gray has worked on and fixed several things along with correct functioning of the captcha system. I will I had given up a while back but thought someone may have had the same type issue.
Joined: Aug 29, 2004 Posts: 9136 Location: Arizona
Posted:
Mon Oct 15, 2007 5:15 am
kevinkap, you might want to take a look at the profile update code in RavenNuke(tm) core (i.e., NOT CNBYA) and compare it with your CNBYA code. We had tweaked the RN Your Account module code awhile back to fix this.
View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum