| Age | Commit message (Collapse) | Author |
|
not capturing all cases for setting and resetting $original, which
leads to some weird and hard to reproduce behavior.
Instead, if we need the original just reload it from the database.
This may result in a somewhat excessive load in places, but we'll have
to fix that in a later optimization pass.
|
|
|
|
before deciding whether or not we changed a value.
Change valid_name to be cascading, not parallel.
|
|
consistency between field names than deal with underlying issues with
Forge bitching about the "name" property.
|
|
consistency between field names than deal with underlying issues with
Forge bitching about the "name" property.
|
|
does the rest. This function is symmetrical to rest::resolve.
|
|
|
|
change_photo_no_csrf_fails_test() which has been broken since we
deleted Rest_Controller.
|
|
|
|
|
|
|
|
|
|
change_album_no_csrf_fails_test() had been broken since we got rid of
REST_Controller, but was poorly written so we didn't realize it. Boo.
|
|
greatly!
|
|
|
|
|
|
|
|
Now to move an item, you just change its parent_id.
|
|
Fix up rename_photo_test.
|
|
|
|
save() now that Kohana ticket #2504 is resolved.
|
|
|
|
|
|
typecasting in ORM).
|
|
|
|
won't get coerced to a string, and then we wind up comparing:
12345 != 12345-12321
In the old approach, they'd both be strings so they'd be inequal. But
in the new approach the first value is an integer (sinced it came from
rand()) so the second value is typecast to an integer which drops
everything after the - sign so they appear equal.
|
|
|
|
|
|
safe. Add tests to make sure that it doesn't relapse with future
Kohana changes. Fixes ticket #983.
Ref: http://gallery.menalto.com/node/93738
|
|
starts failing, the bug is fixed and we can go fix our code that works
around it.
|
|
|
|
since we can't have unsafe slugs.
Add basic_validation_test.
|
|
http://dev.kohanaphp.com/issues/2504
|
|
|
|
|
|
|
|
|
|
Conflicts:
modules/gallery/models/item.php
|
|
the save processing, because that will overwrite the original values with all the new values. The problem with the original approach is that when changed event handlers used ->original(), it had already been reset as part of the save processing. Went back and forth on either leaving this alone and forcing callers to save the original prior to calling the save function, but there were a few event handlers that used ->original(). This seemed the easier change. So to reset the original you need to call reload() or clear(). There is now an optional parameter on the reload to only reload the original."
This reverts commit daeaca110d16128040c86727c65df225e957f7c6.
|
|
|
|
processing, because that will overwrite the original values with all the new values. The problem with the original approach is that when changed event handlers used ->original(), it had already been reset as part of the save processing. Went back and forth on either leaving this alone and forcing callers to save the original prior to calling the save function, but there were a few event handlers that used ->original(). This seemed the easier change. So to reset the original you need to call reload() or clear(). There is now an optional parameter on the reload to only reload the original.
|
|
|
|
clauses and deletes all the entries in the table unless an array of id's are
passed as the parameter. This fix used the Database_builder to specify any where
conditions. Thanks psvo for find the first one. :-)
|
|
|
|
longer considered dirty in the logout controller.
|
|
1) Simplify gallery_rest to return flat models, no children and do no
validation for now.
2) Flatten the REST replies and use HTTP codes to indicate
success/failure instead of additional status messages.
3) Use the message and error code support in the base Exception class,
instead of brewing our own in Rest_Exception.
4) Get rid of rest::success() and rest::fail() -- we only need
rest::reply() since all failures are covered by throwing an
exception.
5) Get rid of /rest/access_key and just use /rest for authentication.
6) Inline and simplify rest::normalize_request since we only use it once
7) Change rest::set_active_user to succeed or throw an exception
8) Extract Rest_Exception::sendHeaders into rest::send_headers()
Here's what's currently broken:
1) Data validation. There currently is none
2) Logging. That's gone too
3) image block and tag code is broken
4) Tests are broken
5) No movie support
|
|
|
|
|
|
|
|
1) We do support changing the name.
2) Choose a random name to avoid conflicts.
|