Fix: Album description showing up in Photos when photo has no synopsis
fix: Photo now shows correct confirmation screen
fix: Photo now gets auto-committed according to Gallery approval workflow
fix: Formatting problems in Album view
fix: Photo and Album assets now retain their Owner after other users edit them.
fix: Gallery::Utility migration now retains createdBy, creationDate, and ownerUserId.
Testing Gallery::Utility a bit more thoroughly.
fix: Photo EXIF data now gets cached correctly and sanitized for references (since JSON won't store them and they're of no use to us anyway).
In these three files, any check for status=archived was removed, since
in each case it is possible that the Asset may want to be viewable
when it is archived, like Files, Posts, etc.
Updated Session/Url.t to remove tests for status=archived.
the child of a non-system page that you had edit rights to.
- api: Added a unified contraints system for the file and image assets.
- fixed several problems with the new attachments control, setup, and tempspace
the file does not exist.
Fixed a bug I created by changing the order of update and change comparison
in Asset/File.pm. This caused Asset/File.t, Asset/File/Image.t and
Macro/Thumbnail.t to fail.
the assetSize in the db was set wrong. This happened when a File/Image
was added, and when it is committed. Editing the Asset would fix it, but
once it was committed, the files in the Storage area were not added.
List of Changes:
1) Removed setSize from File/Image.pm. It can inherit from File.
2) In Asset::File::processPropertiesFromFormPost, set _storageLocation to the Storage
object. Remove the call to setSize since it's done in ->update
3) In Asset::File::setSize, fetch the current storage object via getStorageLocation.
4) In Asset::File::update, move the call to update after the filesystem work. This
way changes in the size of the permissions file get accounted for.
5) In Asset::update, call setSize after all changes, regardless of whether or not
properties have changed.
6) In Asset::setSize, refactor out the size calculation and update $self's properties
cache so that long running scripts have the right size.
mechanism. This isn't optimal; should find a way to use the streaming
mechanism iff we know that there's going to be a live HTTP session on the
other end and not just a filehandle.
existing overrides and callers for that method and making sure they followed
the correct signature. Various related cleanups.
This should fix those bugs with collaboration systems refusing to be copied
or deployed as packages.
(Is there a way to get content_type that wouldn't require File::MMagic?)
Apache2::SubRequest's method lookup_file coused segfault in apache, so I scrapped that and used File::MMagic to to content type determing
Also fixed credit and added a currentPage.rankIsN variable to navigation
