| Age | Commit message (Collapse) | Author |
|---|
|
version. It's redundant. Fixes #1985.
|
|
|
|
Nesalk. Fixes #1834.
|
|
|
|
user_installer::initialize() with the right module version number for
the user module and fix the misspelling there then rebuild the
installer.sql. #1694.
|
|
the value of the incorrect spelling (don't assume that the original value was still 5.
|
|
minimum_password_length
|
|
|
|
|
|
This reverts commit 409121942590e12692eaf4e6e9e8b71bfe5ed60c.
|
|
break loose)."
This reverts commit dcddc68f58dac2f0fe71f5a00ea4af32618efa13.
|
|
|
|
Also fixed a UI bug: No longer showing the edit user buttons to admins in the profile view (to be consistent with the requirements in the controller).
|
|
required in model validation. Without this, any save on a user
without email will fail which means that you can't log in.
Bump user module to version 3.
|
|
it the right way. Set a default email address for admins.
|
|
Conflicts:
modules/gallery/tests/xss_data.txt
|
|
installers to can_activate to reflect that it is doing more than just checking the environment.
|
|
(change_provider) with an initialization callback.
|
|
install and switch to a different identity provider.
|
|
|
|
|
|
the user module use that as a trigger to set ownership of the root album to the administrator.
|
|
the advance settings.
|
|
user module into an identity provider. Change how we determine if there are available groups that we need to export
|
|
the new provider is installed.
|
|
changing providers.
|
|
installed. This is mostly for the unit_tests as when the gallery3 installer is used, the user module is activated by default.
|
|
What I've tested to this point, is you can install a new provider, switch to it, login as administrator, uninstall the default user module, reinstall the user module, switch back to the user module and login.
|
|
the system's default table specification. Fixes ticket #597.
|
|
Add xxx_installer::upgrade($version) method so that upgrade stanzas
are separate from install stanzas. In the old code, to do an upgrade
meant that you had to re-evolve everything from the initial install
because we'd step through each version's changes. But what we really
want is for the initial install to start off in the perfect initial
state, and the upgrades to do the work behind the scenes. So now the
install() function gets things set up properly the first time, and the
upgrade() function does any work to catch you up to the latest code.
See gallery_installer.php for a good example.
|
|
Install: <module>_installer::install() is called, any necessary tables
are created.
Activate: <module>_installer::activate() is called. Module
controllers are routable, helpers are accessible, etc. The module is
in use.
Deactivate: <module>_installer::deactivate() is called. Module code
is not accessible or routable. Module is *not* in use, but its tables
are still around.
Uninstall: <module>_installer::uninstall() is called. Module is
completely removed from the database.
Admin > Modules will install and activate modules, but will only
deactivate (will NOT uninstall modules).
|
|
|
|
don't pass in a Group_Model as the argument. This prevents us from
setting permissions on the wrong group by accidentally passing in a
User_Model.
|
|
mirror the drupal pattern of using braces {}.
|
|
tag, search, comment and notification modules (Ticket #68)
|
|
Correct unbalanced brackets
|
|
calls (Ticket #68)
|
|
There's no UI to select the locale yet.
|
|
This change requires a reinstall in order to pick up the new hash
field in the user table.
|
|
File_Structure_Test to make sure we don't regress.
According to the PHP docs, the "public" keyword is implied on static
functions, so remove it. Also, require private static functions to
start with an _.
http://php.net/manual/en/language.oop5.visibility.php
|
|
user modules.
* Don't delete vars when we delete a module. This makes
reinstalling a module a lot easier.
* Add user::lookup() as the preferred way to load a user, so that
other modules don't delve into the user module (that'd be a
problem when we swap out user modules)
* Notify site admins if Akismet is not fully configured
* Bundle all server variables into the comment so that if/when we
re-check the comment, we are not using the server info from the
site admin's request.
* Update Akismet to grab request context data from the comment
* Pre-seed comment fields if we have a logged in user. Update
comment::create() API to clarify it for this.
* Delete comment::update(), that's a controller function.
* Add url to User_Model
* Add author_name() author_email() and author_url() to
Comment_Model. It'll return the appropriate values depending
on whether the comment was left by a logged in user or a guest.
* Use resetForm() instead of clearForm() when we reload the
comment form after ajax submit, this way we preserve the
pre-seeded values.
* In the user profile page, ignore blank passwords.
|
|
|
|
bytes on some systems.
|
|
figure out how to share forms between user and admin editing.
Incremental improvement
|
|
Now you must call ORM::save() after ORM::add() and ORM::remove().
|
|
other functionality. This makes our user/group and access code
fully consistent.
|
|
model.
|
|
working implementation.
|
|
|
|
|
