'Destiny'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
ita, would you still be able to, if you wished, have it display more to a page?
In theory ... I'd like to cap it at 50. The search function is very intensive, and it was what drove server load up and crashed the CPU the first time we went down.
So, like Google and all the other big search engines, not too many.
FWIW, it's a rule of thumb with commercial search engines, whether general web ones like Google or site-specific ones, that the number of clickthroughs to each next page of search results declines exponentially. If people don't find what they're looking for on that first page, they tend to refine their search and try again.
The one time I did user testing on search (on a corporate site, so, YMMV), I also found that people didn't as a rule *want* to see a huge number of results -- they got overwhelmed by it. If, as I'm guessing, the average Buffistas search is more like "where was Rio's post about the muffin theory again?" than "I want to see everything this person ever posted," then a smaller number of inital results is going to be a help to the average searcher rather than a hindrance.
In theory ... I'd like to cap it at 50.
Um. I'd kind of like it to cap at 50 also.
Yes, even though we tested it here, the search function on a fully operational board is still making me a little nervous.
Would it, like Google, give you the number of results?
The date stamp is determined by where the server lives. HR is in NY, fangeek is in CA.
Cool. I'd wondered if that were it.
My new tagline is, if I've counted correctly, precisely 255 characters long. And yet I'm informed that it clocks in at 257. And yet yet, it looks fine in practice.
Are those extra two characters something other than the plaintext, thus making their truncation no problem, or am I tampering with forces I can't begin to understand?
I confirmed Robert's observation. I tried some other long taglines. The quote marks are getting counted twice. As Robert notes, it doesn't truncate incorrectly, but it is odd.
Noted. That should be a reasonably quick fix.
Am-chau, what's the list?
It's long, list-like, and filled with listy goodness, ita.
In summary:
Some of these seem to be slightly on the 'policy' side of the question, and I'm not entirely sure about the priorities given to some. However, that's roughly the shape of things.
an if-clause in the post-displaying code -- if they're an admin, replace "!STOMP" with the stompy image or whatever.
I think this needs to be modified to "an admin only quick edit (!STOMP) that's replaced with the stompy image".
And added needs to be "design stompy image" (I do remember something floating around).