| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
lifecycle, so any 4.7.x version can be updated to 6.x
|
| | |
|
| |
|
|
| |
policy dictates (and because some API changes make them faulty without further modifications)
|
| |
|
|
| |
time tresholds, so if cron stops running after some time, it also becomes an error, but cron not run yet is not an error on installation
|
| | |
|
| |
|
|
| |
and improve installation error messages checking for all requirements on the same screen, instead of putting the user through individual error screens
|
| |
|
|
| |
#191282 previously
|
| | |
|
| |
|
|
| |
foreach will not bail out on the explode(). Identified in upgrade testing.
|
| |
|
|
| |
was moved out to system.admin.inc, so we need to include that
|
| |
|
|
| |
blocks.
|
| |
|
|
| |
from search module
|
| |
|
|
| |
existing sites, and better handle the default behavior.
|
| |
|
|
| |
removed some trailing whitespace.)
|
| |
|
|
| |
the node_comment_statistics table
|
| | |
|
| |
|
|
| |
based block rehash code, replace it with simpler updates
|
| |
|
|
| |
update to avoid any privacy concerns
|
| |
|
|
| |
index on system table for better database performance
|
| |
|
|
| |
postgresql bugs with it
|
| | |
|
| |
|
|
| |
source code and messages printed
|
| | |
|
| |
|
|
| |
standards
|
| | |
|
| |
|
|
| |
'permissions' for usability reasons
|
| | |
|
| |
|
|
| |
update_fix_d6_requirements() to avoid warnings about the nonexistent table through the update process
|
| |
|
|
| |
.schema files into .install files to prevent mistakes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
db_change_field() and friends in MySQL
|
| |
|
|
| |
we need to check for its existance before updating it
|
| |
|
|
| |
Drupal 6 install and a Drupal 5 upgraded to Drupal 6
|
| |
|
|
| |
will not be deleted after an upgrade
|
| |
|
|
| |
special users
|
| | |
|
| | |
|
| |
|
|
| |
needs more thought and discussion, so postponed until at least Drupal 7
|
| |
|
|
| |
need to return an array
|
| | |
|
| |
|
|
| |
installer cannot be run on Drupal 6 on an upgraded site
|
| |
|
|
| |
actions.module is not turned on
|
| |
|
|
| |
so we can check whether it is wide open, and we have one place for settings
|
| |
|
|
| |
near flowless updates
|
| |
|
|
| |
external sources and only invoked once (note that you should do everything dynamic in the view op, not the load op)
|
| |
|
|
| |
cross-database compatibility (ie. better SQL parsing and altering options)
|
