User login

Agaric

Using LDAP Serverside

Most LDAP functions used at Agaric will be controlled through the Drupal interface.

When for some reason you need to use LDAP straight, here is how.

Type ldap and press TAB to see the available ldap commands. You can then use "man ldapetcetc" to look up that particular command (there is no "ldap" command).

Common commands you may need:
ldapsearch -x cn=Username

ldapsearch, ldapmodify, ldapadd, ldapdelete

To delete a user you need to connect as admin:

Show authors of all revisions on an article of content

Searched Words: drupal show authors of all node revisions multiple contributing users

Related how to for Drupal 5:
Adding 'Last edited by name some time ago' information
http://11heavens.com/adding-last-edited-by-name-some-time-ago-info-to-node

Trac administration with real examples

Run trac-admin commands on the server hosting the trac sites. In our Debian server setup at least, individual projects are in the /srv/trac/ directory, and every trac-admin command should be followed by the path to the project you care about.

For more information than man will give you, use:

trac-admin help

To make a user an admin (I believe this will automatically create a new user if it has to) --

trac-admin /srv/trac/example permission add username TRAC_ADMIN

Select multiple users to delete sorted by registration date and with one profile field (Drupal 4.7)

Side note: Deleting directly with MySQL:
DELETE p, u FROM dru_profile_values p LEFT JOIN dru_users u ON p.uid = u.uid WHERE u.created > 1317450417

On to the long obsolete main show:

If you are unfortunate enough to be doing anything on Drupal 4.7, here is a bit of empathy.

If you have a 4.7 site, it probably has a lot of spam registrations. Drupal 4.7 doesn't have a multiple user delete. And Userplus module doesn't provide a very useful list in its multiple user delete.

How to call the path to theme from within the theme (and why)

We had a site that occasionally generated page not found errors for ie6_fixes.css. Occasionally, we realized, because this file was only sought by browsers following the hide-from-everything-except Internet Explorer 6 code. The file was then not being found because the name of the whole theme had changed, and the existing template had hard-coded in not just the location but also the name of the theme.

Changed in page.tpl.php (and all variations such as page-front.tpl.php and page-node-4.tpl.php:
@import "/sites/default/themes/jonas_theme/ie6_fixes.css";

D7 Book Proposal

Holder for uploaded file.

Cannot merge error message from Git likely due to an added but uncommitted file

"would be overwritten by merge. Cannot merge."

Git tells you which file it is. Use git status to see if it is added but not committed. Commit it. Do the merge again. It'll probably work.

In the future, check your local state before pulling (or performing an Agaric Capistrano task that includes pulling a commit back down locally).

Use Git to commit to CVS, such as for maintaining a Drupal module

UPDATE: See http://more.zites.net/git_drupal_contrib_cvs

Kathleen says this is complicated and not necessary - http://drupal.org/node/288873

HOWEVER-- if you ever want to let other people contribute to your project the normal way (if CVS can be considered in any way normal), then you will want the synch anyway.

Syndicate content