So run perms against the otrs-x.x.x folder.
On Jan 31, 2013 11:44 PM, "Rainer Bendig" wrote:
> Hm upgrade file says:
>
> --- snip ---8<---
> 5) Install the new release (tar or RPM)
>
>
>With the tarball:
>
> shell> cd /opt
> shell> tar -xzf otrs
Hm upgrade file says:
--- snip ---8<---
5) Install the new release (tar or RPM)
With the tarball:
shell> cd /opt
shell> tar -xzf otrs-x.x.x.tar.gz
shell> ln -s otrs-x.x.x otrs
--- /snip --->8--
maybe this needs a patch ;(
Am 31.01.2013 20:
make sure /opt/otrs isn't a symlink. Permissions may not apply correctly if
it is.
On Thu, Jan 31, 2013 at 1:04 PM, Bianchi Massimo <
massimo.bian...@nposistemi.it> wrote:
> Hi all,
>
> I think that I missed some step…
>
> ** **
>
> Tryng to modify ANY item in sysconfig leads to an erro
Hi all,
I think that I missed some step...
Tryng to modify ANY item in sysconfig leads to an error:
Error Message: Can't write ConfigItem!
.
You can Send a bugreport or go back to the previous page.
Error Details
Backend ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Thu Jan 31 18:59:40
2013
I am attempting to run the DBUpgrade-to-3.1.pl script and get as far as step 5.
After it finishes going through our rather large database (10+) everything
after step 5 fails. I saw another post where someone had the same error as me,
and they mentioned increasing their mysql timeout. Anyone
Hi all,
I did a test-upgrade from 3.1.11 to 3.2
It looks great but I have two problems and one question:
BLOCKING:
1) missing "new ticket" in customer interface
Apparently I have not the "new ticket" in customer web interface - quite
strange !
I tested it with standard theme
MINOR
2) searc
There's also the possibility to either save again from Sysconfig after
removal (Ticket.xml will help repopulate) or rebuildconfig from scripts.
You may also want to be sure that OTRS has permissions within the web user
(www-data or otrs) to write to the ZZZ files.
On Thu, Jan 31, 2013 at 12:05 PM
Hello
Yes it is OK. That's the way you return them to the default value. If you
want to find out how to write them back, you can take a look at them at ZZZA
*A*uto.pm and copy them back yo ZZZAuto.pm
Leonardo Certuche
www.itconsultores.com.co
Medellín, Colombia
On 31 January 2013 11:54, Steve C
Hello,
I found that if I remove them from Config/Files/ZZZAuto.pm file they show up
in sysconfig with their default values. Is it OK remove them from the ZZZAuto.pm
file?
On 01/31/2013 11:36 AM, Gerald Young wrote:
Config/Files/Ticket.xml:
Config/Files/Ticket.xml:
Config/Files/ZZZAAuto.
Config/Files/Ticket.xml:
Config/Files/Ticket.xml:
Config/Files/ZZZAAuto.pm:$Self->{'Ticket::Frontend::CustomerTicketZoom'}->{'StateDefault'}
= 'open';
Config/Files/ZZZAAuto.pm:$Self->{'Ticket::Frontend::CustomerTicketMessage'}->{'StateDefault'}
= 'new';
Ticket.xml:
Defines t
I only see them change
On 01/31/2013 10:32 AM, Renee B wrote:
Please ensure that those data aren't configured in Kernel/Config.pm
Have you changed the XML file (Kernel/Config/Ticket.xml)?
On 31.01.2013 16:26, Steve Clark wrote:
Hello List,
These two values have been altered from the default a
Please ensure that those data aren't configured in Kernel/Config.pm
Have you changed the XML file (Kernel/Config/Ticket.xml)?
On 31.01.2013 16:26, Steve Clark wrote:
> Hello List,
>
> These two values have been altered from the default and I can't seem to
> get them set back to the original value.
Hello List,
These two values have been altered from the default and I can't seem to
get them set back to the original value.
When I click the "reset" icon next to the item, otrs acts like it is doing
something but when it
comes back they still have the altered value.
What am I missing?
Ticket
13 matches
Mail list logo
