Thanks for the quick reply, Chris.  That site's sure to be very
helpful!

I couldn't find any particular text on text nesting issue--but it
turns out I had unwittingly created a new line of text at some
point...so replacing the file with the original copy fixed the
problem.  Thanks again!

On Feb 22, 6:32 pm, Chris Lee <[email protected]> wrote:
> Haml often gives the wrong line number for errors. Though I can't tell 
> exactly due to wrapping, but I suspect the problem is not at the line you 
> provided. You may want to double check the 3 Illegal Nesting errors this 
> article mentions:http://nex-3.com/posts/74-haml-errors-suck#comments
>
> Otherwise, you can paste your entire file into pastie and it may be easier 
> for everyone to see the indentations.
>
> - Chris
>
> ----- Original Message ----
> From: jrgoodner <[email protected]>
> To: CommunityEngine <[email protected]>
> Sent: Sunday, February 22, 2009 8:16:00 PM
> Subject: [CommunityEngine] Uploading Profile Photo: "Illegal Nesting"
>
> When I attempt to upload a profile photo, I get an Illegal Nesting
> (within text) Haml Syntax Error in line 19 of views/users/
> edit.html.haml:
>
> = render :partial => 'shared/location_chooser', :locals =>
> {:selected_country => @user.country_id, :selected_state =>
> @user.state_id, :selected_metro_area => @user.metro_area_id, :states
> => @states, :metro_areas => @metro_areas}
>
> Has anyone had this issue before?  I also have the same issue (Illegal
> Nesting) whenever I try to render views/shared/
> _location_chooser.html.haml...I have little experience with Haml, so
> perhaps there's an easy answer?????
>
> Thanks for everything!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" 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/communityengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to