Summary | MOTD not working after vhost changes |
Queue | Horde Base |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | ben (at) |
Requester | ben (at) |
Created | 10/02/2006 (6877 days ago) |
Due | |
Updated | 10/03/2006 (6876 days ago) |
Assigned | 10/03/2006 (6876 days ago) |
Resolved | 10/03/2006 (6876 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
Assigned to ben
State ⇒ Assigned
New Attachment: Horde.php.patch
like this solution much better than my original.
opportunity to override the default motd.php with a vhost-specific
motd.php, which completely negates the reason for using
Horde::loadConfiguration() in the first place.
and to echo the results of the Horde::loadConfiguration() call like
so:
the MOTD files. I'd rather suggest another parameter to
loadConfiguration() whether output from the configuration file is
considered an error or is allowed.
from motd.php.
State ⇒ Feedback
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Queue ⇒ Horde Base
Summary ⇒ MOTD not working after vhost changes
Type ⇒ Bug
changes. The problem is that motd.php doesn't actually set a
variable, so Horde::loadConfiguration() interprets what it gets from
motd.php as an error.
My proposed solution is to make motd.php set a variable ($motd ?), and
to echo the results of the Horde::loadConfiguration() call like so:
<?php echo Horde::loadConfiguration('motd.php', 'motd') ?>
If that seems reasonable to others, I will commit it. Otherwise, we
need to discuss an alternative. (I miss my login screen
customizations via motd.php)