Hi People,

After having used Pligg for quite some time and frustrated with its limitations that only Drupal could meet (like, being able to post blogs, videos, stories, custom content type) to the website, I have started a project called Drupaligg (Digg clone using Drupal) and am releasing its first source code compiled and integrated with all required modules and interface. This is still a testing verison, but should work without much trouble.

The demo is available at:
http://drupaligg.programmingbulls.com/

The code and the details can be found at:
Drupaligg: The Open Source Digg/Reddit Clone using PHP based Drupal
http://www.programmingbulls.com/drupaligg-open-source-diggreddit-clone-u...

Please check out. And do not forget to contribute to the development of the software making it more feature rich and competitive than Pligg using the power of Drupal.

Thanks
Sudeep

Comments

jasonwhat’s picture

So is this using some existing modules, or is it using custom modules? I looked on the site but it wasn't clear if you've changed drupal, created your own modules (if so are they in CVS?), or just configured existing modules in a way that makes it like digg.

sudeoo’s picture

Currently, it is existing modules, but i did make a lot of change to the theme (spreadfirefox) to make it look like digg. Other places I used views. I am writing few modules that i would be releasing as I progress with the work.

guix’s picture

Hi, I'm just a Drupal newbie. I also looked at Pligg and would prefer to use Drupal, Drupaligg is definitely a very good option to me. However it seems you release it like that : the vanilla Drupal and your custom modules, templates, ... This makes administration more difficult : how will you handle security updates, and your users, what if I want to install another module you've not included and it conflicts with yours ? I think you should release it without vanilla Drupal, it can be a .tar.bz2 or a .zip including all the modules, templates, and a PHP script on the root of the archive that installs everything, or a How-To.

guix’s picture

Hi, I'm just a Drupal newbie. I also looked at Pligg and would prefer to use Drupal, Drupaligg is definitely a very good option to me. However it seems you release it like that : the vanilla Drupal and your custom modules, templates, ... This makes administration more difficult : how will you handle security updates, and your users, what if I want to install another module you've not included and it conflicts with yours ? I think you should release it without vanilla Drupal, it can be a .tar.bz2 or a .zip including all the modules, templates, and a PHP script on the root of the archive that installs everything, or a How-To.

sudeoo’s picture

Thanks for the suggestion. guix. This definitely is a great point. Drupal is a great alternative to Pligg and this was my intention from the very beginning to create a powerful alternative to Pligg that has the power of Drupal integrated in it. And this is the reason i want to take the entire code separate and have an independent CVS repository. So that it can be used off-the-shelf as an alternative to Pligg. This was just a first testing release and I might need to do a lot of custom development to develop things to take them further altogether as an independent fork.
I would surely give your suggestion a thought and see how I can shape that. Thanks.

omnyx’s picture

this is a very interesting discussion...i would like to have a simile digg-like site and I don't know if I should start stitching up modules in drupal together myself or if I should use your package sudeep?
I know my way around drupal somewhat well and I can customize it to my liking with more or less work...
how about drupaligg?

I guess my concerns are the same as guix's - i.e. how easy I can modify drupaligg, its look, theming, add new modules, etc...
btw, I'd appreciate it if you could share what existing drupal modules you used to make it. There are vote up down, views....
but what else?

thaks for feedback and thanks for putting drupaligg together.

zoon_unit’s picture

This is the accepted way to develop custom installs of Drupal. With an install profile, the update status module will continue to work properly and users can still upgrade Drupal for security issues.

If you heavily modify any of the off the shelf modules, you can always list them in the projects list on Drupal for people to download.

Forking Drupal is A BAD IDEA, and would keep me and many other drupal developers from even considering your code.