gallery3.git - A clone of the Gallery3 code for testing and development.

Age	Commit message (Collapse)	Author
2013-01-21	Update copyright to 2013. Fixes #1953.	Bharat Mediratta

2012-05-15	Follow-on to ce34e89c899a3fca6d647e99742c39b8b7a4f3e0 for #1865 -	Bharat Mediratta
	allow strings and coerce them to integers. It might be easier to just cast whatever comes in, but I'm worried that we'll accidentally cast an array to an int(1) without realizing it.
2012-05-15	Different approach to resolving #1865, this replaces ↵	Bharat Mediratta
	6a6b3f90f36293a40cba091c3ac387abb64f3c1a which was rolled back.
2012-02-27	Update copyright to 2012. #1822	Bharat Mediratta

2011-01-21	Update copyright to 2011.	Bharat Mediratta

2010-03-03	Update the copyright to 2010. It's only 3 months into the year :-)	Bharat Mediratta

2010-01-20	Oops, bug in save() -- we weren't returning the saved value!	Bharat Mediratta

2010-01-20	Delete MY_ORM::original(). We did not have proper containment to	Bharat Mediratta
	generate $original when we needed it, resulting in inconsistent behavior.
2010-01-17	If we call original() and there's no $original yet, then consider this	Bharat Mediratta
	to be the original. That should be safe because we're already guarding __set, __unset and save.
2010-01-15	Revert "Fix for ticket #978. Don't reset the original property as part of ↵	Bharat Mediratta
	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.
2010-01-15	Revert "Did the old commit then save trick"	Bharat Mediratta
	This reverts commit e41ad23a8ea05d28a99d12c01d8f317455b1d361.
2010-01-13	Did the old commit then save trick	Tim Almdal

2010-01-13	Fix for ticket #978. Don't reset the original property as part of the save ↵	Tim Almdal
	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.
2009-11-25	Preliminary work to cut over to Kohana 2.4	Bharat Mediratta
	- Kohana::log() -> Kohana_Log::add() - Kohana::config_XXX -> Kohana_Config::instance()->XXX - Implement View::set_global in MY_View - Updated Cache_Database_Driver to latest APIs - ORM::$loaded -> ORM::loaded() - Updated item::viewable() to use K2.4 parenthesization
2009-08-29	Adding SafeString which is going to replace p::clean() and p::purify().	Andy Staudacher
	Refactoring of Xss_Security_Test. t() and t2() return a SafeString instance. TODO: - Update all code to use SafeString where appropriate. - Update golden fole of Xss_Security_Test - Stop reporting CLEAN vars in Xss_Security_Test
2009-08-02	Change the API for getting to the original state of an ORM.	Bharat Mediratta
	Old API: $obj->original("field_name") New API: $obj->original()->field_name This allows us to revert the varous xxx_updated events back to passing an original ORM as well as the the updated one. This makes for a cleaner event API. Old API: comment_updated($comment) { $comment->original("field_name") } Old API: comment_updated($old, $new) { $old->field_name }
2009-07-17	Change model_cache::clear() API to clear everything. This prevents	Bharat Mediratta
	old ORM relationships from hanging around, which was causing problems when doing MPTT manipulations (resulting in incorrect permission propagation-- very bad!)
2009-07-16	Non-trivial changes to the event handling code:	Bharat Mediratta
	1) The item_updated event no longer takes the old and new items. Instead we overload ORM to track the original data and make that available via the item. This will allow us to move event publishing down into the API methods which in turn will give us more stability since we won't require each controller to remember to do it. 2) ORM class now tracks the original values. It doesn't track the original relationships (no need for that, yet) 3) Added new events: item_deleted group_deleted user_deleted
2009-05-28	Flush the model cache as appropriate every time we call ORM::save().	Bharat Mediratta
	Fixes ticket #301
2009-05-27	Restructure things so that the application is now just another module.	Bharat Mediratta
	Kohana makes this type of transition fairly straightforward in that all controllers/helpers/etc are still located in the cascading filesystem without any extra effort, except that I've temporarily added a hack to force modules/gallery into the module path. Rename what's left of "core" to be "application" so that it conforms more closely to the Kohana standard (basically, just application/config/config.php which is the minimal thing that you need in the application directory) There's still considerable work left to be done here.