XF 1.5 Can not change year of birthday in acp older than 1970 (i.e.1969)
- Thread starter snoopy5
- Start date
If you are using XenForo 1.5, go to Admin CP > List Add-ons
There should be a "Disable all add-ons" button.
Can take a while to process and rebuild everything, but you can re-enable everything with one click, also, it remembers the add-ons that were already disabled so they won't get re-enabled by mistake.
There should be a "Disable all add-ons" button.
Can take a while to process and rebuild everything, but you can re-enable everything with one click, also, it remembers the add-ons that were already disabled so they won't get re-enabled by mistake.
snoopy5
Well-known member
cool, I did not know that this was available in ACP...
I disabled all addons now. After all addons were disabled, I could even not change the date of birth in ACP anymore. I thought this would be a core feature?
So if this is a feature of an adddon, I have to find out first which one
I keep you updated....
Thanks
I disabled all addons now. After all addons were disabled, I could even not change the date of birth in ACP anymore. I thought this would be a core feature?
So if this is a feature of an adddon, I have to find out first which one
I keep you updated....
Thanks
snoopy5
Well-known member
update:
The addon is called: "Edit User Join Date by Waindigo"
will try to get there some help:
https://xenforo.com/community/resources/edit-user-join-date-by-waindigo.140/
The addon is called: "Edit User Join Date by Waindigo"
will try to get there some help:
https://xenforo.com/community/resources/edit-user-join-date-by-waindigo.140/
It is. It's under the Personal Details tab when you're editing the user.
Ah, that makes more sense, then.
Actually it's probably expected that the add-on gives that error. We're dealing with a UNIX timestamp for the register_date field, a value of 0 would be Thu, 01 Jan 1970 00:00:00. That field would need to be able to accept negative numbers for that to work, which would require that add-on to alter the field definition we have set - I'd recommend leaving it as it is.
That said, if the objective is actually to set a certain date of birth then, yes, that's definitely possible
Actually it's probably expected that the add-on gives that error. We're dealing with a UNIX timestamp for the register_date field, a value of 0 would be Thu, 01 Jan 1970 00:00:00. That field would need to be able to accept negative numbers for that to work, which would require that add-on to alter the field definition we have set - I'd recommend leaving it as it is.
That said, if the objective is actually to set a certain date of birth then, yes, that's definitely possible