| Age | Commit message (Collapse) | Author |
|
date_default_timezone_get() in modules/gallery/config/locale.php but it's
still overrideable in Admin > Settings > Advanced. Follow on fix for #1637.
|
|
- Update gallery_installer::install() to set the version to 48 and
set the timezone
- Rebuild installer.sql
|
|
* Fixes #1637
* New advanced setting gallery/timezone
* Default setting comes from PHP
|
|
|
|
|
|
|
|
upgrader so that it's cleared any time we run an upgrade. Part of
|
|
the last check and auto upgrade checking is enabled, fire off an XHR
to check for a possible upgrade. Finishes off #1605.
|
|
module to v46. There's a new block in the admin dashboard which
controls whether automatic checking happens, and lets you check
immediately. If a newer version is detected, a site status message
appears for admins providing upgrade instructions.
Automatic checking is not yet implemented (even though the UI claims
that it exists). This is all for #1605.
|
|
text. Fixes #1612.
|
|
MySql has problems when comparing float values against -seemingly same- float input, see http://dev.mysql.com/doc/refman/5.0/en/problems-with-float.html for details.
Fixes #1610
|
|
1) Make database changes in gallery_installer::install() instead of
in installer/install.ql
2) Bump the version number in modules/gallery/module.info
|
|
|
|
but DB trimmed data over 2048 chars. Converting column into TEXT type.
Note: The effective maximum length of a VARCHAR in MySQL 5.0.3 and later is subject to the maximum row size (65,535 bytes, which is shared among all columns) and the character set used.
In contrast to CHAR, VARCHAR values are stored as a one-byte or two-byte length prefix plus data. The length prefix indicates the number of bytes in the value. A column uses one length byte if values require no more than 255 bytes, two length bytes if values may require more than 255 bytes.
|
|
|
|
DUPLICATE KEY UPDATE SYNTAX in cache lib
|
|
|
|
random::hash()
random::string()
random::percent()
random::int()
So that we don't have lots of different ways to get random values all
over the code. Follow-on to #1527.
|
|
Fixes #1527.
|
|
name=_cache row. If that overflows, it will cause us to be unable to
load variables, and we can't recover from that.
Instead, use the Cache table. Bump the gallery module to v40. Fixes
ticket #1405.
|
|
Fixes ticket #1384.
|
|
provide a "show_user_profiles_to" setting to allow admins to open it
up to everybody (choices there are "registered_users", "admin_users"
or "everybody"). Fixes ticket #1378.
|
|
|
|
reply-to addresses to an empty string. The first time the user model is saved, set the sendmail from and reply-to addresses. Requires an update to gallery version 38.
|
|
failure of some kind we can restart the upgrade and it'll continue.
Fixes ticket #1325.
|
|
"example.com" when we are using the CLI so we'll get inconsistent
behavior between CLI and the web interface.
For now hardcode it to be example.com so that it's clear. But to do
it right we need an after_install step which actually fixes it up.
And probably an after_upgrade step as well.
|
|
file and store them as gallery module variables. Requires a version number bump to 37.
|
|
expose in Admin > Appearance > Theme Options and defaults to
lib/images/favicon.ico.
Thix fixes ticket #1312.
|
|
as the max title length when we do title truncation in the wind theme.
Bump the gallery module to 35.
|
|
to find missing access_caches is very slow. Bump Gallery module to v34.
|
|
which is on every album page. Bump Gallery module version to 33.
|
|
|
|
module ordering, which is currently being done in the moduleorder
contrib module.
By default, the weight will be the same as the id of the row which
means that new modules will get added at the end of the list. This is
covered in the upgrade case as well.
The one gotcha is that we need to make sure that we don't try to sort
by the weight column if the gallery module version is < 32, which is
something we haven't done before.
Fixes ticket #1272.
|
|
links on the Admin > Maintenance page to allow you to turn it on and
off. This should be efficient since we cache all vars and look them
up on every request anyway.
This also allows us to have the Fix task enable maintenance mode while
it's running which greatly reduces the chances that somebody will come
along and hork the database while we're tinkering with MPTT pointers.
Fixes ticket #1259.
|
|
|
|
(and fix the packager to truncate the cache table before packaging)
|
|
|
|
BiDi algorithm. Also, properly marking the "Powere by" string for translation.
See: http://www.w3.org/International/tutorials/bidi-xhtml/#Slide0420
|
|
|
|
version 28 as a preparation for admin area compartmentalization.
|
|
separate from a successful or failed login.
1) Rename user_login_failed event to user_authenticate_failed
2) Rename failed_logins table to failed_auth (bump Gallery module to
v27 to rename the table)
3) auth::too_many_failed_logins -> auth::too_many_failures
4) auth::record_failed_auth_attempts -> auth::record_failed_attempts
auth::clear_failed_auth_attempts -> auth::clear_failed_attempts
|
|
|
|
Fixes ticket #587.
|
|
minute after there have been 5 consecutive failed login attempts.
Fix for ticket #589.
|
|
|
|
Upgrade gallery3 module to version 23
|
|
number in gallery_installer::install() so the install.sql was out of
sync.
|
|
|
|
|
|
alot of pain to some installations
|