My upcoming birthday list is showing maybe 50 or more names saying they were 1 or 2.
On the calendar it says their birthdays are the 27th so I was wondering how I can fix it so they stop showing for the next week or so till that day passes.
It's obviously not everyone's birthday that day, especially when it says they are all turning 1 or 2.
I thought of disabling the calendar for a few days but would welcome any better advice.
Thanks. :)
http://www.puntroadend.com/yabbse/index.php
Well, it's currently set to show birthdays within the next few days. Today's are shown in bold. This can be changed in Edit Features and Options.
http://www.puntroadend.com/yabbse/index.php?action=profile;u=12
That says he's 1 year old. He or she probably entered the current year as their birthday - it's a common mistake.
-[Unknown]
It's strange that we usually only have one or two birthdays a week then get 50 or so on that one day. The feedback I have from a few people listed is that it isn't their birth date anyway.
Wait, did you convert, originally, from YaBB?
-[Unknown]
Yes.
It's possible that, due to a bug in the old YaBB -> YaBB SE converter, you could have anyone who didn't have a birthday with YaBB set to have on on the date of the conversion...
This can be automatically fixed, but explains why they're all on the same day. This is a notorious problem, so i should have realized it was the case earlier.
If you want, I can fix it for you - or give you a query to use to fix it yourself. If you want me to do it, I'll need your phpMyAdmin password, as I delete them regularly (I don't want to cause security problems for anyone.)
-[Unknown]
Thanks Unknown....will send you the details.
Thanks heaps for responding so quickly and fixing the problem Unknown. :)
Lainaus käyttäjältä: [Unknown] - maaliskuu 21, 2005, 10:24:49 IP
If you want, I can fix it for you - or give you a query to use to fix it yourself.
Unknown the far more technical minded person than myself who helps with my site has asked the general gist of what was causing the problem if you wouldn't mind giving a short explanation please.
If you're too busy please ignore. :)
Well, okay, here's a summary:
When you converted from YaBB to YaBB SE, the converter read in dates and checked to see if they were valid. If the member didn't enter a date, it would be invalid; because of a bug in the code, it used the current date for the birthdate instead of keeping it as none. This was corrected in a later version than you (and most people) used.
To fix this was simple. I determined which date it was by checking for the most recent birthdate (it's unlikely anyone else would be less than 5 years old :P.) Then, I used the following query:
UPDATE members
SET birthdate = '0000-00-00'
WHERE birthdate = '1234-56-78';
Where '1234-56-78' was the bad date.
After that, I noticed that a few of your tables were a bit large, and that you were using MySQL 4. Because of this, I was able to optimize some things and I converted a few tables over to InnoDB. Your forum should be performing faster now, especially for searching.
-[Unknown]
Thanks Unknown,
I'll pass that on.
I have to say the SMF search engine is super efficient and far better than those I've used on other sites. Wel done SMF. :)
Lainaus käyttäjältä: rosy - maaliskuu 23, 2005, 01:09:46 AP
Thanks Unknown,
I'll pass that on.
I have to say the SMF search engine is super efficient and far better than those I've used on other sites. Wel done SMF. :)
I remember when you were having problems with it because it was slow ^_^. Then again, that's why we fixed it :).
-[Unknown]