5th Sep 07, 10:41am |
I've just been experiencing the "you have not posted anything bug"...its php5 related and therefore I can't be frigged to fix it. Remove any symbols you have in your post and it should be fine.
ANYWHO, you can register, login, post a thread, post a post, view forum/thread/index
I'm swamped with work atm, but wuggawoo beta has had a lookin. The design header is fixed now due to help on neowin
ANYWHO, you can register, login, post a thread, post a post, view forum/thread/index
I'm swamped with work atm, but wuggawoo beta has had a lookin. The design header is fixed now due to help on neowin
I will use this thread for updated.
Forum activity replaces thread management, I never liked the idea of subscribing to things anyway and it never got used.
Login now relies on your emailed password.
Manage Account now has password changing.
Search and Private Messaging are next up.
Forum activity replaces thread management, I never liked the idea of subscribing to things anyway and it never got used.
Login now relies on your emailed password.
Manage Account now has password changing.
Search and Private Messaging are next up.
Im tellin ya this remember me does work. I went out at about 9. Im back now and i've had to log in again. I cleared my cookies like you said!
"Cannon bends over for his Father" : They call me Gaz
Well I've renamed it to New Posts but the time bug is something I'm slightly unsure of as its complex math, example;
60 = 1 minute minute, 3600 = (60 x 60) as in one day
Anyway, another significant change is that I've switched from timestamp to datetime back to timestamp. Mainly because theres no benefit to datetime. So you understand datetime is essentially yyyy-mm-dd+hh:mm: ss, whereas timestamp is unix timestamp, where a second = 1 and each second +1's to the timestamp (which interestingly runs out in 2037).
Okay so to work with datetime, essentially any time function had to convert it back to timestamp as otherwise you're modifying the datetime before hand which is basically making the time class one big wrapper for datetime to timestamp.
The other big change, is registering you online is different to Wuggawoo version 1. I forget how v1 works, but this version basically looks at a field called last_seen, if its older than 5 minutes and newposts = 0, then we update it, we also update it if you view a thread. I think there was a delay on version 1 but its pretty sloppy, this way is better imho.
I've once again updated the session class, I think I might have fixed it this time so no more relogging in after a few hours.
$uptime = time() - $timestamp;<
$year = floor($uptime / 31104000);<
$month = floor(($uptime % 31104000) / 2592000);<
$day = floor((($uptime % 31104000) % 2592000) / 86400);<
$hour = floor(((($uptime % 31104000) % 2592000) % 86400) / 3600);<
$minute = floor((((($uptime % 31104000) % 2592000) % 86400) % 3600) / 60);<
$second = floor((((($uptime % 31104000) % 2592000) % 86400) % 3600) % 60);<
60 = 1 minute minute, 3600 = (60 x 60) as in one day
Anyway, another significant change is that I've switched from timestamp to datetime back to timestamp. Mainly because theres no benefit to datetime. So you understand datetime is essentially yyyy-mm-dd+hh:mm: ss, whereas timestamp is unix timestamp, where a second = 1 and each second +1's to the timestamp (which interestingly runs out in 2037).
Okay so to work with datetime, essentially any time function had to convert it back to timestamp as otherwise you're modifying the datetime before hand which is basically making the time class one big wrapper for datetime to timestamp.
The other big change, is registering you online is different to Wuggawoo version 1. I forget how v1 works, but this version basically looks at a field called last_seen, if its older than 5 minutes and newposts = 0, then we update it, we also update it if you view a thread. I think there was a delay on version 1 but its pretty sloppy, this way is better imho.
I've once again updated the session class, I think I might have fixed it this time so no more relogging in after a few hours.
Email