'Get It Done'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
ita will confirm, but I'm pretty sure that the search function will return here once ita has finished coding it (it was always in "beta" at HR). We did a stress test of the search function here at fangeek before we went live, and the host admin didn't think we overtaxed their resources.
Once it does return, it will do exactly what you are asking for.
Actually, it won't be quite so threadsuckable. The beta version, yes, but its main problem is returning all the results on one page. That's very taxing and resource inefficient.
Okay. Thank you. Carry on.
That's very taxing and resource inefficient.
Especially when you have people searching themselves to see how many posts they made on the entire board.
t cough cough
Not that I would ever do that or anything....at least not again.
June 19, 2003, 3:27 pm Aimée[68]: ERROR [2] mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) line 74 of file /home/bufforg/public_html/classes/giles.php
There has been an error. It's of the type we call fatal. Please don't be scared. You're not the one that's going to die.
Okay, where the $$&#&(@#& are the developers?
Just got this 3 times in a row. FYI.
and so did I, in literary.
I got the same error. But all better now.
For search, would it be worthwhile to set something that quits the search if it's going to have more than, say, 100 results? Or something? t /ignorant unhelpfulness
My plan is to have it search in segments of 20 per page.
My plan is to have it search in segments of 20 per page.
ita, would you still be able to, if you wished, have it display more to a page? For better search-on-page ability?
Especially when you have people searching themselves to see how many posts they made on the entire board.
Ah, well, sometimes... you're searching because you want to read all of the posts your girlfriend made... t slinks off
Er, not really. What I wanted to ask was: was it intentional that we changed our datestamp from EST to PDT, or did something get jumbled around in the move...?