XFileSharing Pro - Social Mod Facebook

Message
Author
longsack
Posts: 24
Joined: Feb 04, 2014 3:07 am

Social Mod Facebook

#1 Postby longsack » Jan 30, 2015 11:12 pm

Probably a server error of some nature... When I use the FB social mod to log in I get the following error:

Software error:

Can't exec:
Column 'usr_login' cannot be null at Modules/DataBase.pm line 55.

Thoughts?

longsack
Posts: 24
Joined: Feb 04, 2014 3:07 am

#2 Postby longsack » Feb 02, 2015 6:32 pm

Nothing? :(

AnotherIdiot
Posts: 101
Joined: Aug 23, 2014 2:59 pm

#3 Postby AnotherIdiot » Feb 03, 2015 9:49 pm

This is the second post you have made about the Database.pm and "null".

Have you looked at the pm file? Have you tried rebuilding your mysql database? Do you have the right permissions to be manipulating the database?

longsack
Posts: 24
Joined: Feb 04, 2014 3:07 am

#4 Postby longsack » Feb 10, 2015 6:23 am

AnotherIdiot wrote:This is the second post you have made about the Database.pm and "null".

Have you looked at the pm file? Have you tried rebuilding your mysql database? Do you have the right permissions to be manipulating the database?
Oh my gosh, my second one! Stop the press and put the world on hold while I'm being flogged. I searched every post I have made, please point me in the direction of that 1st post so others kind find it, cause I cant...others may need the answer in the future.

I fixed this issue btw.

AnotherIdiot
Posts: 101
Joined: Aug 23, 2014 2:59 pm

#5 Postby AnotherIdiot » Feb 10, 2015 12:21 pm

You seem to have gotten the wrong end of the stick. I was simply saying that for 2 posts that were about the same thing there may be a conflict somewhere.

Here is where you wrote the last post:

http://sibsoft.net/forum/error-while-tr ... t5640.html

OP wrote:
rawrkee wrote:Hi,

while trying to delete users who have not been logged in within the past XX days, I get this Software error:

Can't exec:
Column 'usr_id' cannot be null at Modules/DataBase.pm line 55.

what can I do to resolve this issue? Thanks!
and you wrote:
longsack wrote:no fix for this? I have the same issue.
So you see, two problems on the same database line. A usr_id problem and a usr_login problem.