# Will Paginate and radiant-paginate-extension?

**URL:** <https://www.ruby-forum.com/t/will-paginate-and-radiant-paginate-extension/143134>\
**Category:** Radiant CMS\
**Created:** [July 15, 2008, 3:45pm UTC](https://www.ruby-forum.com/t/will-paginate-and-radiant-paginate-extension/143134 "2008-07-15T15:45:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![janpipek](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/b5e925/32.png) [@janpipek](https://www.ruby-forum.com/u/janpipek)\
**Post date:** [July 15, 2008, 3:45pm UTC](https://www.ruby-forum.com/t/will-paginate-and-radiant-paginate-extension/143134/1 "2008-07-15T15:45:10Z")

</div>

I seem to have some issues with installing pagination in Radiant too:

I want to use “radiant-paginate-extension”:

[http://github.com/ihoka/radiant-paginate-extension/tree/master](http://github.com/ihoka/radiant-paginate-extension/tree/master)

But when I “rake” I get:

rake production db:migrate:extensions  
(in /home/chainrea/radapp)  
rake aborted!  
Expected  
/home/chainrea/radapp/vendor/extensions/paginate/app/models/paginate\_tags.rb  
to define PaginateTags

I suspect the issue to be related to the requirement of the gem “Will  
Paginate”.

> **[GitHub - mislav/will\_paginate: Pagination library for Rails and other Ruby...](https://github.com/mislav/will_paginate/tree/master)**
>
> master

And I have installed it prior to installing “radiant-paginate”, but  
maybe it isn’t configured properly?

It is installed in my “gems” folder and I have edited the environment.rb  
in “myradiant”/config/ adding the line:

require ‘will\_paginate’

at the bottom like this:

* * *

# Be sure to restart your server when you modify this file

# Uncomment below to force Rails into production mode when

# you don’t control web/app server and can’t set it the proper way

ENV[‘RAILS\_ENV’] ||= ‘production’  
ENV[‘GEM\_PATH’] = ‘/home/chainrea/gems:/usr/lib/ruby/gems/1.8’

# Specifies gem version of Rails to use when vendor/rails is not present

require File.join(File.dirname( **FILE** ), ‘boot’)

require ‘radius’

Radiant::Initializer.run do |config|

# Settings in config/environments/\* take precedence over those

specified here.

# Application configuration should go into files in

config/initializers

# – all .rb files in that directory are automatically loaded.

# See Rails::Configuration for more options.

# Skip frameworks you’re not going to use (only works if using

vendor/rails).

# To use Rails without a database, you must remove the Active Record

framework  
config.frameworks -= [:action\_mailer]

# Only load the plugins named here, in the order given. By default,

all plugins

# in vendor/plugins are loaded in alphabetical order.

# :all can be used as a placeholder for all plugins not explicitly

named

# config.plugins = [:exception\_notification, :ssl\_requirement, :all]

# Only load the extensions named here, in the order given. By default

all

# extensions in vendor/extensions are loaded, in alphabetical order.

:all

# can be used as a placeholder for all extensions not explicitly

named.

# config.extensions = [:all]

# Force all environments to use the same logger level

# (by default production uses :info, the others :debug)

# config.log\_level = :debug

# Your secret key for verifying cookie session data integrity.

# If you change this key, all old sessions will become invalid!

# Make sure the secret is at least 30 characters and all random,

# no regular words or you’ll be exposed to dictionary attacks.

config.action\_controller.session = {  
:session\_key =\> ‘\_radiant\_session’,  
:secret =\> ‘asdfqwerfxcoivswqenadfasdfqewpfioutyqwel’  
}

# Use the database for sessions instead of the cookie-based default,

# which shouldn’t be used to store highly confidential information

# (create the session table with ‘rake db:sessions:create’)

config.action\_controller.session\_store = :active\_record\_store

# Use SQL instead of Active Record’s schema dumper when creating the

test database.

# This is necessary if your schema can’t be completely dumped by the

schema dumper,

# like if you have constraints or database-specific column types

# config.active\_record.schema\_format = :sql

# Enable page/fragment caching by setting a file-based store

# (remember to create the caching directory and make it readable to

the application)

# config.action\_controller.fragment\_cache\_store = :file\_store,

“#{RAILS\_ROOT}/fragment\_cache”  
config.action\_controller.page\_cache\_directory = “#{RAILS\_ROOT}/cache”

# Activate observers that should always be running

config.active\_record.observers = :user\_action\_observer

# Make Active Record use UTC-base instead of local time

config.active\_record.default\_timezone = :utc

# Set the default field error proc

config.action\_view.field\_error\_proc = Proc.new do |html, instance|  
%{

#{html} •  
#{[instance.error\_message].flatten.first}
}  
end

config.after\_initialize do  
# Add new inflection rules using the following format:  
Inflector.inflections do |inflect|  
inflect.uncountable ‘config’  
inflect.uncountable ‘meta’  
end

```
# Auto-require text filters
Dir["#{RADIANT_ROOT}/app/models/*_filter.rb"].each do |filter|
  require_dependency File.basename(filter).sub(/\.rb$/, '')
end

# Response Caching Defaults
ResponseCache.defaults[:directory] =

```

ActionController::Base.page\_cache\_directory  
ResponseCache.defaults[:logger] = ActionController::Base.logger  
end  
end

require ‘will\_paginate’

* * *

So “will\_paginate” should be working? or am i doing something wrong  
here?

I’ve just installed comments, and it seems to work “50 %” it gets  
installed but doesn’t work - probeably becuse “will\_paginate” doesn’t  
work?

---

<div class="post-metadata">

**Author:** ![janpipek](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/b5e925/32.png) [@janpipek](https://www.ruby-forum.com/u/janpipek)\
**Post date:** [July 15, 2008, 3:54pm UTC](https://www.ruby-forum.com/t/will-paginate-and-radiant-paginate-extension/143134/2 "2008-07-15T15:54:10Z")

</div>

I don’t know what the standard radiant practice is for gem plugins,  
but for will\_paginate I think you have to install it as a plugin in  
vendor/plugins. I don’t know if the version of Rails vendor’d in  
Radiant uses the new ‘gem’ syntax.

I would love to hear differently. 🙂

---

<div class="post-metadata">

**Author:** ![janpipek](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/b5e925/32.png) [@janpipek](https://www.ruby-forum.com/u/janpipek)\
**Post date:** [July 15, 2008, 9:39pm UTC](https://www.ruby-forum.com/t/will-paginate-and-radiant-paginate-extension/143134/3 "2008-07-15T21:39:05Z")

</div>

On Tue, Jul 15, 2008 at 9:53 AM, Josh S. \<  
removed\_email\_address@domain.invalid\> wrote:

> I don’t know what the standard radiant practice is for gem plugins, but for  
> will\_paginate I think you have to install it as a plugin in vendor/plugins.  
> I don’t know if the version of Rails vendor’d in Radiant uses the new ‘gem’  
> syntax.

Seems like it would be easiest for ihoka to:

git submodule add  
git://github.com/mislav/will\_paginate.gitvendor/plugins/will\_paginate

at the root of his extension’s git repo. That way, a git submodule init  
and  
git submodule update will grab the latest version of will\_paginate from  
github and shove it in the plugins directory.

Anyone have experience with nested git submodules?

–  
Tim