david at kineticode
Oct 15, 2009, 12:06 PM
Post #2 of 8
(168 views)
Permalink
|
On Oct 15, 2009, at 7:56 AM, Aaron Fuleki wrote:
> First, I uploaded an image named "freddie on pony.JPG" to
> bricolage. On preview or publish, everything is lowercased as per
> the output channel settings, but the spaces are URL encoded in the
> actual filename written to disk ("freddie%20on%20pony.jpg"), which
> makes Apache 404 because somewhere in the request process the %20's
> are decoded back to whitespace. The only way Apache will actually
> serve the file is to double-escape ("freddie%2520on%2520pony.jpg").
> Is this a bug, or do we need to change all templates to double URI
> escape everything? I'm hoping the former...
It's a bug.
> Another thing: expire jobs for media that were created and previewed/
> published pre-1.10.7 are failing if the filenames are now different
> with the new behavior. Sometimes the files were actually removed
> from the destination, sometimes not. The job failure notes just say
> this:
> -------------------------------------------------------
> No parameters passed to ANY()
> [/usr/local/bricolage/lib/Bric/Util/DBI.pm:323]
> [/usr/local/bricolage/lib/Bric/Util/Burner.pm:1311]
> [/usr/local/bricolage/lib/Bric/Util/Job/Pub.pm:201]
> [/usr/local/bricolage/lib/Bric/Util/Job.pm:1889]
> [/usr/local/bricolage/bin/bric_queued:244]
> [/usr/local/bricolage/bin/bric_queued:213]
> -------------------------------------------------------
>
> I've poked around the media_instance table a bit, and they all seem
> to be files that had spaces or uppercase extensions, and some
> versions are getting URI escaped and lowercased, and some aren't.
> Weird.
This is because the bug was fixed, but existing assets weren't
updated. You'll need to fix them manually, I'm afraid.
Best,
David
|
