| Age | Commit message (Collapse) | Author |
|---|
|
Conflicts:
modules/gallery/helpers/gallery_block.php
modules/gallery/helpers/gallery_theme.php
modules/gallery/helpers/user.php
modules/user/helpers/user_event.php
|
|
gallery module
|
|
|
|
gallery module.
|
|
|
|
Conflicts:
modules/gallery/controllers/admin_users.php
modules/gallery/controllers/password.php
modules/gallery/helpers/group.php
modules/gallery/helpers/user.php
modules/notification/helpers/notification.php
|
|
|
|
|
|
If you can change the extension, then you can alter the way the server
handles the file, which is a security problem. So for example, you
can change a .JPG to a .PHP and then if you put some malicious PHP
code in the EXIF data, you can get the server to execute
it. Vulnerability is low because only users who have edit permissions
could do this.
Fixes ticket #846
|
|
performance.
Fixes ticket #835, thanks Joe7!
|
|
Make the filename field required for photos/movies.
Fixes ticket #838
|
|
|
|
the notifications to use user::get_user_list instead of accessing the table directly.
|
|
user::lookup_by_name and user_lookup API methods.
Convert the Admin_User controller
Convert the login and password change controller
Change the item model to call user::lookup to get the owner.
On the log model, delete the relationship between the log and user table, and replace with a
call to user::lookup
(cherry picked from commit 194cc3b27a73afe5119da9f09407c1e068dc6fa3)
Create the get_user_list, lookup_by_name, lookup_by_hash and get_group_list api functions
|
|
our approach to restfulness is that it assumes that the resource will be found in the gallery database. It may well be there, but in the case of using plugable drivers for users management, there are no guarantees that it is in our database or it could be in a ldap directory. So it was just easier to remove the restfulness and just call user::lookup instead.
(cherry picked from commit b3211cb2a8282556d410c91771baeb764d47ed10)
|
|
|
|
|
|
Password" link
|
|
|
|
and display if the Identity driver does not support writes. This is set in the config.identity.php
|
|
our approach to restfulness is that it assumes that the resource will be found in the gallery database. It may well be there, but in the case of using plugable drivers from users, it could be in a ldap directory, it could be the gallery3 database, but the model could be wrapped in a control structure. So it was just easier to remove the restfulness and just call user::lookup instead.
|
|
opposed to return it.
|
|
|
|
|
|
|
|
and applied updates to views. Moved over draggable/droppable styles. Use g-target consistently for drag/drop interactions. Minor re-ordering of selectors in gallery.common.css. Updates to css comments.
|
|
|
|
back to looking in just lib itself. This is not consistent behavior
with the rest of our module structure, though so we should probably
make it more consistent.
Fix up the permission images to use gallery::find_file again.
|
|
Fixed references to them in the edit permissions view.
|
|
providing the default Identity implementation.
* Remove the user_event callbacks and move them to the gallery_event callbacks. This will insure that the active user is always loaded (because the gallery callbacks are always called first) to its available to other gallery_ready handlers. Moved the method set_request_locale to the locales helper as it is more related to locales.
* Move the user controllers and views into the gallery module.
* Move the theme and block processing out of the user module and into core.
|
|
drivers early in the process so the session deserialization works.
|
|
|
|
the other gallery graphics functions.
|
|
the other gallery graphics functions.
|
|
classes which extend the User_Definition and Group_Definition classes defined in the Identity API
|
|
for event notifications. This drove out some issues in the user::users and
group::groups API backend.
|
|
Identity/Gallery::list_groups
|
|
|
|
writes and saves later.
Convert the Admin_User controller
Convert the login and password change controller
Change the item model to call user::lookup to get the owner.
On the log model, delete the relationship between the log and user table, and replace with a
call to user::lookup
|
|
Create an Identity library that defines the interface the Gallery3 expects
Move the user and group helpers into the gallery module to provide the familiar
interface into the Identity library.
Create a Gallery Identity back-end that is supplied by the user module.
The vision here is that all user and group code that is gallery or ui specific
is contained within the core product. Anything that relates to manipulating a
user or group is contained in the back end code that can be replaced.
|
|
|
|
|
|
|
|
the module or theme. This checks for the existence of an application/modules or application/themes first."
This reverts commit e1e1461a77caf5bff457927f098366497de6ffff.
|
|
module or theme. This checks for the existence of an application/modules or application/themes first.
|
|
shared images from wind to lib. Deleted unused images in the admin_wind. This will likely break a few ajax features.
|
|
|
|
|
|
to the document root. Instead ignore all th path parts until one of application, modules, themes, or libs is found. Fixes ticket #827
|
|
|
