kumarsivarajan / mollify

Automatically exported from code.google.com/p/mollify
0 stars 0 forks source link

Error server response for admin user #484

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. to log in as admin error jumps
2.
3.

What is the expected output? What do you see instead?
to log the

What version of the product are you using? On what operating system?
2.1.6 - 2.1.9 - 2.2 On windows server 2008 with php 5.3 and apache 2.2.22 mysql 
5.5.24

Please provide any additional information below.

Original issue reported on code.google.com by r2gale...@gmail.com on 28 Oct 2013 at 4:23

Attachments:

GoogleCodeExporter commented 8 years ago
Could you get the PHP error log, as this pic alone does not tell much

Original comment by samuli.j...@gmail.com on 28 Oct 2013 at 4:46

GoogleCodeExporter commented 8 years ago
Also have to ask, you did run the updater?

Original comment by samuli.j...@gmail.com on 28 Oct 2013 at 4:58

GoogleCodeExporter commented 8 years ago
[Mon Oct 28 14:31:56 2013] [error] [client 192.168.0.101] MOLLIFY ERROR: 
ServiceException: INVALID_CONFIGURATION=Error executing query (SELECT id, name, 
lang, email FROM mollify_user WHERE name='rgfpy') AND (expiration is null or 
expiration > 20131028193156)): You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near ') AND (expiration is null or expiration > 20131028193156)' at line 1, 
referer: http://192.168.0.97/mollify/
[Mon Oct 28 14:31:56 2013] [error] [client 192.168.0.101] MOLLIFY ERROR: 
{0:{file:C:\\wamp\\www\\mollify\\backend\\include\\configuration\\ConfigurationD
ao.class.php, line:54, function:query, class:MySQLIDatabase, type:->, 
args:{0:SELECT id, name, lang, email FROM mollify_user WHERE name='rgfpy') AND 
(expiration is null or expiration > 20131028193156)}}, 
1:{file:C:\\wamp\\www\\mollify\\backend\\include\\Authentication.class.php, 
line:107, function:findUser, class:ConfigurationDao, type:->, args:{0:rgfpy, 
1:, 2:1382981516}}, 
2:{file:C:\\wamp\\www\\mollify\\backend\\include\\services\\SessionServices.clas
s.php, line:59, function:login, class:Authentication, type:->, args:{0:rgfpy, 
1:adminrtic}}, 
3:{file:C:\\wamp\\www\\mollify\\backend\\include\\services\\SessionServices.clas
s.php, line:51, function:authenticate, class:SessionServices, type:->, 
args:{}}, 
4:{file:C:\\wamp\\www\\mollify\\backend\\include\\services\\ServicesBase.class.p
hp, line:59, function:processPost, class:SessionServices, type:->, args:{}}, 
5:{file:C:\\wamp\\www\\mollify\\backend\\include\\MollifyBackend.class.php, 
line:82, function:processRequest, class:ServicesBase, type:->, args:{}}, 
6:{file:C:\\wamp\\www\\mollify\\backend\\r.php, line:63, 
function:processRequest, class:MollifyBackend, type:->, args:{0:Request}}}, 
referer: http://192.168.0.97/mollify/

Original comment by r2gale...@gmail.com on 28 Oct 2013 at 5:33

GoogleCodeExporter commented 8 years ago
apparently mysql syntax error

Original comment by r2gale...@gmail.com on 28 Oct 2013 at 5:34

GoogleCodeExporter commented 8 years ago
(SELECT id, name, lang, email FROM mollify_user WHERE name='rgfpy') AND 
(expiration is null or expiration > 20131028193156))

the closing parenthesis in this section that this is what I think is wrong: 
name='rgfpy') 

correct:
(SELECT id, name, lang, email FROM mollify_user WHERE name='rgfpy' AND 
(expiration is null or expiration > 20131028193156))

Original comment by r2gale...@gmail.com on 28 Oct 2013 at 5:43

GoogleCodeExporter commented 8 years ago
if so is I modified the file: 
backend/include/configuration/ConfigurationDao.class.php line 54: 
$ result = $ this-> db-> query (sprintf ("SELECT id, name, lang, email FROM". $ 
this -> db-> table ("user"). "WHERE (name = '% s')". $ expirationCriteria, $ 
this-> db-> string ($ username)));

after: "WHERE name = '% s')".
before: "WHERE (name = '% s')".

and you can now sign in with the user

Original comment by r2gale...@gmail.com on 28 Oct 2013 at 8:46

GoogleCodeExporter commented 8 years ago
Yes, I modified the user table and moved authentication info into new table, 
and the query was broken. I was testing with allow email option on, and did not 
see this. This is now fixed, releasing a new version.

Original comment by samuli.j...@gmail.com on 29 Oct 2013 at 5:25

GoogleCodeExporter commented 8 years ago
Fixed in 2.2.2

Original comment by samuli.j...@gmail.com on 29 Oct 2013 at 7:20

GoogleCodeExporter commented 8 years ago
thanks excellent work!

Original comment by r2gale...@gmail.com on 29 Oct 2013 at 1:26