Age | Commit message (Collapse) | Author |
|
|
|
user in messages or pages.
Partial fix for ticket #889 and a fix for #931.
|
|
languages than english.
|
|
user menu. Since the information displayed is identical in both admin and
theme views, it makes sense to combine the generation to it is done in a common
location.
|
|
set the size of the underlying flash object.
|
|
printing the form. Fixes ticket #980.
|
|
ticket #899.
|
|
fixes ticket #911
|
|
|
|
provider and then reinstall the current one.
|
|
installers to can_activate to reflect that it is doing more than just checking the environment.
|
|
providers are installed in the admin module screen.
|
|
|
|
(change_provider) with an initialization callback.
|
|
install and switch to a different identity provider.
|
|
The request limit was in place already, but the client didn't respect it before, leading to unhappy users in case they had lots of 3rd party modules installed, or more than 2-3 locales enabled. This is all taken care of now.
|
|
way and rejects submissions that change under the normalization step)
|
|
|
|
pre_deactivate api methods.
|
|
which is called prior to installation. The method allows the module to provide
an error message or warnings if the module can not be installed or activated
without issues. The admin module controller also will fire a pre_deactivate
event, which allows modules to indicate issues that may arise be deactivating the
specified module.
These messages are displayed in a dialog box prior to installation in order to
allow the gallery administrator to determine the appropriate action before proceeding.
Lays the foundation for implementing a fix for ticket #937
|
|
longer casting in ORM.
Task->done is now a string, boolean false is stored as integer 0 and loaded as string "0". On the client side that's interpreted as truthy in JavaScript.
Fix: cast "0" to (bool) before encoding to JSON.
|
|
|
|
|
|
typecasting in ORM).
|
|
|
|
won't get coerced to a string, and then we wind up comparing:
12345 != 12345-12321
In the old approach, they'd both be strings so they'd be inequal. But
in the new approach the first value is an integer (sinced it came from
rand()) so the second value is typecast to an integer which drops
everything after the - sign so they appear equal.
|
|
|
|
|
|
http://dev.kohanaphp.com/issues/2459 -- I don't exactly know why, but
the solutions are equivalent so I'm not going to dig too far.
|
|
longer typecasts values as of http://dev.kohanaphp.com/issues/2459
|
|
|
|
|
|
safe. Add tests to make sure that it doesn't relapse with future
Kohana changes. Fixes ticket #983.
Ref: http://gallery.menalto.com/node/93738
|
|
|
|
parent::save() it'll be reset. Clone it first.
This is an alternate fix for #978.
|
|
changed since the last save. Instead, use the original ORM passed in.
|
|
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.
|
|
This reverts commit e41ad23a8ea05d28a99d12c01d8f317455b1d361.
|
|
operands. '=' is no longer assumed. Fixes ticket #979
|
|
|
|
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.
|
|
actually display the original's title properly. Fixes ticket #966, but does now show us ticket #978
|
|
because the search is done in the browser and the the enter will unexpectedly reload the root directory.
|
|
|
|
|
|
|
|
end of the page.
|
|
ticket #975
|
|
alot of pain to some installations
|
|
In the graphics_rules table height and width set the maximum height and width
values and should be equal. Initially, the height on the resize target rule was
less than the height, which artificially constrained images in portrait mode.
**Note"" this fix requires an upgrade to version 22. All the resizes will be flagged
dirty.
|