Mailing List Archive

Error: Can't use string ("right") as a HASH ref
Folks,

On v1.11.1, I attempted to add an "alignment" custom field to a "Pull
Quote" subelement with the attributes "left" and "right." It returned
the following error, and does so every time that I attempt to edit it:

---cut---
Can't use string ("right") as a HASH ref while "strict refs" in use
at /usr/local/bricolage/comp/widgets/profile/displayFormElement.mc
line 214, <GEN39> line 929.
---cut---

Details are pasted below. I want to figure out how to get past this,
but I don't know where subelements live. I can't find it in the file
system, and mucking around in the database—the element_* and
subelement_type tables—I can't seem to find where subelement
attributes would be recorded, although it does seem like they should
be in here somewhere. Any suggestions as to how to get past this
little hurdle?

Best,
Waldo



ERROR DETAILS
Fault Class HTML::Mason::Exception
Description generic base class for all Mason exceptions
Timestamp 2009-10-29 16:54:44.000000
Package HTML::Mason::Exceptions
Filename /usr/lib/perl5/site_perl/5.8.8/HTML/Mason/Exceptions.pm
Line 129

STACK
Can't use string ("right") as a HASH ref while "strict refs" in use
at /usr/local/bricolage/comp/widgets/profile/displayFormElement.mc
line 214, line 92

Stack:
[/usr/local/bricolage/comp/widgets/profile/displayFormElement.mc:214]
[/usr/local/bricolage/comp/widgets/profile/displayAttrs.mc:63]
[/usr/local/bricolage/comp/admin/profile/element_type/dhandler:323]
[/usr/local/bricolage/comp/admin/profile/autohandler:16]
[/usr/local/bricolage/comp/autohandler:7]
Re: Error: Can't use string ("right") as a HASH ref [ In reply to ]
Waldo Jaquith wrote:
> Folks,
>
> On v1.11.1, I attempted to add an "alignment" custom field to a "Pull
> Quote" subelement with the attributes "left" and "right." It returned
> the following error, and does so every time that I attempt to edit it:

That sounds like a bug in the form element code although the code looks
right in my version of displayFormElement. Since that line just deals
with flagging whether it's a required field or not, you could comment it
out temporarily and you should still get the element definition so you
can do some more testing on what's wrong. Pulldowns work fine for me
with 1.11.1 - latest master.

regards,

Paul