| Age | Commit message (Collapse) | Author | 
 | 
1) Changed the way that we get forms.  Now, if you want to get a form
   for a REST resource you prefix /form to the resource id.  So:
    /form/photo/1    : returns a form for editing photo id 1
    /form/comments/1 : returns a form for adding a comment to photo id 1
    /form/comment/1  : returns a form for editing comment id 1
2) Changed the comment module to have two controllers:
    comment:  deals with a single comment resource
    comments: deal with collections of comments attached to an item
Related stuff:
- Moved the comments js into the theme
- Reworked Comment_Helper for clarity
- Moved form generation code down into Comment_Helper
- Cleaned up routes (eliminating new comment ones added in recent rev)
- Added form() function to all REST controllers
- Changed comment module to use a block instead of an arbitrary helper call from the theme
- Comment controller only returns HTML currently, but returns a 201 Created status
  code when a new comment is added, which the Ajax code can catch and act upon.
- Got rid of a lot of extra views in comment module
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
* Hardcode the item has_one owner relationship again
* Overload User_Model::__get to handle missing owners gracefully
* Fix Item_Controller to take the owner_id from the session or
  from the parent album when adding new albums and photos.
 | 
 | 
user; and the views don't break if user module is not installed
 | 
 | 
* Remove user registration link and popup from the theme; this
  shouldn't be done in a popup. Use ajaxform to simplify the way
  that we load the login popup.
* Create form.html.php, this is a template for Forge based forms.
* Move user validation rules into User_Model and let forms
  populate the rules into their forms as useful.
* Undo r18688's changes regarding the REST code.  We should never
  accept a null resource, this breaks the REST abstraction.
* Change login and user controllers to use Forge which lets us delete
  login.html.php and user.html.php since those now are generated by
  the theme-owned form template
 | 
 | 
template.
 | 
 | 
 | 
 | 
and deletes modules into it.
 | 
 | 
 | 
 | 
solution, but it works for now.
 | 
 | 
 | 
 | 
500 localizations on them.
 | 
 | 
PHP includes and show a visible stack trace to help developers.
 | 
 | 
to be like Rails.
 | 
 | 
 | 
 | 
 | 
 | 
variable; change the header so it links to the user controllers; and add the user controllers which don't do anything.
 | 
 | 
_put(), _delete().
This should make it more obvious that these are not your typical
routes, simplifies overall routing by removing a rule and removes the
possibility of accidentally leaking information if we route to one of
them by accident.
 | 
 | 
 | 
 | 
file_structure_test
 | 
 | 
controllers.  Any controller that wants to act RESTful can extend this
class and implement get/post/put/delete.
Tweak default routes to disallow direct access to the REST controller
and direct access to any REST methods.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Item_Controller to accept it.
 | 
 | 
do anything else.  Just got tire of my changes being clobbered :-)
 | 
 | 
 | 
 | 
Revert $_POST back to $this->input->post() because that supports default values.
 | 
 | 
 | 
 | 
Convert $this->input->post to $_POST
 | 
 | 
Album_Test -> Album_Helper_Test
  Photo_Test -> Photo_Helper_Test
 | 
 | 
Adjust/simplify photo::create
Add image uploading to the scaffolding
 | 
 | 
 | 
 | 
 | 
 | 
Create Item_Controller as a common superclass for Album_Controller and
Photo_Controller.  Change routes to route requests to Item_Controller
for dispatching, which in turn will generate get/post/put/delete
requests to the controlller so that each controller has a RESTful
surface.
Change in_place editing to take advantage of this.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
relationship to bind the two.  To do this, I overrode __get in
Item_Model so that $item->owner returns the appropriate User_Model.
 | 
 | 
database exception use the null value)
 | 
 | 
 | 
 | 
 | 
 | 
basic install test. There is no interface at the moment to do authentication. It is dependent on the install of the user module.
 | 
 | 
sometimes i would get the message "There was an SQL error: Table 'gallery3_unittest.modules' doesn't exist - ...." and sometimes I would get the message "Table modules does not exist in your database." In both cases the error code was 44.
 |