Drupal for Evil

...for Drupal 7 has 666 patches in it.

That is all.

I did a little experiment recently to see how we could get e-Commerce Transactions into views in D5. The reason I did this was because I'd like to de-couple store crud routines from store admin ui code so that someone could write an alternative admin interface for ecommerce. The current admin interface is clumsy and always begging to be hacked.

For those not familiar with ecommerce, transactions are represented by a few tables, I was just interested in the main one ec_transaction for this experiment.

(Note: yes, usernode does something like this for users.)

I found this coming in from Drupal planet http://www.tech-wanderings.com/drupal-nofollowed-too-pervasive.

Greg Holsclaw talks about how nofollow attributes could be hurting Drupal (rel=nofollow being a well intentioned way of deterring spam. Something that has managed to keep the ratio of spam to real content on the web down to a respectable 10:1 :P) Basically, he points out that most internal links on drupal.org get the nofollow attribute attached to them.

Greg makes a number of good points, but I think the two most important are:

Yesterday I downloaded and played with the Drigg module. Among its features is an option to let a privileged role submit content as a different user. The list of spoof users is also an administration option. The motivation for this is clear... it lets a handful of people easily make a site look like a bustling community. This is great for jumpstarting your Drigg site (which is designed to be a Digg clone), but how ethical is it?

Disclamer: this only contains usernames with certain words in their nicks. If you want to block them, please check if they are legit

<

ul>

A small follow-on to brilliant past posts by Moshe and Angie:
How to dizzy the next guy
#DANGEROUS_SKIP_CHECK: the most evil of the Form API properties

Since core is mostly frozen, I'm thinking of evil ways to use new features in the Forms API for 6.x.

Hello,

I wanted to announce a new module, just released today: Node Cloud. If you're familiar with tag clouds this module should look pretty familiar: it themes the output of a view like a tag cloud.

The primary ordering of the view is from the first sort. The sizing of each item is based on the second sort order. This makes the plugin very versatile for making clouds of popular content, highly rated content (say with the voting api), highly commented content, etc.

To make our evil plan to genocide "patch (code needs review)" issues today (under the guise of "patch review day") go off without a hitch, we will need dww to do our bidding as follows:

1. Find the list of issues that are in a patch* state but have no attachments, and leave the list under the bridge in a paper sack.

Deletion API documentation here: http://drupal.org/node/153904

Before doing anything else, we should fix http://drupal.org/node/154046

Additional links to issues:

The über-evil Steven Wittens wrote this great piece of information/inspiration.

We still have space for several more lightening talks at the OSCMS/DrupalCon. I'd like to have around 10 or so, if possible, so please step up. You can sign up for a lightening talk by leaving a comment on the LT page. This would be an excellent opportunity to show off something evil. I'll be talking about viewfield, first announced here in D4E.

Us: A decent sized Drupal development firm, working with some of the biggest sites in the Drupal Community

You: A talented individual with php skills, MySQL skills, CSS skills, Drupal skills, sword fighting skills, etc, etc.

The offer: A short term 1 month contract working on a client site, leading to full time employment in March if you know your stuff.

If you like us and we like you, the possibility to join the company on a long term basis, or if you don't want that, a sweet 1 month gig.

Hey Evil Drupalers,

I wanted to point you to the Drupal Lightning Talks at DrupalCon. They're a great opportunity to showcase something truly evil about Drupal.

Now back to your regularly scheduled evilness.

To my dear New York City, Drupalistas and soon to be Druaplistas,

We are two weeks away from DrupalCamp NYC 2, 20 & 21 Jan. A few of us have been thinking what if we concentrated our efforts on a single project instead of working solely on individual projects? I'm not talking about a classroom setting, but a project (ie install profile, module stuff and theme) to educate each other?

Well here is your opportunity to change the future of one lucky group. Big or small, non-profit or community organization... If you know of a project that can use the assistance of a Drupal site, we need you to nominate them. The lucky organization will also get one year of CivicSpace on Demand (hosted and managed install of Drupal 4.7 and CiviCRM + EMAIL)!

Every day I get two or three spam mails through the contact form on one of my homepages.
This is why I think, that the contact.module and Drupal is evil ;)

Do you have the same problems?
What are your solutions against this?

Regards Tobi

Hello views aficionados. If anyone has the time, could you review the module posted in

http://drupal.org/node/103171

It's a module (that I will recode as a patch to views itself, eventually) that provides views within forms. These views can be used to select nodes. It includes exposed filters and a pager, and it generally behaves exactly the same as any other view would.

