I've fixed the issue by: 1) removing both ZZZ*.pm modules 2) Running otrs.RebuildConfig.pl from the console (which recreates ZZZAAuto.pm) 3) Reimporting my Sysconfig backup from the UI (which recreates ZZZAAuto.pm)
The front end now loads without error. Apologies for the spam. Hugh On Tue, Aug 24, 2010 at 6:17 AM, Hugh Kelley <[email protected]> wrote: > Thank you, Martin. > > You have shown me the issue. I "carried ahead" my ZZZAuto.pm file to Beta2 > so that I would not have to recreate free text settings. I see the issue > below in that file. What is the supported way to port these settings (the > desirable free text), but leave the others behind? > > 'Core.Form.Validate.js', > 'Core.UI.Dialog.js', > > > I can confirm the following that all of the following are fine. > > - the ZZZAAuto.pm file is recreated each time I run otrs.RebuildConfig.pl > - the $Self->{'Loader::Agent::CommonJS'}->{'000-Framework'} sequence of > files appears to be correct > > 'Core.UI.Dialog.js', > 'Core.UI.ActionRow.js', > 'Core.UI.Popup.js', > 'Core.Form.js', > 'Core.Form.ErrorTooltips.js', > 'Core.Form.Validate.js', > > > > On Tue, Aug 24, 2010 at 5:37 AM, Martin Gruner <[email protected]>wrote: > >> Hi Hugh, >> >> that indicates that the Perl configuration Cache ZZZAAuto.pm, which is >> generated by otrs.RebuildConfig.pl, is out of date. Can you verify that >> ZZZAAuto.pm has the values in correct order and that they do not appear in >> ZZZAuto.pm? >> >> Regards, mg >> >> Am 23.08.10 23:16, schrieb Hugh Kelley: >> >> I know very little about the framework process so I may be on the wrong >> track here. However, one thing I have noticed is this: >> >> Framework.xml lists the scripts in the following order: >> >> <Item>Core.UI.RichTextEditor.js</Item> >> -->> <Item>Core.UI.Dialog.js</Item> <<-- >> <Item>Core.UI.ActionRow.js</Item> >> <Item>Core.UI.Popup.js</Item> >> <Item>Core.Form.js</Item> >> <Item>Core.Form.ErrorTooltips.js</Item> >> -->> <Item>Core.Form.Validate.js</Item> <<-- >> <Item>Core.App.js</Item> >> >> A trace of the UI request shows them returned in a different order, which >> would explain why Core.Form.Validate can't verify that Core.UI.Dialog has >> been loaded. >> >> >> >> >> >> URL >> >> >> >> >> >> >> >> >> >> /otrs-web/js/Core.Form.js >> >> >> >> >> >> >> >> >> >> /otrs-web/js/Core.Form.ErrorTooltips.js >> >> >> >> >> >> >> >> >> >> /otrs-web/js/Core.Form.Validate.js >> >> >> >> >> >> >> >> >> >> /otrs-web/js/Core.UI.Dialog.js >> >> >> >> >> >> >> >> Hugh >> >> >> On Mon, Aug 23, 2010 at 3:23 PM, Hugh Kelley <[email protected]>wrote: >> >>> Thanks for the suggestion. Per the Upgrade guide, I have run both that >>> and DeleteCache before reporting the issue. Apologies for not mentioning it >>> in the original post. >>> >>> C:\Temp>perl \OTRS\otrs-3.0.0\bin\otrs.RebuildConfig.pl >>> otrs.RebuildConfig.pl <Revision 1.14> - OTRS rebuild default config >>> Copyright (C) 2001-2010 OTRS AG, http://otrs.org/ >>> >>> C:\Temp>perl \OTRS\otrs-3.0.0\bin\otrs.DeleteCache.pl >>> >>> Hugh >>> >>> >>> >>> On Mon, Aug 23, 2010 at 3:18 PM, Michiel Beijen <[email protected] >>> > wrote: >>> >>>> Hi Hugh, >>>> >>>> Please run bin/otrs.RebuildConfig.pl and try again. >>>> >>>> Michiel Beijen >>>> Senior Consultant >>>> >>>> OTRS BV >>>> Schipholweg 103 >>>> 2316 XC Leiden >>>> The Netherlands >>>> >>>> T: +31 71 8200 255 >>>> F: +31 71 8200 254 >>>> I: http://www.otrs.com >>>> >>>> OTRS brings true mobility to the Help Desk: The OTRS iPhone App free >>>> download http://www.otrs.com/en/products/iphone-app/ >>>> >>>> >>>> On Mon, Aug 23, 2010 at 8:31 PM, Hugh Kelley <[email protected]> >>>> wrote: >>>> > I have started the upgrade process for my Beta 1 system (built >>>> originally on >>>> > that version). >>>> > >>>> > When I access the app I now get this prompt on each page: >>>> > >>>> > Namespace Core.Form.Validation could not be initialized, because >>>> > Core.UI.Dialog could not be found. >>>> > >>>> > I don't see any hints in the log files. Has anyone else experienced >>>> this? >>>> > >>>> > Hugh >>>> > >>>> > >>>> > >>>> > >>>> --------------------------------------------------------------------- >>>> > 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 >> >> >> -- >> Martin Gruner >> Developer R&D >> >> OTRS AG >> Europaring 4 >> 94315 Straubing >> >> T: +49 (0)6172 681988 0 >> F: +49 (0)9421 56818 18 >> I: www.otrs.com/ >> >> Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: >> DE256610065 >> Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann >> >> OTRS mobilisiert Ihren Help Desk. Die OTRS iPhone App zum freien Download: >> http://www.otrs.com/de/produkte/iphone-app/ >> >> >> --------------------------------------------------------------------- >> 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
