| Commit message (Collapse) | Author | Age |
|
|
|
| |
compliance with standards.
|
| |
|
| |
|
|
|
|
| |
all tables.
|
| |
|
|
|
|
| |
Senpai: usability improvement: allow more users to see the node admin page.
|
|
|
|
| |
arrays and forms (e.g. 'Operations') alterable.
|
|
|
|
| |
filter usability and accessibility.
|
| |
|
|
|
|
| |
validates that there were rows selected. (with tests)
|
| |
|
| |
|
| |
|
|
|
|
| |
take a single argument. Code clean-up and performance improvement. Woot.
|
|
|
|
| |
admin users and admin nodes.
|
|
|
|
|
|
| |
before a form builder function, to facilitate common form elements. Clean-up
from form_builder changes from CTools patch. Has nice side-benefit of making
all form functions' signatures consistent.
|
|
|
|
| |
admin role after installation.
|
|
|
|
| |
numbers.
|
|
|
|
| |
administration pages.
|
| |
|
|
|
|
| |
local actions.
|
|
|
|
| |
Convert 'class' attribute to use an array, not a string.
|
|
|
|
| |
Content item, which would immediatey lead to the "Find content" screen. The current Drupal 7 code is almost there, but still has an RSS settings item blocking the implementation of this by default and aggregator and book also add subitems.
|
| |
|
|
|
|
|
|
| |
admin overview page.
We can work on creating a generic framework for adding tasks later, if that is deemed necessary. I'm still not sure it is, and in the mean time, this patch addresses an important usability issue.
|
| |
|
| |
|
|
|
|
| |
prevent errors upon enabling modules.
|
|
|
|
| |
settings' admin screen and relocate options.
|
|
|
|
| |
node type data.
|
| |
|
|
|
|
| |
session handling.
|
|
|
|
| |
nominalizations from Docblocks.
|
| |
|
| |
|
|
|
|
| |
deletion of lots of nodes.
|
| |
|
| |
|
|
|
|
| |
database abstraction layer. Yay.
|
| |
|
|
|
|
| |
administration screen consistent with other screens.
|
| |
|
|
|
|
| |
user/user_role for consistency.
|
|
|
|
| |
clearfix, which is the lingo that designers use for it.
|
| |
|
|
|
|
| |
unless something has been written to . This is an important performance improvements -- as long as you use modules that use carefully. It might be good to report some analytics about this in the performance settings page so administrators can see if there is a 'broken' module.
|
|
|
|
| |
table namespace.
|
| |
|
|
|
|
| |
taxonomy_term_data.
|
|
|
|
| |
system_settings_form().
|