I got it!

After doing a rollback to the backup of this afternoon and re-doing the
migration, including

>
http://blog.otrs.org/2013/02/20/about-otrs-mysql-myisam-and-innodb-storage-engines/#more-1198

I got an upgrade that seems to be valid. I have now Dynmic Fields in the
corresponding Admin section.

Of course I have lost 5 hours of tickets, but that's okay as we don't
have a heavily used ticket system (5-10 new tickets a day).

Puh... what a mess...   ;-)

Regards
Karsten

On 03/20/2013 06:56 PM, Karsten Becker wrote:
> Hi,
> 
> in fact we are using a non-heavily-customized installation of OTRS for
> nearby 2 years now. I have absolutely no idea what DynamicFields are,
> compared to FreeTextFields (which existence is also new to me).
> 
> In the Admin -> DynamicFields there's nothing in our installation - no
> DynamicFields. I'm sure to have followed all the upgrade guides during
> our way upgrading through the versions.
> 
> If I read
>> http://doc.otrs.org/3.2/de/html/dynamicfields-configuration.html
> I'm getting sick, as I absolutely have no clue what to do, why to do and
> how to do.
> 
> What's also a mystery to me is the fact that everything seems to work,
> even without the DynamicFields obviously needed. The only thing is that
> damned error message.
> 
> If I select under Admin -> DynamicFields -> Article a "Text" field and
> fill in some values, I get an error "Error Message: Could not create the
> new field". So this seems not to work either.
> 
> Is there any way to "convert" whatever should be converted in an
> automated way?
> 
> Regards
> Karsten
> 
> 
> On 03/20/2013 06:06 PM, Gerald Young wrote:
>> Where can you disable the fields? In the Admin,Dynamic Fields.
>>
>>
>> On Wed, Mar 20, 2013 at 1:01 PM, Karsten Becker
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>>     Thanks for your answer... but I don't understand anything.  :-D
>>
>>     Where can I do that?
>>
>>     Sorry Karsten
>>
>>     On 03/20/2013 04:40 PM, Gerald Young wrote:
>>     > Relevant code:
>>     >
>>     >     # create a dynamic field config lookup table
>>     >     for my $DynamicFieldConfig ( @{ $Self->{DynamicField} } ) {
>>     >
>>     >         $Self->{DynamicFieldConfigLookup}->{
>>     $DynamicFieldConfig->{Name}
>>     > } = $DynamicFieldConfig;
>>     >
>>     >     }
>>     >
>>     >
>>     >     return $Self;
>>     >
>>     > What it means:
>>     >
>>     > Your conversion didn't work perfectly as your TicketFreeTextFields
>>     didn't change to DynamicFields well.
>>     >
>>     >
>>     > What you can do:
>>     >
>>     > disable TicketFreeTextFields and build them as Dynamic Fields.
>>     >
>>     >
>>     >
>>     > On Wed, Mar 20, 2013 at 11:26 AM, Karsten Becker
>>     > <[email protected] <mailto:[email protected]>
>>     <mailto:[email protected]
>>     <mailto:[email protected]>>> wrote:
>>     >
>>     >     Hi folks!
>>     >
>>     >     I upgraded to OTRS 3.2.3 from 3.1.6 two hours ago and have a
>>     problem.
>>     >
>>     >     When writing a test email to my helpdesk, I get the following
>>     error
>>     >     emails from OTRS to our management email address.
>>     >
>>     >     Subject:
>>     >     > Cron <otrs@XXX01> $HOME/bin/otrs.PostMasterMailbox.pl
>>     <http://otrs.PostMasterMailbox.pl>
>>     >     <http://otrs.PostMasterMailbox.pl> >> /dev/null
>>     >
>>     >     In the body, I have multiple lines saying:
>>     >     > Use of uninitialized value in hash element at
>>     >    
>>     /opt/otrs-3.2.3/Kernel/System/Ticket/Event/NotificationEvent.pm line 53.
>>     >
>>     >     If I take a look in my Apache logs, I find corresponding
>>     entries which
>>     >     look like:
>>     >     > [Wed Mar 20 16:11:35 2013] [error] [client 192.168.AAA.BBB] [Wed
>>     >     Mar 20 16:11:35 2013] index.pl <http://index.pl>
>>     <http://index.pl>: Use of
>>     >     uninitialized value in hash element at
>>     >     /opt/otrs-3.2.3/bin/cgi-bin/../../Kern
>>     >     > el/System/Ticket/Event/NotificationEvent.pm line 53., referer:
>>     >    
>>     https://XXX.YYY.local/otrs/index.pl?Action=AgentTicketClose;TicketID=8281
>>     >
>>     >     The whole system seems to behave normally. It sends out
>>     emails, even the
>>     >     automatic replies for new incoming requests. But, for whatever
>>     reason,
>>     >     it produces these error emails.
>>     >
>>     >     Has somebody an idea how to track down the problem to get rid
>>     of it?
>>     >
>>     >     Regards
>>     >     Karsten
>>     >
>>     >    
>>     ---------------------------------------------------------------------
>>     >     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
>>     >
>>
>>
>>     ---------------------------------------------------------------------
>>     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
>>
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 

<<attachment: karsten_becker.vcf>>

---------------------------------------------------------------------
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