| Age | Commit message (Collapse) | Author |
|---|
|
(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.
|
|
in the version 24 upgrade code.
Update packager to serialize files so that we can serialize the new
.htaccess files
Update init_var.php to include the newly serialized .htaccess files.
Fixes ticket #587.
|
|
|
|
number in gallery_installer::install() so the install.sql was out of
sync.
|
|
email address for the admin user, since one is required for all users.
|
|
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.
|
|
we do a more thorough security audit on it first.
|
|
new installations.
|
|
tweaks result in smaller diffs.
|
|
|
|
related options."
This reverts commit 678e22996d73b96833c48d94751344a6bd8f2899.
|
|
|
|
|
|
are no allowed again
|
|
hash of the module_name:block_id. Also change the packager so we delete the _cache variable for the module gallery not core.
|
|
module_name:block_id. This allows easier lookup of blocks to remove when modules
are being deactivated. Change the module activation/deactivation to call (activate|deactivate)_blocks instead of just the sidebar blocks. This insures
that when a module is deactivated any admin dashboard blocks are removed as well the site sideboard blocks. Fix for ticket #876.
|
|
refactoring of the user module into an idnetity provider
|
|
steps to merge into your head.
|
|
defined admin (id = 2)
|
|
gallery_graphics:: to each of the defined rules operations
|
|
* moves the composite method back into core
* requires that the operation be fully qualified i.e. gallery_graphics::resize
* caches the graphics rules on each request
|
|
theme names.
Update installer.sql
|
|
database type. Changed the packager to not remove the engine specification if the table is search_records. Fixes Ticket #774
|
|
|
|
|
|
the system's default table specification. Fixes ticket #597.
|
|
|
|
charset (utf8) expressions that were removed by merging in rledisez's left/right -> left_ptr/right_ptr changes.
|
|
|
|
- gallery_version is gone
- access related columns are now binary (Postgres)
- for some reason we've reverted back to the /*!40101*/ style settings
in mysqldump.
|
|
- DENY = false
- ALLOW = true
- UNKNOW = null (for intent only)
- INHERIT = null (for cache)
Upgrade is not included for now.
(cherry picked from commit 719c59e0402464a0e2b14915f6d10218ff5d4729)
|
|
easier to see what's changed.
|
|
SET character_set_client = @saved_cs_client;
becomes:
/*!40101 SET character_set_client = @saved_cs_client */;
for MySQL 4.0.1-01 and newer.
|
|
change).
Refresh the install.sql.
|
|
gallery 2 -> 3
comment 1 -> 2
|
|
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.
|
|
only implementing schema version 1. This caused install.sql to be
populated from version 1 which meant that after install you'd have to
run the upgrader. No harm done, and the pattern is fixed for the
future.
Alphabetize the tables so it's easier to find stuff.
|
|
|
|
that install.sql is more stable.
|
|
database and var directory to a seperate standalone file in the installer. This will save the current database environment and restore it when the packaging is complete
|
|
Settings > Advanced. It's stored in the variable as an
internationalized string and localized at output time.
|
|
Rebuild install.sql
|
|
|
|
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).
|
|
> Settings > Advanced. The default is 75.
|
|
|
|
single query. In most cases, we were fetching 4-5 variables per page
load, so this is 2-3x faster.
|
