| Age | Commit message (Collapse) | Author |
|
- Add support for retrieving a list of members from a collection
- Implement put(), post() and delete() for tags.
- Use tag_rest::delete() as a way to remove members from the tag collection
|
|
1) Deal in fully qualified URL resources through the rest
interface. All rest methods are now passed the complete url in
request->url.
2) Create rest::resolve() which lets individual resource definition
code convert a full url into the appropriate matching resource.
Implement gallery_rest::resolve() and tag_rest::resolve()
3) Reimplement tag_rest's get() and post() methods. They're much
simpler now.
4) Implement the tags_rest helper which supports working with the
entire tags collection.
|
|
approach depended on having an $item, which is not the case on all
pages (eg: tag pages). Also, check the CSRF in the logout controller,
else you can use the logout link as a blind forwarder.
|
|
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
|
|
|
|
|
|
guess how to send the user back. Instead, proxy the originating item
id through the edit forms so that we can tell exactly what page we
were on when we began editing. If we were viewing the item, then
redirect to its new url (in case it changed) to fix ticket #745. But
if we were viewing some other item, then just stay on the current page
to fix #940.
The page_type approach didn't work because you'd have the same
"collection" page_type when doing a context menu edit for an album.
|
|
instead of calling rest::forbidden and other rest helper error messages.
|
|
Item_Model. Change the Duplicate errors to sentence case. And generally clean up the flow in _validate().
|
|
Kohana_404_Exception
2) Don't use the input path to lookup the item via relative_path_cache. Instead use url::get_item_from_uri method.
|
|
refactoring for check for commits
|
|
|
|
was returning an empty string. This fixes ticket #955.
|
|
converting the rest API to Kohana 2.4
|
|
|
|
Conflicts:
modules/gallery/controllers/albums.php
modules/gallery/controllers/movies.php
modules/gallery/controllers/photos.php
|
|
|
|
|
|
are acutall a path. Leave it up to the handler to determine.
|
|
Corrected a problem identified with the unit tests... failed if the path was empty on PUT.
|
|
array
|
|
or_where() for compatibility and convenience. Caught by failing unit
tests.
|
|
for lookup. So instead of doing:
ORM::factory("foo", array("some_key" => "some_value"))
you have to do:
ORM::factory("foo"->where("some_key", "=" "some_value")->find()
|
|
|
|
|
|
|
|
|
|
retrieve related ORMs. If we tack a find_all() on the end, it breaks
the User_Definition interface so create User_Model::groups() and
Groups_Model::users() as glue.
|
|
|
|
package" and generate the same SQL as before.
|
|
|
|
resource contents returned via the rest interface.
|
|
|
|
|
|
|
|
|
|
Conflicts:
modules/gallery/helpers/identity.php
|
|
|
|
|
|
|
|
of {Albums|Photos|Movies)_Controller and into the item helper so we can reuse it from the rest put handler.
|
|
path. This allows us to forego the extension as part of the REST url. As well, urls are consistent between normal usage and rest usage.
|
|
|
|
Implement the get_album rest request handler.
|
|
|
|
|
|
controllers.
|
|
the case where we just have one restriction, it's unnecessary.
|
|
Fix viewable() to properly OR view restrictions together.
|
|
|