Just a quick announcement that we've now launched club memberships for our Drupal themes, with a Standard option and a Developer option. Individual themes will still be available under a single-use, GPL compliant license. We currently have 12 themes with more to come, and will be focusing on putting together some flexible business oriented designs that minimize bloat on the back end.
Additionally, ThemeShark has been a part-time venture to date, and we will be moving to full-time to accommodate new customization and PSD 2 Drupal services.
Some months ago after the publication of my second Drupal book Drupal 6 Site Blueprints a Drupal disciple called me up and asked :
"Rabbi, my ass is grass; what can I do to take my megacool site to internet heaven? It is damn too slow".
"What have you got running on it ?", I asked him.
"Oh, it's got tons of modules installed; it can do practically everything", he proudly told me.
"Dude, you have sinned", I rebuked him.
Thus the most useful advice that most people will need to take is contained in chapter 2 of the book Drupal 6 Performance Tips - that is, disable all modules and themes that are not in use or that are not useful. When Drupal has to load with masses of code components and CSS that you don't actually need it doesn't take a rocket scientist to predict that it will run slower; and who the heck wants to wait for ages for your dot-in-the-cloud website to load?
Now grab this scene : You are at the fairground selling ice cream ; so are a whole bunch of other dudes. The thing is everybody else is selling just plain old vanilla mush , but you’ve got exotic flavors that just perfectly hits the spot at every slurp .(yummy!) Now can you guess who gets the chicks ? Okay the guy with the fat wallet not selling ice cream actually gets the chicks , but that was just an hypothetical question really.
I think this is my first post in these forums, even though I've been using Drupal for a couple of years now.
In a project I'm working on I needed to have an extended history of node views per user. I know Drupal already has the {history} table for this, but its records are purged if they are at least 30 days old.