On Apr 28, 2010, at 2:57 PM, Henry Baragar wrote:
Kevin,
I figured out that the "skip" attribute works nicely:
<engagement-table:collection_name skip="player" />
when using the following definition:
<def tag="engagement-table">
<table fields="player match collectable ..." merge >
</def>
That is, I added both "first" columns and skip either one or the
other.
However, if I change the definition as follows:
<def tag="engagement-table">
<div part="engagement-table">
<table fields="player match collectable ..." merge >
</div>
</def>
I get the following error message:
undefined method `attributes' for #<ActionView::Base:
0x7f06a128e638>
Am I doing something wrong? Or is there a bug code generated for
the "part" attribute?
I'm not 100% sure, but there's a good chance that parts might not work
cleanly when defined inside tags like that. Alternatively, the 'merge'
on the table could be interacting with the part context mechanism. Can
you post a complete backtrace?
--Matt Jones
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
