[rt-users] Spreadsheet view displays more columns than in search

[Jesse Vincent]

On Thu, May 25, 2006 at 08:42:35AM -0500, Flynn, Timothy J wrote:
> Just an FYI, it was the double quote that was causing the issues with
> Excel and rows not showing properly.  I am using Excel 2003.  I ended up
> doing this:

Thanks! It sure looks like our escaping isn't up to snuff. We should likely be
using the relevant CPAN module. I've opened a ticket.

Jesse

> 
> $val =~ s/[^\032-\041\043-\176]/ /g;
> 
> -Tim
> 
> 
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Flynn,
> Timothy J
> Sent: Wednesday, May 24, 2006 9:55 AM
> To: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Spreadsheet view displays more columns than in
> search 
> 
> After reviewing my changes further I believe I came up with a better
> solution for escaping tabs.
> 
> In the file "rtroot"/share/html/Search/Elements/Results.tsv ....
> 
> 
> Instead of the line:
> $val =~ s/(\n|\r)//g;
> 
> And instead of the previous change I suggested:
> 
> $val =~ s/(\n|\r|\t)//g;
> 
> I am going to change it to this:
> 
> $val =~ s/\s/ /g;
> 
> My thinking is if the intent of a newline, tab, or other whitespace
> character was to separate data, then a single space would be more
> fitting than nothing at all.  Hope this helps someone else.  Also
> wouldn't be a bad idea to add this fix to future versions even if it
> doesn't match what I did above.  I would think having tabs escaped would
> be required for a tab delimited file to work properly.
> 
> -Tim
> 
> 
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Flynn,
> Timothy J
> Sent: Wednesday, May 24, 2006 9:16 AM
> To: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Spreadsheet view displays more columns than in
> search 
> 
>  
> Woops, just found this:
> 
>  $val =~ s/(\n|\r)//g;
> 
> Looks like I just need to change to:
> 
> $val =~ s/(\n|\r|\t)//g;
> 
> 
> -Tim
> 
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Flynn,
> Timothy J
> Sent: Wednesday, May 24, 2006 9:15 AM
> To: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Spreadsheet view displays more columns than in
> search 
> 
> I think I found the root of the problem.  It doesn't appear that tab
> characters or newlines are being escaped from the result set.  This
> would cause issues with the presentation in Excel.  I will add some
> coding to do this to the rows after I apply the patch.  I am surprised
> this never affected anyone before.
> 
> Thanks,
> -Tim
>  
> 
> -----Original Message-----
> From: Stephen Turner [mailto:sturner at MIT.EDU] 
> Sent: Wednesday, May 24, 2006 9:04 AM
> To: Flynn, Timothy J; rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Spreadsheet view displays more columns than in
> search 
> 
> At Tuesday 5/23/2006 04:50 PM, Flynn, Timothy J wrote:
> >Thanks Eric,  do you know why I'd be getting different results in
> >spreadsheet vs the web list?  On one report I am getting 14 tickets in
> >the web view and in the spreadsheet I am getting 11 and the data is
> >wrong..  FYI the web results are correct and the spreadsheet is not.
> Is
> >something not being escaped that is affecting the query?
> >
> >-Tim
> >
> 
> The mechanism use in searching for the web view is different from 
> that used in the full spreadsheet download.
> 
> That said, you should still see the same number of rows. When you get 
> 14 rows in the web view are you actually seeing 14 tickets in the 
> list, or is that number from the 'Found 14 tickets' message? It's 
> just possible that you only have permission to see 11 of the 14 rows
> returned.
> 
> Steve 
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> 
> 
> We're hiring! Come hack Perl for Best Practical:
> http://bestpractical.com/about/jobs.html
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> 
> 
> We're hiring! Come hack Perl for Best Practical:
> http://bestpractical.com/about/jobs.html
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> 
> 
> We're hiring! Come hack Perl for Best Practical:
> http://bestpractical.com/about/jobs.html
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
> 
> 
> We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
> 

--