RE: [help-GIFT] Error in indexing: Attributes[1] too long

[Chapman, Brian J.]

Thanks, It appears that this is just some debugging information and not an 
actual limit on the string length.

What I am trying to figure out is why I am only getting a few random images 
displayed from the Viper php script. The gift server provides random 10 images 
as requested, however, the viper script displays anywhere from 0 to 10 images.

I found that some of the paths I am indexing have the "&" character in them. I 
know it is bad practice to use the "&" in the path, but this is an existing 
file system with users who do not know better. 

Some digging into the code showed that spaces are converted into their hex 
equivalent in gift-add-collection.pl:

$i=~s[ ][%20]g;

Just adding another line(s):
          $i=~s[\&][%26]g;
          $i=~s[\#][%23]g;

should protect against the "&" (and "#" for URL problems) in the filename from 
causing xml parsing problems.

Brian.

> -----Original Message-----
> From: address@hidden [mailto:help-gift-
> address@hidden On Behalf Of Wolfgang Müller
> Sent: Thursday, May 13, 2004 10:58 AM
> To: Chapman, Brian J.; address@hidden
> Subject: Re: [help-GIFT] Error in indexing: Attributes[1] too long
> 
> > CAttributeList.cc:45:lAttributes[1] too long:[
> > http://baxter.vaengr.com/gift/thumbnails/marketing/Proposals/2003/P03-12
> >
> 1%20Carollo%20City%20of%20Modesto%20Masterplan%20Flow%20Monitoring/V
> &A's
> >
> %20Modesto%20Proposal%20Page%202%20of%202_thumbnail_jpg.jpg]ENDOF
> STRING
> 
> Well, as far as I can remember, I put that one in, when I had strange
> multithreading problems back in 2001. These multithreading problems clobbered
> strings in a weird fashion. You noticed that, when strings became all of a
> sudden VERY big. So I wanted to have the assertion that things barf when a
> BIG string really comes from my side and not from a programming error.
> 
> It looks to me that these errors were due to some misunderstanding between
> previous versions of GCC and myself ;-) . I guess that has been fixed in the
> meantime (GCC and its c++ standard library behaves now as I hoped it to
> behave back then).
> 
> If I do not remember things wrongly, you should be safe either removing the
> >200 comparisons in CAttributeList or setting the value up to regions that
> don't hurt at all.
> 
> Cheers,
> Wolfgang
> 
> 
> 
> _______________________________________________
> help-GIFT mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/help-gift


--------------------------------------------------------------------------------
Due to the potential that information exchanged by electronic 
media can deteriorate, be damaged, lost or modified unintentionally 
or otherwise, use of this electronic data by anyone other than 
V&A Consulting Engineers, Inc. shall be at the sole risk of such user 
and without liability or legal exposure to V&A Consulting Engineers, Inc. 
The recipient is responsible for verifying the accuracy of data against 
governing hard copy documentation.  Recipient assumes all risks in the 
changing or modification of data and revisions or updating of hard copy 
documents.