[ic] wacky widget (Modified Subject: Additional Image Fields: Values Shifting)

Mike Heins mike at perusion.com
Wed Nov 5 12:14:36 EST 2003


Quoting Gary Norton (gnorton at broadgap.com):
> 
> > Everything shows up as desired but....
> > If I go back and make any changes in the image fields the thumbs shift to
> > the first empty spot in the image fields but only in the new fields I've
> > created.
> > thumb_1 data moves to image_1 data field if image_1 was empty, otherwise
> > it
> > would move to the image_2 field. Am I witnessing Interchange string theory
> > or is my problem obvious to someone out there?
> > Advice appreciated.
> > 
> 
> This is identical to a message I posted last week. 
> 
> I have worked around this problem by adding a very small (i.e. 1px)
> transparent image as a placeholder in these fields. It seems to be a viable
> work-around.
> 
> I was working with Mike Heins on some other consulting projects and
> mentioned this particular issue to him. He suggested that it might be a bug
> in the code related to multi-part file uploads. I believe ge added it to the
> list of bugs/things-to-check-out.
> 
> Beyond that, I did not get any responses or come up with other work-arounds.
> 
> I know that the dev team is very busy working on the upcoming 5.0 release
> and are actively fixing bugs. However, I don't know the priority of
> something like this in the grand scheme of things.
> 
> Depending on its importance and/or your skills you might be able to address
> it yourself, or seek consulting services of one of the devs.
> 
> Good luck and let me know if you find a better work-around or fix. This
> drove me nuts for about a week 8).
> 

It is a simple patch to Data.pm:

Index: Data.pm
===================================================================
RCS file: /var/cvs/interchange/lib/Vend/Data.pm,v
retrieving revision 2.31
retrieving revision 2.32
diff -r2.31 -r2.32
3c3
< # $Id: Data.pm,v 2.31 2003/09/09 23:45:32 racke Exp $
---
> # $Id: Data.pm,v 2.32 2003/11/05 17:12:57 mheins Exp $
307c307
< 			or die "No absolute file names like '$fn' allowed.\n";
---
> 			or die ::errmsg("No absolute file names like '%s' allowed.\n", $fn);
1854,1855c1854,1855
<     my @file_paths = split /[\s\0,]+/, $CGI::values{mv_data_file_path};
<     my @file_oldfiles = split /[\s\0,]+/, $CGI::values{mv_data_file_oldfile};
---
>     my @file_paths = split /\0/, $CGI::values{mv_data_file_path};
>     my @file_oldfiles = split /\0/, $CGI::values{mv_data_file_oldfile};


It is committed to CVS.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.513.523.7621      <mike at perusion.com>

"Even if you're on the right track, you'll get run over if you just
sit there." -- Will Rogers


More information about the interchange-users mailing list