FileUploadAll Bug... eta? (there are fixes available in the community, but not the build?

Can I highlight a couple of really simple bugs that need fixing in current
builds.

Why aren’t bugs like this fixed in Railo 4.(anything)? (really I’d like to
know why in the past fixing key features have major bugs)

I’m seeing these in Lucee 4.5.1.003 final

Chris–

As reported here (with custom build with fixes) by Jetendo CMS team (not
related to me):

Railo Custom Build For v4.2.1.002

Released: Jul 13, 2014

Download: Railo Custom Build For v4.2.1.002
https://www.jetendo.com/zupload/user/railo-custom-build/4.2.1.102.rc

Release Notes

This custom build will fix the following 2 bugs in Railo before there is an
official release:

  1. HTML 5 multiple file upload, i.e.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-2468

  2. Fixed email header to be standards compliant for embedded images in an
    html email. It allows images to be inline instead of attachments in
    Thunderbird and perhaps other email clients that depend on
    “multipart/related” instead of the Java default “multipart/mixed” header.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-661

Hi Christopher,

I have added a ticket to the Lucee BitBucket issues (
Log in with Atlassian account) for the first one of these:

and included Bruce’s suggested fix.

I’m not aware of the other issue, so if that needs migrating across as well
then it would be worth you adding it to the issue tracker.

Also, remember Lucee is open source and community fixes are welcomed, so if
you or someone you know can do the fix and issue a pull request I’m sure
Micha would very much welcome that.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - MemberOn 22 February 2015 at 15:31, Christopher Dawes <@Christopher_Dawes> wrote:

Can I highlight a couple of really simple bugs that need fixing in current
builds.

Why aren’t bugs like this fixed in Railo 4.(anything)? (really I’d like to
know why in the past fixing key features have major bugs)

I’m seeing these in Lucee 4.5.1.003 final

Chris

As reported here (with custom build with fixes) by Jetendo CMS team (not
related to me):

Railo Custom Build For v4.2.1.002

Released: Jul 13, 2014

Download: Railo Custom Build For v4.2.1.002
https://www.jetendo.com/zupload/user/railo-custom-build/4.2.1.102.rc

Release Notes

This custom build will fix the following 2 bugs in Railo before there is
an official release:

  1. HTML 5 multiple file upload, i.e.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-2468

  2. Fixed email header to be standards compliant for embedded images in an
    html email. It allows images to be inline instead of attachments in
    Thunderbird and perhaps other email clients that depend on
    “multipart/related” instead of the Java default “multipart/mixed” header.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-661


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/b37d81da-4999-484e-a0fd-6d784b813f32%40googlegroups.com
https://groups.google.com/d/msgid/lucee/b37d81da-4999-484e-a0fd-6d784b813f32%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Cheers, appreciate that. I think the second is fixed according to the
tracker…

Appreciate the fast response.On Monday, 23 February 2015 19:10:19 UTC+11, Andrew Dixon wrote:

Hi Christopher,

I have added a ticket to the Lucee BitBucket issues (
Log in with Atlassian account) for the first one of these:

Log in with Atlassian account

and included Bruce’s suggested fix.

I’m not aware of the other issue, so if that needs migrating across as
well then it would be worth you adding it to the issue tracker.

Also, remember Lucee is open source and community fixes are welcomed, so
if you or someone you know can do the fix and issue a pull request I’m sure
Micha would very much welcome that.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member

On 22 February 2015 at 15:31, Christopher Dawes <daw...@gmail.com <javascript:>> wrote:

Can I highlight a couple of really simple bugs that need fixing in
current builds.

Why aren’t bugs like this fixed in Railo 4.(anything)? (really I’d like
to know why in the past fixing key features have major bugs)

I’m seeing these in Lucee 4.5.1.003 final

Chris

As reported here (with custom build with fixes) by Jetendo CMS team (not
related to me):

Railo Custom Build For v4.2.1.002

Released: Jul 13, 2014

Download: Railo Custom Build For v4.2.1.002
https://www.jetendo.com/zupload/user/railo-custom-build/4.2.1.102.rc

Release Notes

This custom build will fix the following 2 bugs in Railo before there is
an official release:

  1. HTML 5 multiple file upload, i.e.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-2468

  2. Fixed email header to be standards compliant for embedded images in an
    html email. It allows images to be inline instead of attachments in
    Thunderbird and perhaps other email clients that depend on
    “multipart/related” instead of the Java default “multipart/mixed” header.
    Railo Jira Bug Report: https://issues.jboss.org/browse/RAILO-661


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+un...@googlegroups.com <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/b37d81da-4999-484e-a0fd-6d784b813f32%40googlegroups.com
https://groups.google.com/d/msgid/lucee/b37d81da-4999-484e-a0fd-6d784b813f32%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.