Great! That would do the trick!

2015-01-08 0:09 GMT+01:00 Gerald Young <cryth...@gmail.com>:

> if you change the accept *code* it *activates* again.
>
> On Wed, Jan 7, 2015 at 3:02 PM, Lars Jørgensen <ljo...@gmail.com> wrote:
>
>> Thank you for your quick reply. I tried to fiddle with the
>> CustomerAccept, but once a customer has accepted, it never seems to appear
>> again. I would like to make it appear whenever I activate it.
>>
>> 2015-01-07 17:08 GMT+01:00 Gerald Young <cryth...@gmail.com>:
>>
>>> Sorry. Missed the inference for this. :( OK, now you know how to tell
>>> people OTRS is down :)
>>>
>>> *A* way to provide a notification is to use the CustomerAccept.dtl file
>>> within Framework->Frontend::Customer (There's an analogous situation for
>>> Agents with a video https://www.youtube.com/watch?v=NoJe_6rvVpY).
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jan 7, 2015 at 10:58 AM, Gerald Young <cryth...@gmail.com>
>>> wrote:
>>>
>>>> Create a "We're down" web page and set the LoginURL to that page. When
>>>> you're done, go back and clear the checkbox for:
>>>>
>>>> SysConfig:
>>>> Edit Config Settings in Framework -> Frontend::Customer
>>>> CustomerPanelLoginURL
>>>> Edit Config Settings in Framework -> Frontend::Agent
>>>> LoginURL
>>>>
>>>>
>>>>
>>>> On Wed, Jan 7, 2015 at 9:23 AM, Lars Jørgensen <ljo...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We would like to be able to give customers a status message if some
>>>>> major downtime is ocurring. When they login to OTRS it would be nice to 
>>>>> let
>>>>> them know that "file server 1 is down, you don't need to create tickets to
>>>>> that effect". Also it would be nice is this message is displayed to users
>>>>> already logged in.
>>>>>
>>>>> I've spent some time trying to get MOTD to display via
>>>>> CustomerLogin.tt but my skills are obviously not up to the task.
>>>>>
>>>>> Is there an easy way to do this? Preferably the contents of the
>>>>> message should not come from a file on the filesystem but somehow be
>>>>> configurable from within OTRS. That last part is clearly in the
>>>>> nice-to-have category, though, and not a necessity.
>>>>>
>>>>>
>>>>> --
>>>>> Lars
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>>>>> Archive: http://lists.otrs.org/pipermail/otrs
>>>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>>> Archive: http://lists.otrs.org/pipermail/otrs
>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>>>
>>
>>
>>
>> --
>> Lars
>>
>> ---------------------------------------------------------------------
>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>> Archive: http://lists.otrs.org/pipermail/otrs
>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>>
>
>
> ---------------------------------------------------------------------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>



-- 
Lars
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Reply via email to