> > When an attached image name contains a space in its filename and attachment
> > display is enabled elog builds a wrong url to the image:
> >
> > http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
> >
> > instead of the correct one:
> >
> > http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg
>
> This is on purpose. If you want to save an attachment locally and right click on
> the attachment, and select "Save link as..." in your browser, then the default
> file name is taken from the link. If your original file namw was "peeling
> 002.jpg", then you want again the same name, and not "050309_170709_peeling
> 002.jpg, because you would have to delete the date/time part of the file name
> each time which would be annoying. That's why I have chosen to put an artificial
> "/" between the date/time and the original file name. On the elog side, it's
> converted correctly back to the file name.
>
yes I notice this after posting :-) sorry
> The problem with blanks in attachment names I could not reproduce. See this
> post, which contains an attachment with a blank in it. As you can see, this does
> not crash the server.
Ok I can confirm this.
The problem arises, for me, when upgrading to the new version of elog having yes
some old entries with attached filenames containing spaces and/or uppercase extensions.
It seems that uploading files with spaces in the name *now* works well... so the
problem should be somewhere in the handling of existing attachments, not rised when
the attachment is uploaded with the current version of elog ... it's quite strange |