User login

Drupal

Where can hook implementations be placed so that they are called?

.module files or any file mentioned in the module's .info?

Excellent, excellent questions from Randy Fay:

23:30 rfay: Can anybody instruct me about where hook implementations can be placed in D7?
23:31 rfay: Can they be placed in any file listed in the info file's files[] ?

Send an e-mail to an administrator when a new user registers on a Drupal 7 site

10:13 benjamin-agaric: Drupal 7 - the simplest way to have an administrator e-mailed when a new user signs up? Can't find any core setting and no trigger does it either? Seems we should have a way to get this functionality short of Rules module... thoughs?
10:22 benjamin-agaric: Answer: it can be done through Drupal core- an advanced action simply has to be configured first at admin/config/system/actions/configure and then back to trigger configuration.

Do not link to the page we are currently on

Is this a generally accepted concept that links on a page should never go to that page itself?

Found this: "No link in a menu should simply reload the page itself"
http://www.webmasterworld.com/forum21/3705.htm

How to do it:

Menu System - Drupal API
http://api.drupal.org/api/group/menu/7

Export and re-import a database with Drush and the command line

These are run from the project's web root, example/web, so that drush can run, but the database itself is stored outside the web root, example/db.

On the export side:

drush sql-dump > ../db/development.sql

On the import side:

drush sql-connect < ../db/development.sql

expands to:

mysql -hlocalhost -uexample -pyMsx2rIP drupal-example < ../db/development.sql

An interesting RFP for a Network of Networks: HASTAC.org

The primary goal for the new hastac.org is to be simple and flexible. We are an organization that is always changing, and we expect our web site to be able to evolve along with us as we expand, experiment, and learn together. In our request for proposals we outline a number of specific approaches that we think will help us accomplish our mission effectively, but no single feature is as important as the need to keep the site easy to manage and simple to change in the future.

Using Imagecache for a theme's user-provided logo

Agaric considers it best practice (meaning we do it occasionally) to keep a logo (the user-uploaded logo), so that the site principal can have its logo swapped out by an administrator, and not only by a developer or themer. Practically, some designs will have the logo so integrated that it should not be swappable, but note that one additional advantage of having a clean and separate logo file is that people can swipe it and display their brand loyalty while linking to you. Or maybe add devil horns to it in MS Paint.

Syndicate content