User login

Drupal

Toward an automatically deployable per-project ticket tracker and project management site

Automatic Benefits:

Your clients learn to use an environment similar to the site you are building for them, rather than the different markup syntax and behaviors of trac or other system.

Features:

  • URL fields for bug reports which would be able to replace (or generate) the base URL with a defined set of URLs for development, stage, or production sites in use.
  • Time tracking?

Resources:

[unsolved] putting a query string in a menu local task tab link item

any experience working with hook_menu, specifically for tabs
(menu_local_task items)
how would one pass a query from one of those links?
for instance, working with organic groups, on the group nodes, want tabs for adding new content inside the group
so the link needs to be something like
node/%node/add/event?gids[]=876
876 being whatever the current group context is

Use checkboxes for multiple select form elements

Checkboxes are more user-friendly than multiple-select option form field.

Taxonomy Super Select seems to be the popular choice.

Better Select worked better for our needs, however:
http://drupal.org/project/betterselect

Fortunately, it has a node form only option. It also has an always save parent also option! All under Administer » Site Configuration » Better Select.

Note that Content Taxonomy would also be an option for this functionality.

Deleting the last content type containing a field deletes that field also

Which is good if that's what you want.

No content_field_fieldname table remaining, and no entries in the content_node_field nor content_node_field_instance tables.

Very nice!

Awesome CSS for centering a list item menu of unknown width: very useful for Drupal

We do Drupal. This CSS will of course work for any HTML that outputs a surrounding container (probably div) and an unordered list with floats, but you can find lots of tutorials on that around the web. From Agaric you get the straight Drupal and nothing but the Drupal (ok, not really).

If you put a menu in your footer, you're not going to see the code it directly in your page template. Instead, the footer section of your zen subtheme page.tpl.php might look like this:

Field templates are run before row templates, not vice versa

Field template are run before the row template.

This:
views-view-field--products--page-4--field-imagecrop-fid.tpl.php

is processed before this:
views-view-fields--products--page-4.tpl.php

The individual fields are run and then handed off to the row.

That is, the row template isn't run and given the chance to call and pass info into the field templates.

Syndicate content