similar to: reversing paginated lists, linking to last page from controller

Hi, I am looking for ideas on how to remove the last item from a paginated page when a new item is inserted, thus leaving only 10 elements on the page. Currently I have a form that inserts with AJAX, but as expected, each post added to the page just increases the number of posts leaving 11 on a page that should only be displaying 10. I have unique ID''s for each post (e.g.

Using Ferret for searching, I''ve got results that I need to link to. Which is fine, except for that they''re displayed on paginated pages using Rails paginate function - so it''s not like I can''t get it from the database or anything else. Anyone have any ideas on how to go about this? It''s not so much a coding problem as a theory problem, and I

The built-in Rails pagination is fairly limited...you pass in the model name, and optionally some conditions, and it generates a paginated query for you. This gets to be very bad if you''ve got any custom queries. class Company < ActiveRecord::Base def complete_videos Video.find :all, :conditions => "company_id=#{id} AND status=''complete''", :order

I''m just getting my hands dirty with caching. The pages I want to cache have some user specific data on them (for example "log out"). That sent me down the route of fragment caching. One of the things I want to pagination is a paginated list. My question is how is pagination and query strings handled with fragment caching? Does each page get its own fragment and query string

Hello, I want to know how can I paginate a set of records. It seems there is no direct way of doing this, and I am not able to understand the documentation of paginate, so any pointers on how to do this will be much appreciated. To be specific what I want is that the records returned by user.recipes, the recipes of the particular user be paginated. My attempt to do this failed because

hi i know i can do: @customer_pages, @customers = paginate :customers, :per_page => 8 but these customers have helpdesk calls which are child records. I hoped i could do something like paginate customers.calls, but dat doesn''t work what is the best way to get a paginated list of child records? remco -- Posted via http://www.ruby-forum.com/.

Hey all, I''m building a photo album site (for fun) and have a few questions. 1) This site will have a browse section, where you can view the photos by thumbnail. I want to let the user change how many thumbs they can see per page. I''ll have a couple links at the bottom of the page letting them do that. The problem is, if they are in the middle of browsing and decide to

I''m using will_paginate in a Post class method; [code]def self.list(page) paginate :per_page => 10, :page => page, :include => :user end[/code] I can happily use the method on my posts controller index action; [code] class PostsController < ApplicationController def index @posts = Post.list(params[:page]) respond_to do |format|

I am using a smallint database column to store several boolean flags. The flags are accessible thru facade column accessors. I''d like to hide the database column so all access is thru the facade accessors. How do I do it? TIA, Jeffrey

Hi, Why can''t I use a variable to specify the :per_page attribute when using the most basic form of pagination? (if I use a hardcode number, it runs) What did I do? Thx. My code: def list_orders page_size = 20 ... order_pages, @orders = paginate(:orders, :per_page => page_size) end My Errors: undefined method `>'' for false:FalseClass RAILS_ROOT:

Hi - I''ve just started working with Rails, having come from a Cold Fusion background. I''m curious how best to deal with a huge result set. For example, I''m building an app that contains users. I''ve used scaffolding to setup my initial pages for CRUD operations on users. All that is great. The problem is, I''m going to end up with 1000+ users in

I put everything in a pastie to make it a bit more readable: http://pastie.org/593379 This is the gist: Will_paginate doesn''t play quite nice. The first result set is fine, and when I click on one of the paginated links, it returns the following error: Couldn''t find DictatedExam with ID=filter_widget observe_field triggers filter_widget which calls the paginated search.. Which

Hi, I have @result_pages and @results obtained from paginate in an action. I want to show the pages as 1 | 2 | 3 | 4 > The fifth page will show: < 5 | 6 | 7 | 8 > and so on. How exactly do I render the paginator to give this effect? I guess I will have to use pagination_links_each. But being new to Rails, I need help. Thanks, Yash -- Posted via http://www.ruby-forum.com/.

Hi all, I''d like to output some nicely formatted reports in a rails app. I''ve done a bit of research, found the jasperreports bridge (java eeeww), and datavision bridge (not quiet what I was after). I guess has anyone else found any great tools / utils to either do something like flash paper or perhaps something else to generate paginated / print friendly reports? If not

def show_details @sd_ticket = ServiceDeskTicket.find(params[:id]) @servicedesk_cis = @sd_ticket.service_desk_cis end What I need is a pagination for @servicedesk_cis using the custom pagination..How can i give offset and limit to this? I have successfully done previously custom pagination in another def as below def search_sd_ticket @search_sd_ui_hash=params[:sd_ticket]

Hi all, I'm new to the list but I've been using markdown for a while and I wonder if it might make the things I've been doing recently easier if I could find a tool that does what I need. Essentially, I've been writing a lot of technical proposals of late (mostly using google docs), but I'd like to switch to writing them in Markdown (which handily means I can track revisions

hi everybody, i am new to rails.. plz clear my doubt... this is my question In my table(public_topics), i have 11 rows of data.. whenever i run the following view, it shows the entire rows in the current page.. and i have set the '':per_page'' option to ''2''.so it must show two data per page..but it shows all the rows in a single page..and this case continue

How come I allways immediately run into difficult stuff when I''m trying some new programming language? Am I blind for the simplicity of Ruby/Rail, which a see must be there? Anyway, don''t try and answer this rhetoric question. I have got another one for you, seemingly difficult. I''m struggling with a n:m relationship (in a database, that is) and its join table.

I''m a beginning programming using ActiveRecord outside of Rails to do conditional processing of database records. So far, I''ve been successful. However, my script loads all matching records into memory first. There are hundreds of thousands of matching records so the script quickly consumes over 500MB of RAM before any processing is done. Is there a way to avoid this preloading

Hi there, I''ve been trying to paginate over a list of members that all share a tag in common using the acts_as_taggable plugin. The regular way of paginating over a collection doesn''t seem to work with acts_as_taggable. Here''s what my method looks like that takes in a tag name, finds all the members that share the tag and then displays all the members. Nothing too fancy