Hi Carlos Gallego, I am able to install the CustomerUserImportExport pack from OPAR
http://opar.perl-services.de/bin/index.cgi/package/C/CA/CAPEIT/CustomerUserImportExport During above pack deployment, we are getting below error Oops! An Error occurred. Error Message: Sorry, can't install package, because package ImportExport v3.1.1 is required! Currently i m using OTRS 3.1.6. Help please... Thanks, SMPM On Tue, Jun 12, 2012 at 9:15 PM, sm pm <smpm1...@gmail.com> wrote: > Hi Carlos Gallego, > > Thanks for ur input on bulk data upload.. > > Regards, > SMPM > > > On Wed, Jun 13, 2012 at 3:10 AM, <otrs-requ...@otrs.org> wrote: > >> Send otrs mailing list submissions to >> otrs@otrs.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.otrs.org/cgi-bin/listinfo/otrs >> or, via email, send a message with subject or body 'help' to >> otrs-requ...@otrs.org >> >> You can reach the person managing the list at >> otrs-ow...@otrs.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of otrs digest..." >> >> >> Today's Topics: >> >> 1. Re: Add template list to OutputFilterTextURL after upgrade >> to OTRS 3.1.6 from 3.0.11 (Mark Dissington) >> 2. Re: 2.4.7 and 3.0.12 # or Ticket# (Neil Simpson) >> 3. Re: Bulk Customer Data upload in to OTRS Postgres DB >> (Carlos Andr?s Gallego Arboleda) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 12 Jun 2012 13:14:31 +0100 >> From: "Mark Dissington" <mark.dissing...@netmania-it.com> >> Subject: Re: [otrs] Add template list to OutputFilterTextURL after >> upgrade to OTRS 3.1.6 from 3.0.11 >> To: "User questions and discussions about OTRS." <otrs@otrs.org> >> Message-ID: <4fd740b80200002f00012...@h2g2.netmania-it.com> >> Content-Type: text/plain; charset=US-ASCII >> >> Thanks mg, >> >> Have applied the patch and the errors have stopped being logged. >> >> Thanks, >> Mark. >> >> >>> On 12/06/2012 at 07:40, Martin Gruner <martin.gru...@otrs.com> wrote: >> > Hi Mark, >> > >> > this is a bug, and it is already fixed: >> > http://bugs.otrs.org/show_bug.cgi?id=8543. >> > If you don't want to patch your system, you can ignore the messages for >> > now and upgrade to OTRS 3.1.7 when it is available. >> > >> > Regards, mg >> > >> > >> > Am 11.06.12 14:39, schrieb Mark Dissington: >> >> We've completed a successful upgrade to OTRS 3.1.6 but now have the >> error >> > below repeatedly logged to /var/log/messages >> >> >> >> Jun 11 11:32:40 zaphod OTRS-CGI-10[18479]: >> > [Notice][Kernel::Output::HTML::Layout::Ascii2Html] Please add a >> template list >> > to output filter Kernel::Output::HTML::OutputFilterTextURL to improve >> > performance. Use ALL if OutputFilter should modify all templates of the >> > system (deprecated). >> >> >> >> I've searched everywhere for how to do what is suggested, OTRS >> website, both >> > Dev and Admin manuals. But can't discover how to do what it suggests. >> The >> > closest I can find is Frontend::Output::FilterText###AAAURL in >> Framework -> >> > Core::Web in Sysconfig but doesn't seem to have anything to do with >> > templates. In fact, I don't even know what a Template in OTRS context >> is! >> >> >> >> Can someone point me in the right direction? >> >> >> >> TIA, >> >> Mark. >> >> >> Netmania IT Limited >> Registered in England No: 4039293 >> Registered Office: The Stables, Elmhurst Business Park, Elmhurst, >> Lichfield, Staffordshire, UK, WS13 8EX >> VAT Reg No: 765 6677 74 >> >> This electronic message contains information from Netmania IT Ltd which >> may be privileged and confidential. The information is intended to be for >> the use of the individual(s) or entity named above. If you are not the >> intended recipient, be aware that any disclosure, copying, distribution or >> use of the contents of this information is prohibited. If you have received >> this electronic message in error, please notify us by telephone or email >> (to the number or address above) immediately. >> >> Activity and use of the Netmania IT Ltd's email system is monitored to >> secure its effective operation and for other lawful business purposes. >> Communications using this system will also be monitored and may be recorded >> to secure effective operation and for other lawful business purposes. >> >> -- >> Scanned by iCritical. >> >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Tue, 12 Jun 2012 15:16:09 +0200 >> From: Neil Simpson <nad...@gmail.com> >> Subject: Re: [otrs] 2.4.7 and 3.0.12 # or Ticket# >> To: "User questions and discussions about OTRS." <otrs@otrs.org> >> Message-ID: >> < >> cad-pqjamyv1v0med6ycfx2j-hjvcpwhgvhqycylow6p0kuy...@mail.gmail.com> >> Content-Type: text/plain; charset="windows-1252" >> >> hi, >> >> think your looking for the ticket::hook option. Core::Ticket under >> sysconfig section. or it might be hard coded in your ~/Kernel/Config.pm >> file. >> >> mine is set to default which is Ticket#. >> >> Neil >> >> On Mon, Jun 11, 2012 at 9:48 PM, Andy Wodfer <wod...@gmail.com> wrote: >> >> > We've just upgraded from 2.4.7 to 3.0.12. I suspect something is wrong >> > somewhere since OTRS doesn't seem to put replies to tickets created and >> > answered on 2.4.7 into the correct ticket on 3.0.12. >> > >> > I see that in the subject field we used to have [#20120213 10000074] as >> a >> > ticket number while on 3.0.12 we have Ticket#2012061110000114. I suspect >> > this is causing some problems because instead of adding a reply to the >> > existing 2.4.7 generated ticket the system now creates a new ticket >> with a >> > new and old ticketnumber Ie: Ticket#2012061110000178 ? Re: >> > [#2012021310000074] Some title. >> > >> > Any idea of what I can do and where to change/fix this? Ideally I'd like >> > to see only [#20120213 10000074] like we had in 2.4.7. >> > >> > Thanks for any help! >> > >> > Best regards, >> > Andy >> > >> > --------------------------------------------------------------------- >> > 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 >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.otrs.org/pipermail/otrs/attachments/20120612/88bef384/attachment-0001.html >> > >> >> ------------------------------ >> >> Message: 3 >> Date: Tue, 12 Jun 2012 16:38:35 -0500 >> From: Carlos Andr?s Gallego Arboleda >> <carlos.gall...@itconsultores.com.co> >> Subject: Re: [otrs] Bulk Customer Data upload in to OTRS Postgres DB >> To: "User questions and discussions about OTRS." <otrs@otrs.org> >> Message-ID: >> <CAF4Nvh+4UBhXG=Z+yqj9a3vEVVmEgo4gh= >> kd+xcc_-pqdxd...@mail.gmail.com> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi, >> >> This package works for mysql DB, I never use on pgSQL you can try >> >> * >> >> http://opar.perl-services.de/bin/index.cgi/package/C/CA/CAPEIT/CustomerUserImportExport >> * >> >> >> Regards. >> >> Carlos Gallego >> >> 2012/6/11 sm pm <smpm1...@gmail.com> >> >> > Hi ALL, >> > >> > I would like to upload more than 500 customer data in to postgres db of >> > OTRS. I was tried with copy and pg_upload that have not been successful. >> > >> > Any help? >> > >> > >> > SMPM >> > >> > On Mon, Jun 11, 2012 at 5:30 PM, <otrs-requ...@otrs.org> wrote: >> > >> >> Send otrs mailing list submissions to >> >> otrs@otrs.org >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> http://lists.otrs.org/cgi-bin/listinfo/otrs >> >> or, via email, send a message with subject or body 'help' to >> >> otrs-requ...@otrs.org >> >> >> >> You can reach the person managing the list at >> >> otrs-ow...@otrs.org >> >> >> >> When replying, please edit your Subject line so it is more specific >> >> than "Re: Contents of otrs digest..." >> >> >> >> >> >> Today's Topics: >> >> >> >> 1. Error fetchting mails with IMAPTLS (Johannes Homuth) >> >> 2. change ticketing numbering (Neil Simpson) >> >> 3. Re: change ticketing numbering (Steven Carr) >> >> >> >> >> >> ---------------------------------------------------------------------- >> >> >> >> Message: 1 >> >> Date: Mon, 11 Jun 2012 10:47:26 +0200 >> >> From: Johannes Homuth <johannes.hom...@sourcepark.de> >> >> Subject: [otrs] Error fetchting mails with IMAPTLS >> >> To: otrs@otrs.org >> >> Message-ID: <4fd5b09e.4080...@sourcepark.de> >> >> Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" >> >> >> >> Hi List, >> >> >> >> I setup my OTRS System last week (Version 3.1.6) and everything works >> >> fine. But I get stuck on an "Error" which is displayed in the >> >> SystemProtocol. It always says that he can't process mail the Array >> >> would be empty. I mean, there is no mail every time the cron job will >> >> check, but that isn't an error I guess?!? Does anyone have the same >> >> problem and/or know how to fix that? >> >> >> >> >> >> Aktuelle Eintr?ge im Systemprotokoll >> >> >> >> Zeit Priorit?t Einrichtung Nachricht >> >> Mon Jun 11 10:22:02 2012 notice >> OTRS-otrs.PostMasterMailbox.pl-10 >> >> IMAPTLS: Fetched 1 email(s) from xxxx/xx.xx.xx.xx >> >> Mon Jun 11 10:22:02 2012 error >> OTRS-otrs.PostMasterMailbox.pl-10 >> >> IMAPTLS: Can't process mail, email no ARRAY(0x3322e88) is empty! >> >> >> >> >> >> -- >> >> ------------------------------------------------------- >> >> SOURCEPARK GmbH >> >> B.Sc. Johannes Homuth >> >> Hohenzollerndamm 150 >> >> 14199 Berlin >> >> >> >> Tel. : +49 (0) 30 / 39 80 68 30 >> >> Fax : +49 (0) 30 / 39 80 68 39 >> >> e-mail : johannes.hom...@sourcepark.de >> >> www : www.sourcepark.de >> >> ------------------------------------------------------ >> >> SOURCEPARK GmbH >> >> Sitz der Gesellschaft: Berlin / Amtsgericht Charlottenburg >> >> HRB 80254 >> >> Gesch?ftsf?hrung: Matthias Barmeier, Harald D?rr >> >> ------------------------------------------------------ >> >> >> >> Wichtiger Hinweis: Die vorgenannten Angaben werden jeder E-Mail >> >> automatisch hinzugef?gt >> >> und lassen keine R?ckschl?sse auf den Rechtscharakter der E-Mail zu. >> >> >> >> Diese Email kann vertrauliche und/oder rechtlich gesch?tzte >> Informationen >> >> enthalten. Wenn sie nicht der richtige Adressat sind oder diese E-Mail >> >> irr- >> >> t?mlich erhalten haben, informieren Sie bitte sofort diesen Absender >> und >> >> ver- >> >> nichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte >> >> Weitergabe dieser E-Mail ist nicht gestattet. >> >> >> >> >> >> >> >> -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: < >> >> >> http://lists.otrs.org/pipermail/otrs/attachments/20120611/13599123/attachment-0001.html >> >> > >> >> >> >> ------------------------------ >> >> >> >> Message: 2 >> >> Date: Mon, 11 Jun 2012 10:51:39 +0200 >> >> From: Neil Simpson <nad...@gmail.com> >> >> Subject: [otrs] change ticketing numbering >> >> To: "User questions and discussions about OTRS." <otrs@otrs.org> >> >> Message-ID: >> >> <CAD-pqJZuxNEHv4U-ngM5P=hB1YtkXB5X0t= >> >> r5fnkhk6zjo4...@mail.gmail.com> >> >> Content-Type: text/plain; charset="iso-8859-1" >> >> >> >> We have two ticket systems running currently and in certain cases they >> >> send >> >> mail to each other. The problem we have is that tickets are being >> merged >> >> together that shouldn't be due to the numbering in the subject. For >> >> example >> >> first otrs system had a ticket 1, then second otrs system sends a >> ticket >> >> to >> >> it also with ticket 1 number, now there merged but two totally >> different >> >> issues. >> >> >> >> Can we change the ticket numbering to make one system unique. so >> instead >> >> of >> >> Ticket#2012060110000065, maybe Ticket#2012060110000065a. then both >> systems >> >> could not get tickets confused with one another. >> >> >> >> thanks >> >> >> >> Neil >> >> -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: < >> >> >> http://lists.otrs.org/pipermail/otrs/attachments/20120611/4b0068b8/attachment-0001.html >> >> > >> >> >> >> ------------------------------ >> >> >> >> Message: 3 >> >> Date: Mon, 11 Jun 2012 10:12:02 +0100 >> >> From: Steven Carr <sjc...@gmail.com> >> >> Subject: Re: [otrs] change ticketing numbering >> >> To: "User questions and discussions about OTRS." <otrs@otrs.org> >> >> Message-ID: >> >> <CALMep04ArNes6U= >> >> yt8wbdqyu+ha+zsplbrsk-iffaxmrwkz...@mail.gmail.com> >> >> Content-Type: text/plain; charset="utf-8" >> >> >> >> You system IDs are the same (looks like they are both set to the >> default: >> >> 10), change the ID in Framework -> Core -> SystemID so that both >> systems >> >> are unique. >> >> >> >> Steve >> >> >> >> >> >> >> >> On 11 June 2012 09:51, Neil Simpson <nad...@gmail.com> wrote: >> >> >> >> > We have two ticket systems running currently and in certain cases >> they >> >> > send mail to each other. The problem we have is that tickets are >> being >> >> > merged together that shouldn't be due to the numbering in the >> subject. >> >> For >> >> > example first otrs system had a ticket 1, then second otrs system >> sends >> >> a >> >> > ticket to it also with ticket 1 number, now there merged but two >> totally >> >> > different issues. >> >> > >> >> > Can we change the ticket numbering to make one system unique. so >> instead >> >> > of Ticket#2012060110000065, maybe Ticket#2012060110000065a. then both >> >> > systems could not get tickets confused with one another. >> >> > >> >> > thanks >> >> > >> >> > Neil >> >> > >> >> > >> >> > >> >> > --------------------------------------------------------------------- >> >> > 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 >> >> > >> >> -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: < >> >> >> http://lists.otrs.org/pipermail/otrs/attachments/20120611/e504d66f/attachment-0001.html >> >> > >> >> >> >> ------------------------------ >> >> >> >> --------------------------------------------------------------------- >> >> 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 >> >> >> >> End of otrs Digest, Vol 45, Issue 15 >> >> ************************************ >> >> >> > >> > >> > --------------------------------------------------------------------- >> > 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 >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.otrs.org/pipermail/otrs/attachments/20120612/a3a5f39b/attachment.html >> > >> >> ------------------------------ >> >> --------------------------------------------------------------------- >> 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 >> >> End of otrs Digest, Vol 45, Issue 18 >> ************************************ >> > >
--------------------------------------------------------------------- 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
