Jifty 1.10518 - May 17th, 2011
CORE

SECURITY

BUGFIXES

INSTALL


Jifty 1.10228 - February 28th, 2011
BUGFIXES

DOCUMENTATION

TESTS


Jifty 1.10214 - February 14th, 2011
CORE

VIEW

BUGFIXES

DOCS

TESTS


Jifty 1.01209 - December 9th, 2010

 |  _ \| |      / \  / ___| |/ / | |
 | |_) | |     / _ \| |   | ' /  | |

| __/| |___ / ___ \ |___| . \ |_|
|_| |_____/_/ \_\____|_|\_\ (_)

The biggest change since the last release is Jifty's move to Plack. Please be sure to read the INCOMPATIBILITIES section below.

INCOMPATABILITIES

Jifty is ported to PSGI using Plack. This changed much of the request and response handling code, but hopefully in ways that don't hurt existing apps too much.

POSSIBLE INCOMPATIBILITIES

CORE

PLUGINS

I18N

JAVASCRIPT

BUGFIXES

DOCS

TESTS


Jifty 0.91117 - November 17th, 2009

POSSIBLE INCOMPATABILITIES

     perl -MFile::ShareDir=dist_dir -e 'print dist_dir("Jifty")' \
      | xargs sudo rm -ir

...to make sure the old CRUD is gone so the new CRUD can take its place.

CORE FEATURES

CRUD

DOC

I18N

PLUGINS

REFACTOR

TEST

VIEW


Jifty 0.90701 - July 1st, 2009

BUGFIX

I18N


Jifty 0.90630 - June 30th, 2009

POSSIBLE INCOMPATIBILITIES

CORE FEATURES

REFACTOR

BUGFIX

CRUD

I18N

PLUGINS

DOC

TEST

VIEW


Jifty 0.90519 - May 19th, 2009

POSSIBLE INCOMPATIBILITIES

CORE FEATURES

CRUD

I18N

BUGFIX

DOC

INSTALL

PLUGINS

PUBSUB

REFACTOR

TEST

VIEW


Jifty 0.90409 - April 9th, 2009

POSSIBLE INCOMPATIBILITIES

SECURITY

CORE FEATURES

ACTIONS

COMMAND LINE

PUBSUB

I18N

BUGFIXES

CRUD

DOCUMENTATION

PERFORMANCE

PLUGINS

TESTING

VIEW


Jifty 0.80408 - April 8th, 2008

I18N

BACKWARD-COMPATIBILITY-PROBLEM

BUGFIX

CORE

CRUD

DOC

INSTALL

MISC

PERFORMANCE

PLUGIN

SECURITY

TESTING

VIEW

Jifty 0.71129

I18N

BUGFIX

CORE

CRUD

DOC

INSTALL

MISC

PERFORMANCE

PLUGIN

TESTING

VIEW

Jifty 0.70824

INSTALL

TESTING

VIEW

template foo =>
page { title => 'this is title', other => 'foo' } content {
h1 { 'blah }
}; - clkao

U-PUBSUB

DOC

PLUGINS

Yes, it's learnt from RoR, and it's good to have it when developing applications, or when you just start learning Jifty. - gugod

CORE

we do it in user_object, so solution is generic should work in any case, but only if people use the method to set user_object and user model uses currentuser key to store reference to the CurrentUser - ruz

We used to just ignore the rendering of any columns that refers to a JDBI::Collection, because there's no trivial way to do so.

However, if the column comes with a "render_as", we can assume that the app developer know what he/she is doing. So we just render it as whatever specified.

One scenario is that a collection of tags is rendered as a normal text input field, and develoeprs create tags records in their Tag model in before_create() method. With ajax canonicalize_tags this could be a simple and smart interface, and not difficult to implement at all.

I'm sure that it'll open the chance to let developers write their own collection rendering modules like I did before. If we keep being ignoring, this won't even happend. - gugod

jifty is sane when apps' developers are sane

everybody have own critirea of sanity

     column bars =>
       refers_to "My::Model::BarCollection",
       render as "Collection"
       availables are defer {
           retrieve_some_bars()
       };

in their model class, and it'll just display a nice form to input the value for a list of available bars. - gugod

Jifty 0.70422

[Password Authentication plugin]

[Core]

Jifty 0.70416

Jifty 0.70117

Dependencies:

Jifty 0.70116

New authors

PubSub (audreyt, clkao, jesse)

Database

Documentation

Plugins

Internals

Web UI

Jifty Actions

bin/jifty

Building apps

Dependencies and installation

Internationalization

Testing

Email notifications

Dispatcher

Jifty 0.60912

Testing

Models

Admin UI

REST

Actions

Documentation

Perfomance and optimization

Javascript and HTML

Distribution

Dispatcher

Internals

Internationalization

Email

Plugins

Win32

060707

060706

We found this vulnerability on 6 July 2006 during an internal Security scan. We've added new tests to ensure that these and other similar vulnerabilities don't recur.

We recommend that ALL users of Jifty UPGRADE to 0.60706 IMMEDIATELY.

060616

060615 (15 June 2006)

The following incompatible changes were made to Jifty. For a complete changelog, please see the "Changes" file.

0.60507 (7 May 2006)

0.60505 - Cinco de Jifty! (5 May 2006)

0.60321

0.60221

0.60213

0.51228

0.51225 - Initial release