The module even includes a test harness where you can click a few buttons and test the new form element with any view on your website.

This is not production code, but I wanted to alert people early. Please do review this module and let us know what you think. It's a lot of code, and may require some changes to the underlying views implementation, so the more people who try it, break it, and suggest changes the better. Also, you can use this to start testing with your own modules.

Sorry, drupalistas, but this is a goodwill project for NYC teachers. Coquille, my good friend/teacher/activist wants to create a really really simple site to teach other NYC teachers how to recycle. By law the schools are to recycle, but the school system refused to educated nor provide supplies for recycleing. So enter my friend, armed with a dozen or fellow teachers to do data input and create content. They need something simple that will be functional and hopefully get a bit of press (IE... free advertisement for you.)

I'm just the connector here... So please be nice. ;)

Noel

I'm looking to create a website to encourage recycling in NYC schools. I'd like the site to start with teacher and student-generated content created by our school, with the idea that our resources/recycling system could be easily replicated in other schools. Eventually, other schools could join in authoring content. Currently, few schools are recycling in NYC, which is totally frustrating because it's the law and, more importantly, the right thing to do.

Hello,

I've posted a timeline of viewfield development, if anyone is interested:

http://drupal.org/node/100971

Cheers,
-Mark

Update: I've attached a screen shot of viewsfield working with filters. Also pictured: ajaxviews - loading a teaser on top of a views table. Way cool.

I've been thinking about some of the specifics of creating a personal workspace within Drupal -- although my main area of interest is education, these thoughts have applications outside education -- these are some rough notes, and I'm curious to see/hear reactions about what I'm missing/overlooking. These notes are not intended to be comprehensive, but a starting point in a conversation about some specific functionality

Some basic functionality--

<

ol>

[ Edit ]
To make a long story short, it turns out that robroy was already well ahead of me in figuring out why the old documentation wasn't helping people and will update the documentation next week. Serious props to his chops for the effort.

If you're interested in how this is shaping up, take a look here.

[ / :) ]

I noticed webchick had pulled the old documentation for writing installation profiles a couple of days ago, and after kiting her a brief email, feel like I know what's going on with Drupal, for once, or at least the docs. Short version being that the old ones were as dated as they appeared, and new ones will require a little research to complete, so I will be taking a stab at this over the next couple of days.

Here are some directories in CVS that do not get any love and by love I mean downloads.

It could be for lots of reasons why they are not downloaded, but the bottom line is that they are not popular and could be considered for removal from CVS and/or Drupal.org project pages. These are only the directories in contributions for modules/, themes/ theme-engines/ and translations/

I wrote this on my blog 1 year ago. I bet the list could be made even more fiendish today

Drupal has gained some powerful tools in recent year(s). They are all valid and useful. When used improperly though, they can become dizzying. Consider these misdirections ....

• Rewrite arbitrary SQL queries fom your own module
• Rewrite forms from your own module. Add/remove fields and change the Action attribute
• Alias some system urls so he can't tell what module is handling the page
• Implement some theme() functions so he can't find who is outputting an HTML chunk
• Drop small node-story.tpl.php files in the theme directory so that he can't figure out why stories look different.
• Use menu.module to restructure your Navigation block. Change some link text while you are there.
• Use the 'arbitrary PHP' feature of blocks to show only for certain people on certain pages.
• Implement advanced database prefixing so that he looks at the wrong tables by accident. Ouch!
• Switch themes from some obscure part of your code by changing the global $custom_theme variable.

Tucked away in form.inc is the little-known #DANGEROUS_SKIP_CHECK property of the Form API. It's so evil that it's not even documented!

What can you use this little nugget of fiendishness for?

I believe the evil credentials of views and CCK are well established. I wanted to unveil a new module that combines the two into an unbelievably devilish system: viewfield.

Viewfield allows content type administrators to add view reference fields into CCK content types. When a user creates one of these nodes, he/she can select from a list of views to embed into the node. When the node is viewed, the view runs and is output as one of the node fields. (Of course this can be themed).

What an auspicious day to start the Drupal For Evil group. I welcome you, my brothers and sisters in evilness, to this group. May our reign of terror be long and fruitful.

<-- break -->

As we march forward in our world domination, feel free to use this forum as a place to post your evil tricks and hacks. Deriding alternative web technologies is welcome and encouraged. We will rule them all. Post evil code snippets, laugh at evil websites, and generally take pleasure in all that is Drupal for Evil.