Max length for params?

Rails
1

<%= link_to “Edit”, :controller=>“new”, :action=>“index”, :edit=>true,
:req_id=>"#{@posts.first.requirement_id}",
:title=>"#{@posts.first.title}", :tags=>"#{@posts.first.tags}",
:description=>"#{@posts.first.description}",
:justification=>"#{@posts.first.justification}" %>

I have that link that sends params… i use the params to populate
textareas. It works fine for a while, but when I put a large amount of
text, there is some sort of error. From what I can tell, it can’t find
the page (maybe the url gets messed up with a large amt of params?)

Any suggestions?

Thanks

2

Justin To wrote:

<%= link_to “Edit”, :controller=>“new”, :action=>“index”, :edit=>true,
:req_id=>"#{@posts.first.requirement_id}",
:title=>"#{@posts.first.title}", :tags=>"#{@posts.first.tags}",
:description=>"#{@posts.first.description}",
:justification=>"#{@posts.first.justification}" %>

I have that link that sends params… i use the params to populate
textareas. It works fine for a while, but when I put a large amount of
text, there is some sort of error. From what I can tell, it can’t find
the page (maybe the url gets messed up with a large amt of params?)

Any suggestions?

Thanks

In IE7: res://ieframe.dll/dnserrordiagoff.htm
FF can handle more than IE7, but eventually it gets messed up.

Thanks

3

On Aug 14, 1:25 pm, Justin To [email protected]
wrote:

Any suggestions?

Thanks

Posted viahttp://www.ruby-forum.com/.

There’s a limit to how much you can stuff into a GET request.

But you don’t need to send all that data, since it’s all coming from
models anyway. Have your edit action prefill your form based on the
@post data. You just need to send the @post.id, and your controller
can figure it all out from there.

Even better would be to go with a RESTful approach if possible - it
would help clean up the logic even further, I believe.

Jeff

REST with Rails
Oct 4, 2008
Austin, Texas
http://www.purpleworkshops.com/workshops/rest-and-web-services

4

<%= link_to “Edit”, :controller=>“new”, :action=>“index”, :edit=>true,
:req_id=>“#{@posts.first.requirement_id}”,
:title=>“#{@posts.first.title}”, :tags=>“#{@posts.first.tags}”,
:description=>“#{@posts.first.description}”,
:justification=>“#{@posts.first.justification}” %>
Whenever you see something like this in your code, it should be taken as
a big red flag telling you that you’re probably doing something wrong
(or the hard way).

What’s going to happen in 6 months or a year when you, or someone else,
has to decipher this code to figure out what it’s supposed to do? The
beautiful thing about Ruby on Rails is that, when written properly, the
code can be understood in a glance. At least that’s the goal anyway.

Jeff C. wrote:

On Aug 14, 1:25�pm, Justin To [email protected]
wrote:

Any suggestions?

Thanks

Posted viahttp://www.ruby-forum.com/.

There’s a limit to how much you can stuff into a GET request.

But you don’t need to send all that data, since it’s all coming from
models anyway. Have your edit action prefill your form based on the
@post data. You just need to send the @post.id, and your controller
can figure it all out from there.

Even better would be to go with a RESTful approach if possible - it
would help clean up the logic even further, I believe.

Jeff

REST with Rails
Oct 4, 2008
Austin, Texas
http://www.purpleworkshops.com/workshops/rest-and-web-services