process markup on items in forms that are Pointers

Looks like we fixed this today.

nice. love it when clean-ups take care of edge case messes :)

--Ethan McCutchen.....Tue Jan 25 17:27:18 -0800 2011

Actually, I thought this was the one you told me about related to searches in "closed" mode. Same thing here, but a pointer.

I added a "Tests" tag to remind us we need to have a test case for it. Or did I do that? Well we should make suer anyway.

--Gerry Gleason.....Tue Jan 25 19:39:38 -0800 2011

no, wait. heh, this is not fixed; it's a byproduct of rendering the content forms we're not supposed to render. though the render_raw thing might fix it....

--Ethan McCutchen.....Tue Jan 25 19:52:16 -0800 2011

Well, we're now showing pointee rather than

, because we're just providing the raw view. My take is that we should close this ticket (and untag the release), even though the solution suggested above isn't implemented. Instead, we should ticket something like improve form creation experience and start to work out the design details of how that looks there.

--Ethan McCutchen.....Thu Jan 27 01:16:08 -0800 2011

Oh, I think this is because we no longer to the "is_collection" processing in expansion. It is commented out, and each time I see that, I wonder where it belongs. Maybe in process_content.

Tests for this would be nice. I thought we had some, so I'm a little unclear on what the actual test case is. This may be one of those cases where we have multiple paths an we shouldn't.

--Gerry Gleason.....Thu Jan 27 02:30:35 -0800 2011

Oh, this is the edit case for pointers. Now I get it.

--Gerry Gleason.....Thu Jan 27 02:32:12 -0800 2011

I'd like to leave this open for now, just to make sure we attend to how it looks when this release goes out...

--John Abbe.....Thu Jan 27 11:54:50 -0800 2011

ok, then I'll switch to testing, because I think we've finished working on this piece.

--Ethan McCutchen.....Thu Jan 27 12:35:04 -0800 2011