| Age | Commit message (Collapse) | Author | 
 | 
based on the contents of the user/config/user.php file.  And load that driver based on the User_Driver interface.  There is a default User_Gallery_Driver class that will provide the actual interface implementation.  Replacing this driver will allow a completely different user and authentication implementation to be used... hopefully will reduce issues with embedding and other user management systems.  Removed from unit tests so they will still run.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
do anything else.  Just got tire of my changes being clobbered :-)
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
commit.
 | 
 | 
 | 
 | 
relationship to bind the two.  To do this, I overrode __get in
Item_Model so that $item->owner returns the appropriate User_Model.
 | 
 | 
 | 
 | 
ERROR_MESSAGE");
 | 
 | 
 | 
 | 
 | 
 | 
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.
 | 
 | 
test failures)
 | 
 | 
pivot table was not populated.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
screen and you can install and uninstall it.  Which creates the tables, defines 2 groups (adminstrator, registered) and one user (admin).
 | 
 | 
 | 
 | 
sidebar.html.php file loops over $theme->blocks() which in turn calls
carousel::block() which uses the Block object to create a standard
block UI.  Hooray!
 | 
 | 
Replace theme HTML with *almost* the latest stuff from the
mockups.  (it doesn't include r18467 yet).
Our theme format is now modelled after WordPress / Habari's style
where you have one entry point per type (eg: album.php) which can
load up whatever parts it needs (eg: $theme->display("header"))
Created album and photo helpers which have create() functions
that form the base of our new API, along with tests for them.
Created our own version of the ORM_MPTT since the existing
versions were too buggy and unsupported to depend upon.  Only has
a minimal implementation so far, and the tests are not yet
committed.
Added path(), thumbnail_path() and resize_path() to Item_Model
Extended the scaffolding to allow you to add lots of
photos/albums into your hierarchy.
Deleted modules/mptt -- we're not going to use this anymore.
 | 
 | 
so that the test passes.
 | 
 | 
 | 
 | 
 | 
 | 
mess up the real database.
 | 
 | 
* item model (contains basic item info, similar to the gx version)
  * module model (has info about each module and which version of it is installed)
  * added a very basic unit test to verify that we can create an instance of item
  * Updated our test controller to require a unit_test db config and
    call core::install if it hasn't been done already.
New pattern:
  * core/helpers/core_installer.php creates core_installer helper.
    When we install a new module you call xxx_installer::install(),
    and when you want it to go away, you do xxx_installer::uninstall()
Create
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
browser.
 | 
 | 
 | 
 | 
command line mode, and expects to put data into test/var.  Create a module
to wrap it that generates a nice text-only view of the output.
 | 
 | 
git-svn-id: http://gallery.svn.sourceforge.net/svnroot/gallery/trunk/eval/gx/gallery3/trunk@18408 57fcd75e-5312-0410-8df3-f5eb6fbb1595
 |