| Summary | borken 2.1_to_2.2_sql_schema.php |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | rsalmon (at) mbpgroup (dot) com |
| Created | 05/21/2008 (6254 days ago) |
| Due | |
| Updated | 05/21/2008 (6254 days ago) |
| Assigned | |
| Resolved | 05/21/2008 (6254 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
/var/www/html/horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
on line 145
no reference to the $names variable.
variables at the top of the script ``$db_user``, ``$db_pass`` and
``$db_table``, but why not use the global configuration settings ?
we have no way of knowing which on the admin wants to update.
$db_user/$db_pass - Ideally, the user set up in the global
configuration settings shouldn't have the permissions to perform the
ALTER / CREATE statements, so these are used to provide the user
information that _does_ have these permissions.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ borken 2.1_to_2.2_sql_schema.php
Type ⇒ Bug
State ⇒ Unconfirmed
Notice: Undefined variable: names in
/var/www/html/horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
on line 145
PHP Warning: Invalid argument supplied for foreach() in
/var/www/html/horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
on line 145
the docs/UPGRADING file says to manually change the three
variables at the top of the script ``$db_user``, ``$db_pass`` and
``$db_table``, but why not use the global configuration settings ? I
removed the following lines to use the global conf and it connects
fine :
$config['username'] = $db_user;
$config['password'] = $db_pass;