| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
3.1.5
* Avoid Rails 5 deprecation warning about original_exception
* No longer generates <a rel="start"> for first page link since "start"
is an invalid rel value
3.1.4 (seems not released)
3.1.3
* Rails 5 compatibility for inheriting query params in pagination links
* Fix locale load path so that application can override will_paginate's
built-in translations.
3.1.2
* Further fix security vulnerability when generating pagination URLs in
Rails.
3.1.1
* Fixed security vulnerability when generating pagination URLs in Rails.
3.1.0
* Rails 5.0 support
* Drop support for old Active Record finder params to paginate():
# now unsupported:
User.paginate(:page => 1, :order => 'created_at DESC', :conditions => ...)
# convert to Arel syntax instead:
User.order('created_at DESC').where(...).paginate(:page => 1)
# or, even better:
User.order('created_at DESC').where(...).page(1)
* Add support for pagination with Mongoid
|
|
* Rails 5.0 support
* Drop support for old Active Record finder params to paginate():
# now unsupported:
User.paginate(:page => 1, :order => 'created_at DESC', :conditions => ...)
# convert to Arel syntax instead:
User.order('created_at DESC').where(...).paginate(:page => 1)
# or, even better:
User.order('created_at DESC').where(...).page(1)
* Add support for pagination with Mongoid
|
|
Problems found locating distfiles:
Package cabocha: missing distfile cabocha-0.68.tar.bz2
Package convertlit: missing distfile clit18src.zip
Package php-enchant: missing distfile php-enchant/enchant-1.1.0.tgz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
Improve compatibility with newer rails. Please refer
<https://github.com/mislav/will_paginate/commits/3-0-stable> in detail.
|
|
* important security fix that prevents XSS in generated pagination links
* always call html_safe if available on will_paginate result
* exclude reorder for count queries
|
|
No changes are available, but various changes.
|
|
Exact changes are unknown.
|
|
Changes are unknown.
|
|
Changes are unknown.
|
|
Changes are unknown, but it seems a few bug fixes.
|
|
* Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk.
* Add LICENSE.
* Remove default value of GEM_BUILD.
= 2.3.12, released 2009-12-01
* make view helpers "HTML safe" for Rails 2.3.5 with rails_xss plugin
= 2.3.11, released 2009-06-02
* fix `enable_actionpack`
= 2.3.10, released 2009-05-21
* count_by_sql: don't use table alias with any adapters starting with "oracle"
* Add back "AS count_table" alias to `paginate_by_sql` counter SQL
= 2.3.9, released 2009-05-29
* remove "AS count_table" alias from `paginate_by_sql` counter SQL
* Rails 2.3.2 compat: monkeypatch Rails issue #2189 (count breaks has_many :through)
* fix generation of page URLs that contain the "@" character
* check for method existance in a ruby 1.8- and 1.9-compatible way
* load will_paginate view helpers even if ActiveRecord is not loaded
== 2.3.8, released 2009-03-09
* Rails 2.3 compat: query parameter parsing with Rack
== 2.3.7, released 2009-02-09
* Removed all unnecessary &block variables since they cause serious memory damage and lots of subsequent gc runs.
== 2.3.6, released 2008-10-26
* Rails 2.2 fix: stop using `extract_attribute_names_from_match` inernal AR method, it no longer exists
== 2.3.5, released 2008-10-07
* update the backported named_scope implementation for Rails versions older than 2.1
* break out of scope of paginated_each() yielded block when used on named scopes
* fix paginate(:from)
== 2.3.4, released 2008-09-16
* Removed gem dependency to Active Support (causes trouble with vendored rails).
* Rails 2.1: fix a failing test and a deprecation warning.
* Cope with scoped :select when counting.
== 2.3.3, released 2008-08-29
* Ensure that paginate_by_sql doesn't change the original SQL query.
* RDoc love (now live at http://gitrdoc.com/mislav/will_paginate/tree/master)
* Rename :prev_label to :previous_label for consistency. old name still functions but is deprecated
* ActiveRecord 2.1: Remove :include option from count_all query when it's possible.
== 2.3.2, released 2008-05-16
* Fixed LinkRenderer#stringified_merge by removing "return" from iterator block
* Ensure that 'href' values in pagination links are escaped URLs
== 2.3.1, released 2008-05-04
* Fixed page numbers not showing with custom routes and implicit first page
* Try to use Hanna for documentation (falls back to default RDoc template if not)
== 2.3.0, released 2008-04-29
* Changed LinkRenderer to receive collection, options and reference to view template NOT in
constructor, but with the #prepare method. This is a step towards supporting passing of
LinkRenderer (or subclass) instances that may be preconfigured in some way
* LinkRenderer now has #page_link and #page_span methods for easier customization of output in
subclasses
* Changed page_entries_info() method to adjust its output according to humanized class name of
collection items. Override this with :entry_name parameter (singular).
page_entries_info(@posts)
#-> "Displaying all 12 posts"
page_entries_info(@posts, :entry_name => 'item')
#-> "Displaying all 12 items"
== 2.2.3, released 2008-04-26
* will_paginate gem is no longer published on RubyForge, but on
gems.github.com:
gem sources -a http://gems.github.com/ (you only need to do this once)
gem install mislav-will_paginate
* extract reusable pagination testing stuff into WillPaginate::View
* rethink the page URL construction mechanizm to be more bulletproof when
combined with custom routing for page parameter
* test that anchor parameter can be used in pagination links
|
|
|
|
textproc/ruby-will-paginate.
Pagination is just limiting the number of records displayed. Why should
you let it get in your way while developing, then? This library makes
magic happen. Did you ever want to be able to do just this on a model:
@posts = Post.paginate :page => params[:page],
:order => 'created_at DESC'
and then render the page links with a single view helper? Well, now
you can.
<%= will_paginate @posts %>
|
