yay! a new dawn!!! zum... err... hehe... I meant Lebogang, Lebogang!
Happy daze on 75th apples!!!
Alo,
This is the 75th Apples version. The backend has changed drastically --- a few minute UI tweaks -- I haven't added a lot of functionality. The objective of the update was to have a 'backend' I/we grow with.
It will be easier to add things as time moves along.
Like clock work, if you spot errors, let me know --- it will be appreciated.
*oh, the ajax/comment/delete doesn't work, yet --- I will fix that now --- internet explorer 6 is not supported at all. Sorry. (and ie7 doesn't wanna place nice with all the kids, eish).
till tomorrow --- I need some sleep.
1ove, progression.
yay! a new dawn!!! zum... err... hehe... I meant Lebogang, Lebogang!
Happy daze on 75th apples!!!
well, almost --- we got hit by some problems, which I am not actually sure, what they are --- but will see if they replicate.
in essence I'm putting this 'stable', till it survives a week at the least.
(bow)
and, now it turns out ie8 doesn't work as well.
*arggggg, I need my sleeeeeeeeeeeep.
I'll test in Firefox and Chrome. I don't play in the IE world if I can help it.
Well done Lebogang ... Apple's LIVÉ!
Ah, tested on ie8 (service pack 3) --- it seems okay, but Kunta/Kinte insists there is something wrong.
*sigh
(bow)
ups and downs --- I honestly do not know why it keeps dying ---
when I get home, I pulling out the an afro-comb and go through the code line, by line,,
ol'right --- we figured it out --- it's not the code, well, not entirely.
it's mysql --- something-about-something-that keeps queries in a 'lock(ed)' state.
We are investigating why.
Okay, I think we got it sorted, just a little bit.
Now, we wait for tomorrow, peak traffic.
It appears the problem was a very bad SQL JOIN query --- which rendered any other follow up query to que and wait for the JOIN to finish.
I think I have it sorted --- but, we will test it out. Sadly I can't do it, coz of the 'role' I play within the site. So if anybody can try the 'messages' page and navigate throughout (reading threads, adding contacts, sending messages) then we will know if it worked.
the query involved checking to see if you and 'a friend' are contacts --- that is to say it checked if you have made them a contact AND they too have made you their contact.
that JOIN created a massive data response from the Database --- on the local dev machine there is only 20-30 pple, whereas on 75 there is about 300, so, 300 multiplied by 300 resulted 90,000 records being returned, hence the pseudo crashing of the site.
the new version is awesome
ta!