I came up with the idea to create an open source "Myspace", "Facebook", "Bebo" "[insert social networking site name here" type platform using the Drupal platform. It seems a lot of people are asking how to make clone sites, or add similar functionality to a Drupal website. I work for Leo Laporte, and I know he's been thinking about having a social networking site for TWiT users.
If enough developers have a little time spare, would you be interested in helping making this sort of Platform for the Drupal community...? We'd then release it free, run it on a domain I just bought (drupit.com) as a demo and working social networking site. I want to make it clear that although we could all benefit from this as the developers, the community as a whole would also. The project wouldn't be owned by anyone, and everyone could pitch ideas and once we have an alpha and beta version, people can start testing it.
Once they run it on their site, they can do whatever they like with it. No one gets paid for this, it's an OPEN SOURCE project. If you later want to give it to a client and charge for customisation, that's your right to do so. I'd love to know how many Drupal developers are available to help create this "one install" package. This would open up so many possibilities for users. I for one would also be using it on a local community site I currently have under development...etc.
Is there any method to allow users to block content by taxonomy?
I'm working on a gallery art site, and I want to be able to allow users to opt out of viewing specific types of content when checking the updated pages. eg: every item has a choice between sketches/3D/sculpture, and the user only wants to see sculptures, or wants to see 3D and sculptures, but not sketches.
This is related somewhat to ignoring users (really, a staple in many social networking sites) but contentblocker seems a little.. incomplete.
Yogurt SN is a third-party module for XOOPS. Even though it is limiting, the `privacy options' is quite nice. A user can have albums, groups (called tribes), and that Scraps (guestbook, similar to the Wall)
And the user can set per album, per picture for friends, for other users, public or only for himself.
Drupal's Buddylist is not integrated with NodeAccess. You have to type in a username, then click `Search' then click on `view'.
I'm writing some code that could one day make it into a module so I'd like to make sure I'm following best practices. Can anyone please help me out with the node_revisions table? Here's what (I think) I know thus far:
There will be one node record and 1 or potentially more node_revisions records related on nid.
There will be only be one node_revisions record for a given node when revision tracking is off.
node_revisions.vid is the primary key and hence will be unique.
node_revisions.timestamp contains an integer that corresponds to the the this revision was last updated.
My basic question is this: Is there any way to categorize blocks using the taxonomy module? Let me give you some context so you'll see why I want to do this and maybe someone can come up with a better idea than what I'm thinking.
The owner of the site really likes being able to rearrange the six boxes on the front page. I'm using blocks for those boxes and styling them one at a time using CSS (in other words, I have separate CSS rules for .block-block-1, .block-block-2, etc.). Some of them have dotted outlines and a little pair of scissors, and are thus intended to be coupons. Some are simply a solid border and are used as shout boxes. There are six different colors he can choose from. So, he already has 12 different blocks that he can swap in and out of the mix.