HI Ignacio,
Yes, documentation of the 406 error would have saved me several days of
frustration. That is all it would take for future users, too. We don't
really have to change the code so long as the developers can find it
with a web search.
Thanks,
Don
On 09/14/2013 02:31 AM, Ignacio Huerta wrote:
Hi Donald,
I'm glad you solved your issue :). About the error response, that's a
nice idea, though the current error means "You have not provided an
acceptable format to hobo_show". If you take a look at this page
-http://www.hobocentral.net/manual/controllers- you will see that when
you pass an argument to the block, this is what Hobo is expecting:
hobo_show do |format|
format.pdf { render foo }
end
What if we add to the docs something like: "If you pass an argument but
you don't provide a "format.XXX" line, you will get a Completed 406 Not
Acceptable error".
This might help future users when looking though Google. What do you think?
Regards,
Ignacio
El 13/09/13 18:51, Donald Ziesig escribió:
Hi!
Well I got the popup working using js, but the interaction with hobo
drove me crazy! I kept getting "Completed 406 Not Acceptable" errors,
and all of the leads I followed were dead ends. The only thing left
after hacking away was the changes I made in the edit controller for the
show and update methods. Both of them were edited as follows:
def show
hobo_show do |elem|
# some code
end
end
and
def update
hobo_update do |elem|
# some code
end
end
The problem still existed when the intervening block was empty. Note, I
put the block argument |elem| in by force of habit. When I removed it,
what ever was causing the 406 error went away and what was left of my
app after three days of hacking, fumbling and beating my head against
the wall worked. The code should look like this:
def show
hobo_show do
# some code
end
end
and
def update
hobo_update do
# some code
end
end
For the sake of future users, if it is possible to detect the presence
of the block argument in the code and warn the user it will save some
poor developer many headaches.
Now, back to undoing all of the hacks -- thank heaven for git. ;-)
Don Ziesig
On 09/12/2013 11:39 AM, Donald Ziesig wrote:
Hi Ignacio!
Unfortunately, the invocation is via a redirect_to because this is not
a standard hobo control flow. I don't have access to the code that
actually shows it (and it comes from two vastly different places in
the code as well, one being javascript, the other standard hobo/rails).
I need something that changes the <page></page> code.
I tried
<def tag="edit-page" for="Client">
<page merge popup="true"
just for the heck of it, but that had no effect.
From the looks of it, Rails 3 has deprecated the old easy way of
implementing popups in favor of NO popup support.
I'm really hacking this one :-(
Don
On 09/11/2013 04:40 PM, Ignacio Huerta wrote:
You could use something like:
<edit-link: target="_blank"/>
This should make the edit link open in a new tab.
Regards,
Ignacio
El 11/09/13 22:34, Donald Ziesig escribió:
Hi All!
I need to open a slightly modified version of the edit page (could be
any page, but need edit for now). I have the page working properly
except that it overwrites the previous page, which hoses the flow of
the
app.
Is there any way of introducing the :popup=>true flag that rails
provides into the hobo tag?
Thanks,
Don Ziesig
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.
