promote function problem

New Member Joined: Dec 19, 2004 Posts: 5

I am useing [CNB Your Account 4.4.1] and when i try to promote a user it says

ERROR: There was a problem with the database.

i even tried cnbya 4.4.2 with same error, if someone could tell me how to fix this i would appreciate it thanks.

Posted: Sat Jun 04, 2005 8:35 pm

Without a bit more description as to the error, that could be tricky. . .

Might try searching the forums for tips on how to get more detail out of your errors, then once you have some more info we can go from there. I would search for phpinfo or sql abstraction layer in the forums - nukecops used to have a sticky written by chatserv on how to do this I think.

-sting

Worker Joined: Nov 10, 2004 Posts: 110

Very helpfull would be if you could specify you phpnuke version number and (if you have any) the ammount of the extra fields in your nuke_authors table.

Cheers,
Richard

Posted: Wed Jun 08, 2005 10:57 pm

how do i lookup the fields in nuke_authors table and im useing nuke ver 7.6

Posted: Thu Jun 09, 2005 8:47 am

Use phpmyadmin, or whatever database utility you have to manage the site.

Usually found through your ISP administration utility (Cpanel, Vdeck, etc, etc)

-sting

Posted: Thu Jun 09, 2005 10:38 am

aid varchar(25) No
name varchar(50) Yes NULL
url varchar(255) No
email varchar(255) No
pwd varchar(40) Yes NULL
counter int(11) No 0
radminsuper tinyint(1) No 1
admlanguage varchar(30) No
radminblocker tinyint(2) No 0
Check All / Uncheck All With selected:

Hangin' Around Joined: Jun 25, 2005 Posts: 30

I am getting the same error. My authors table is same as above. Any ideas?

Posted: Thu Sep 01, 2005 10:07 pm

Check into the validity of radminblocker - I think I have run into this before on occasion, where the Insert statement in the code did not match up with the number of fields in the database. More than likely you could either add an additional zero value to be put into the radminblocker field or (gasp) delete the radminblocker field altogether, of course making a backup copy of the database BEFORE you do it...

Good luck - keep in mind I don't think we have seen the original error as of yet, so troubleshooting this is sort of like flying blind...

-sting