Two new recent launches for dating sites built on Drupal

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
drupdrips's picture

Here are two additional drupal dating sites. One is a Lesbian Dating site and the other is serious dating site. These dating sites are in active use today.

Both sites employ pretty much all the modules as stated in this thread http://groups.drupal.org/node/51698, except Buddylist as it did not need to utilize any user relationship/association type functionality. These two latest cougar dating sites are more typical of industry standard features. Users are allowed to join for free as "Basic Members". Basic members can use the "send drink" feature (a custom written module) to show initial interest and also reply to messages from other subscribed members for free, but cannot initiate new messages to members without being a subscribed member.

All members are also allowed to create private profiles which can be only viewed by subscribed members if they have the view permission granted by the profile's owner (user owning the profile). This is to offer users privacy where they don't want to reveal more private details about them to the wider audience and only selectively permit certain users in their inner circle who they like or trust. Subscribed members can send a request to access someone's private profile. By default all subscribed members have access to a user's private profile at the time of creation. But the user owning the private profile can remove the default access and add only certain individuals of their choosing, either upon request for such access from that individual or of their own choosing. Most of this is driven by the nodeaccess module and also some custom code.

Other than that everything else is pretty standard with CCK and Views being the main engine behind profile data generation and presentation. Some of the rest is the same as I stated in my previous thread on NOTforPlayers.

Comments

Hi Drupdrips, I've seen your

artscoop's picture

Hi Drupdrips,
I've seen your 3 sites made with Drupal.
As good as they can be, there still is this Drupal look which cannot be mistaken.
To be on par with amny other dating sites, one needs to customize his site layout and theme.

However, aside from this, this is a neat job.
I have a few interesting questions about these sites :
How do you administer ? Is it easy ? Have you set custom tools, something ?
Are the sites not too memory, database and CPU intensive ?

I diggit

drupdrips's picture

I actually dig the drupal look especially the register/userlogin/request password. Drupal has it the best way and if I was using another CMS or my own custom style I would like to adopt drupal's look & feel instead. Unless you use the default garland theme which a lot of drupal sites get nickanamed for as drupal'ish, there is nothing like a drupal look. It really boils down to your theme and use of images.

there are utility functions written for cron execute (some functions only execute on certain hours regardless of cron frequency) that does most of the administrative functions. Of course, profile creates need a human eye to evaluate for the image uploaded and text in the open-ended description (although bad words filter is in place in addition to a human check), other than that it's on cruise control.

The site is optimized via as much caching as possible - boost for static files, memcache, opcode cacher - xcache, drupal's own cache sets of course .. query tuning for mysql, avoiding unnecessary php execution by using custom module to really drive the most repeated functions. Even though some of the contrib modules may offer the same functionality it may be better (and at your own risk) to strip down to the unique functions for your site's custom needs and aggregate that in a custom module. I like drupal core as it is optimized, secure, lean and well-written code as it can be. Custom modules I tend to strip and use ideas maybe, but mostly custom written for the site. With an opcode cacher on top of that or memcache you would have done as much as you can for php tuning. The remainder is tuning up for scalability based on traffic volume and traffic type (anonymous/loggedin). higher RAM/CPU/ are easy to scale up, disk I/O throughput is not so easy, but I have not had to think about disk i/o yet although my VPS slows down during Americas wee hours of the morning as they run backups for the entire server. At that time it shoots the wio% high for small reads even, which is not good. But other than that, if I really need to drum up disk i/o speed and if my traffic volume justified it, I would go for SSD's and trash the scsi.

Dating

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: