Developers and coders

Comparison of Lightbox-type modules http://drupal.org/node/266126

Three ways to deal with troublesome users.

1. Using a contributed module. Read more.
   
2. Build in Drupal version 6 under admin/user/rules You must setup the appropriate access rule. You can find any user's IP address under admin/reports/dblog Search under the Message column for Session opened for User-Name-Here. Then click on this link. User's IP address is on the next page. If not working make sure that the Tracker core module is activated.
3. At server level with HTACCESS. Read more.
   

This article attempts to do a comparison between modules able to deal with troublesome users. This article should allow you to choose which module best suits your needs.

What is a troublesome users?

• Offensive, hostile, insulting behaviour
  
• Flamebait
  
• Spammer
  
• Spambot
• Scraper
  

Bottom text in Ukrainian - fixing sorting trouble with "і" "ї" "є" letters

При сортуванні матеріалів за допомогою модуля views було замічено
помилку. Матеріали з українською буквою "і" поміщаються вище ніж
матеріали з буквами "а", "б",... і т.д.

Вирішення цієї проблеми полягає в заміні порівняння кодування з
utf8_general_ci на utf8_unicode_ci.
В моєму випадку сортування проводив по загаловках матеріалів. Виправлення:

Оскільки сортування прводяться не тільки по цих полях, тому варто
змінити це у всій базі.

snippet fix by Brun

If you have built your Drupal site on a development machine using multi-site configuration, you've discovered that there's a headache that will occur once you've ported your site to its live box. If you are about to do this, then you'll soon see the problem.

The problem lays within the site/files directory. Once you've uploaded your development site to its live server, you'll discover that you have to go into your tables and change the paths for images and other files. On your development box, you named, just for the sake of example, your site: drupal/sites/mygreatwebsite.com And in both of these directories, you've added a files directory.

To the world, that site will be: thegreatestwebsite.com and its file structure is drupal/sites/thegreatestwebsite.com Once you went live, you'll see that the paths to your images, pdf and other files looks something like this: http://thegreatestwebsite.com/sites/thegreatestwebsite.com/files/myimage...

On one hand, you gulp at the length of that url. Next, you sigh because you realize that you have to change the path -- in the database.

Drupal 7 has a fix for this -- not the length (that's another story) but for the path problem.

And, while it won't be committed to Drupal 6, there is a patch that you can add to Drupal 6 -- if you don't mind doing that no-no: patching core.

What are packaged install profiles?

The job of the drupal.org packaging system is to take the code for a project, assemble it into an easily downloadable format, and post it to the project's pages on drupal.org. It's an automated system that takes the headache of distributing code off the hands of the developer.

Modules and themes are packaged in a fully automated fashion -- once a release node is created, the packaging system handles the rest. Installation profiles are a bit more complicated to package -- because they can contain modules and themes from other projects on drupal.org, as well as Drupal core. To use the full power of profile packaging, you must include a 'make' file with your profile. This file tells the packaging system what other projects should be included in the release download. As a profile maintainer, all you have to check in to CVS is the .make file, and the packaging script will automatically assemble all of the modules and themes it references when creating the downloadable file archive for a given release.

Quickstart

This quickstart assumes you already have a profile project on drupal.org, and that you're ready to create a packaged release.

1. Install Drush/Drush make