CMS Made Simple Forums

I am using frontend users version 1.0.0 and have about 60 users.  I am able to edit usernames, but when I try to edit the expiration date, it will not change.  Anyone out there run into this and have a solution?

I am using CMS version 0.12.1 "Savusavu"

Any help would be greatly appreciated!

I had problems with the expirationdate too. But my problem was that the expoiration-date was reset to null everytime a user changed his/her settings and so was no longer able to login to the system.
Robert checked for errors but he didn't find any.

I'll check the expiration date stuff on the admin side again, but the latest svn version has this fixed for users modifying their own details.

I just haven't cut a release yet, due to problems with the export stuff.

Calguy,

I'm not giving the user the ablity to modify the expiration date from the front.  Only admin can from the backend.

Any solutions?

Thanks as always!

tussin wrote: Calguy,

I'm not giving the user the ablity to modify the expiration date from the front.  Only admin can from the backend.

Any solutions?

he said he is looking into it:

I'll check the expiration date stuff on the admin side again

... thanks for the UPDATE petert

In the latest svn code all worked well, so I must have already fixed it

Hi Calguy,

I've updated to the latest snapshot and still I cannot modify the expiration date.  It always defaults back to 2016.

Any other suggestions?

I'm having trouble with this as well.  I created a user to expire in 10 years.  Then, I decided to change it to 20 years.  When I hit "submit" it reverted back...to today...and the user was expired and I could not change it from today.

Any ideas?

make sure you have the latest and greatest svn.  I recently made a change for this.

I've given a try to the latest SVN and the expiration date problem is still present.

I'm also still getting this even with the new version.  It works fine - I can set expiration dates and everything (unless I set it to Dec. 31 2040, which resets it to 0/0/0000.  And when a user tries to change their settings, it sets their expiration date to 0/0/0000.

Actually, it seems to set it to that date (which actually appears to be Nov. 30, 2000) when you try to set it to any date after 2035.

This is bad.  I really, really need people to be able to change their own passwords.

what happens when you set the expiry date to any date that's reasonable, say Jan 1, 2010  ?

That works.  I can set it to 2035 even.  It's no problem from the admin side.

However, when a user changes his/her settings (to change password and/or other properties) it sets their expiration date to 0000-00-00 00:00:00.

I'm using 0.13 beta 2 and the latest versions of FEU and CC.

EDIT: Further information:

It's only when changing passwords that it changes the expiration date - however, the password change goes through successfully.  If you change any custom properties, it doesn't revert the expiration date.

Okay, tested yet again (feusers latest svn, which is valid with 0.14-svn only).

Yes, the year 2040 seems to be a problem,  I'll look into this.

However.

I created a user in the admin, using default values for the expiry date
Then changed the users password in the admin, and set his expiry to June 1, 2036.  This worked fine.

Then I logged in to the frontend as that user, and went to change settings.
I set the password, and hit submit.

Going back into the admin section and hitting reload showed exactly the same expiry date.