Heh! I went to my profile to add my date of birth (admitting my age won’t hurt all that much), and it won’t save the date I put in, it keeps changing it to 1969! Not that I mind being 36 again...
Looks like datefunctions.inc uses the base php functions (date, mktime, checkdate) which depend on the UNIX epoch *and* the "DOB" is stored as an int(10) on the db instead of a date field, which makes this hack much more difficult. The field itself would have to be changed to date, datetime or text, and then the alternative (to date, mktime, etc) functions would be applied. In the past, I have changed the date/time funcs to ADODB date/time with success on blogware that stores the date in a wider DB field, seems to do the trick.
I’d really like to see this changed as well - I use pre-1969 dates in some of my historical references (and just turned big 5-oh myself this week!).
I did notice that TVs work (they are stored as text), which I was using for my history stuff. Perhaps the only truly affected field is DOB?
Any thoughts from development? I’m willing to help on this, but I’m still a neophyte to modx ...
The forum is running SMF, so the problem lies there I fear. :/
, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Yes, this is not a MODx issue at all, but a SMF issue.
You can leave year feild as 0000... I guess
Sorry I missed that the forum topic is the forum itself (doh). But I did notice that my DOB in modx comes up blank for me if I enter something in the 1960’s. And then I noticed that the dob attribute in the modx_user_attributes table is an int(10), so I assumed it’s being stored as UNIX time. I’ll search for a like thread in a more appropriate topic.
While I’m moving very off topic, I really think modx is the best open source cms/blog tool I’ve experimented with and/or used to-date! Many thanks for the effort!