summaryrefslogtreecommitdiff
path: root/modules/rest
AgeCommit message (Collapse)Author
2010-06-20Remove trailing ?>Bharat Mediratta
2010-06-20Rename error_rest.php to error_rest.json.php so that we specify theBharat Mediratta
result type in the filename as is our convention for views.
2010-06-19$response is optional in the Rest_Exception constructor.Bharat Mediratta
2010-06-19Throw exceptions as appropriate, but allow the Kohana exceptionBharat Mediratta
handling framework to handle the exception and delegate to our template, which will JSON encode the response.
2010-06-19Oops. Fix up a bad instance of $user in rest::access_key() introducedBharat Mediratta
in my last change.
2010-06-18Simplify rest::get_access_key($user) to rest::access_key() thatBharat Mediratta
returns just the access key string for the active user. That's how we use the API, so keep it simple.
2010-06-18change single to double quotes.Bharat Mediratta
2010-06-15Guard against relationships() not returning an array.Bharat Mediratta
2010-06-15Update the description.Bharat Mediratta
2010-06-13Merge branch 'master' into talmdal_devTim Almdal
2010-06-11Send back the REST API version as a header. It's on every request,Bharat Mediratta
which sucks, but it's totally unobtrusive because it's a header so that's ok. Decided that the current version is "3.0" although it will surely change before the final 3.0 release. Fixes ticket #1148
2010-06-10Tweak the error response for rest requests to make it easier for the client ↵Tim Almdal
to extract error information.
2010-06-08Don't use the standard error formatting for exceptions that have occurred as ↵Tim Almdal
part of a REST request. Format the exception as a json encoded text string so the client can extract the fault information if they so choose.
2010-06-08The status message for an HTTP 400 status should always be 'Bad Request', if ↵Tim Almdal
I'm reading the specification right.
2010-06-07Merge branch 'master' into talmdal_devTim Almdal
2010-06-07If the identity provider changes then delete all the rest user_access_keys, ↵Tim Almdal
as they are no longer valid. (i.e. all the related users have been deleted.)
2010-06-06Merge branch 'master' into talmdal_devTim Almdal
2010-06-05Add an advanced setting to allow developers to allow guest access toBharat Mediratta
REST entities.
2010-04-21Merge branch 'master' into talmdal_devTim Almdal
2010-04-17Update tests to reflect recent changes to the REST API.Bharat Mediratta
2010-04-07Merge bharat_dev rest implementationTim Almdal
2010-04-06Merge branch 'master' into talmdal_devTim Almdal
2010-04-04REST changes: Allow PUT and POST requests to modify members, notBharat Mediratta
just entity. TESTS ARE NOT UPDATED YET. - Fix item_rest::get() to maintain the proper sort order, which requires duplicating some Item_Model code. - Elide "weight" from the REST version of item - Adjust the weight of members according to the order they're returned from the client. You can't add or remove members here, you can only reorder them. - Changed the wire protocol to handle more complex values. Now "entity" and "members" are JSON encoded. The Gallery3 helper does this correctly. - Changed the wire protocol for tag_item -- now it stores the tag and item urls in the entity, not as members. This is more consistent. - Added missing security for renaming and deleting tags. - Got rid of vestigial tag_rest::post(). We add/remove tags via the relationship.
2010-03-31Merge branch 'master' into talmdal_devTim Almdal
Conflicts: modules/rest/controllers/rest.php
2010-03-30Rest -> RESTBharat Mediratta
2010-03-30Rename "access_token" to "access_key" in the code for consistency.Bharat Mediratta
2010-03-30Rename "user_access_tokens" table to "user_access_keys" as step 1 of aBharat Mediratta
multi step process to refer to REST access keys as "access_key" everywhere. Bump the rest module to version 2.
2010-03-21If the access token is not set, then look in the post data.Tim Almdal
2010-03-13Merge branch 'master' into talmdal_devTim Almdal
2010-03-13Whitespace correctionTim Almdal
2010-03-13Changes to support updating the child elements within an album. In this ↵Tim Almdal
change the urls of the children are sent up asan array of post fields children[0].... children[n]. If an existing child is not included it is deleted. Including a url to an child in another album will move the child. Changing the order of the children will respect the order of the children, if the sort column is 'weight'
2010-03-13Update tests to reflect the fact that you have to be logged in to do anything.Bharat Mediratta
2010-03-13Guests don't get access to the REST API.Bharat Mediratta
2010-03-05Update tests to reflect the fact that you have to be logged in to do anything.Bharat Mediratta
2010-03-03Guests don't get access to the REST API.Bharat Mediratta
2010-03-03Update the copyright to 2010. It's only 3 months into the year :-)Bharat Mediratta
2010-02-24Remove redundant print statement. rest::reply() does the print so having the ↵Tim Almdal
extra print statement could lead to problems.
2010-02-20When using rest::reply(), don't call var_export() if the response is empty.Bharat Mediratta
2010-02-19Refactor away the "display_all" construct in User_Profile_Controller.Bharat Mediratta
"display_all" is too coarse, and we should be letting event handlers make the appropriate decision on what to display and when. This duplicates some code, but it's now very clear in the event handlers what's getting shown. Throw a 404 if we try to view the user profile for a missing user. The only feature change in this should be that we now display the name, full name and website for a user to any other registered user, which makes sense since these are typically public fields. Don't show any of the edit buttons unless identity::is_writable()
2010-02-14If the return object is empty still return the empty object in the json ↵Tim Almdal
response.
2010-02-07Create the concept of a "failed authentication" as semanticallyBharat Mediratta
separate from a successful or failed login. 1) Rename user_login_failed event to user_authenticate_failed 2) Rename failed_logins table to failed_auth (bump Gallery module to v27 to rename the table) 3) auth::too_many_failed_logins -> auth::too_many_failures 4) auth::record_failed_auth_attempts -> auth::record_failed_attempts auth::clear_failed_auth_attempts -> auth::clear_failed_attempts
2010-01-31Fix lots of warnings that pop up when we're in E_STRICT mode. They'reBharat Mediratta
mostly issues around uninitialized variables, calling non-static functions in a static context, calling Session functions directly instead of on its singleton, passing non-variables by reference, and subclasses not using the same interface as the parent class.
2010-01-30Refactory auth::too_many_failed_logins() out ofBharat Mediratta
auth::validate_too_many_failed_logins() to conceptually separate the two.
2010-01-30Protect REST login controller from brute force attacks too.Andy Staudacher
And make the REST auth token less predictable by using a better source for randomness.
2010-01-29Use ? or & as appropriate when appending output=html.Bharat Mediratta
2010-01-29Use var_export instead of print_r for better clarity.Bharat Mediratta
2010-01-28Do all the html::clean|purify calls in the views and not the controller. ↵Tim Almdal
Also clean the subject line and email message body of the contact user email.
2010-01-25Merge branch 'master' of git@github.com:gallery/gallery3 into bharat_devBharat Mediratta
Conflicts: modules/gallery/libraries/MY_ORM.php
2010-01-24Add the active notifications and rest api key to user profile page.Tim Almdal
2010-01-23Update tests for recent REST changes.Bharat Mediratta