Frontend Users not expiring

[jmcgin51]

Running 1.0.2 "Maui", with FEU 1.1.1, and I just realized that users aren't expiring when their expiration date is reached.  I have three users that should have expired on October 31st, 2006, but I can still log in today (December 2, 2006) using their username and password.

Any ideas?  Calguy?

Thanks

EDIT: I've read that there are some Smarty caching issues with FEU.  Could this be part of the problem?  What files do I need to edit to resolve this?  Are there any drawbacks associated with turning off Smarty caching?

[jmcgin51]

bump

[jmcgin51]

more information...

No matter what expiration date I assign to a user, when I view the list of users, the dates are all correct, but the times are all 00:00:00.

The users do not expire.  Why isn't FEU saving the time correctly?

[jmcgin51]

Darn, Calguy - I saw you were on this morning responding to a bunch of other posts, and I hoped you'd be able to respond to this one...  Any ideas?  I have a site that is ready to launch, but I need this issue fixed first.

Thanks!

[calguy1000]

I think that this has been fixed in SVN.  there'sa a bunch of posts about some missed changes to DBTimeStamp. 

See this link, it describes exactly where the fixes were for this:

http://viewsvn.cmsmadesimple.org/viewsv ... 1=97&r2=98

[jmcgin51]

Calguy,

Thanks for the link, but it didn't help.  I made all the changes in the SVN notes, along with the "trim" changes posted by Roland in another thread, and there's no difference in performance.  I cleared the cache and still no luck.

I've tried on both Win2003 IIS 6 and WinXP running XAMPP, with identical performance on both, so I don't think it's IIS-related.  I know it used to work under CMS .13 and the last .13-compatible version of FEU, whatever that was.

I'm using ADODB LITE.

Thanks for your help!

[jmcgin51]

Calguy, is there any additional information I can provide you with that might help determine the cause of this problem?  At this point I'm a bit discouraged, because I've spent countless hours developing the site, and it worked fine under .13, and now I have a site that I really can't use, because I need to restrict access to certain users and groups.  Without the ability to expire users, I'm going to have to look for a different solution, which really bums me out because I've really grown to like CMSMS.

What I don't understand is that the expire date is listed correctly.  It's only the time that is 00:00:00.

Thanks in advance...

[calguy1000]

well, check your database fields in cms_module_feusers_* tables, and make sure that all of the appropriate fields are of type DATETIME instead of DATE or TIME.  that's probably what's causing it.  if you've applied the fixes to dbtimestamp.  I can't reproduce it here myself.

[jmcgin51]

createdate is datetime
expires is datetime

When I browse the database in phpMyAdmin, the createdate is listed correctly, but the expires date is not.  For some reason, the date is not being written correctly to the database...

bummer.

[jmcgin51]

Calguy, what do these two lines in the FEU api file do, and what is the difference between the original code (on the left) and Roland's fix (on the right)?

$db->DbTimeStamp(time()),          $db->DbTimeStamp(time()."'"),
$db->DbTimeStamp($expires) ) );    $db->DbTimeStamp($expires,"'") ) );

[calguy1000]

the fix put's quotes around the database timestamp before giving it to adodb lite.  it's a change that had to be done when we went to adodb-lite, and I missed a couple of em.

[jmcgin51]

right, sorry, I meant to ask what the functional difference is, but you answered it.  Basically the function is the same; the quotes are just a requirement for ADODB LITE.

So is the data not being sent to ADODB LITE correctly, or is ADODB LITE receiving good data and is not writing it correctly to the database?  Is there any way to tell?

[jmcgin51]

update:

If I go into the database and manually add the expiration time, the expiration time then shows up in the FEU Users page (until I edit that user, after which I have to do a manual database edit again), but the expires time doesn't "do" anything.  In other words, I can set the expiration time in the database to be October 1, 2006 at 17:00:00, but if I try to log in using that userid, it still lets me in, even though the user should be expired...

I would be open to trying a non-Windows server, but since I'm already running one instance of this on XAMPP and it's performing the same, I'm doubtful that a non-Windows server is necessarily the answer.

Does my host's server configuration matter for this module to function correctly?

Thanks...

[jmcgin51]

more issues:

Calguy, when I try to edit the user's profile (in the front-end "Edit My Settings" page), if I just try to change my password, it returns an error that the email address is already used...  I searched the forum and found an earlier thread of mine where I had the same problem running an earlier version of FEU.  Your reply was that the latest (1.1) worked ok and fixed this issue.

haven't tested this on the XAMPP install yet, but I'm becoming more and more discouraged by FEU.  It sounds like it works for many users, but doesn't work everywhere that CMSMS works...

[mahjong]

I have the same issues.

• Users can log in after their expiring date is passed.
• Hour, minutes and seconds always revert to 00:00:00 when setting the expiring date