Wagn 1.3+discussion

Migrations from English:

I removed *layout+*options because layouts don't strictly *have* to be HTML, but the other ones all look important to me. Will migrate soon. -efm

Some more complex migrations are noted at http://spreadsheets.google.com/ccc?key=tc229MGg7C_3LjsPj8F_C4Q&hl=en&pli=1

Those are all done -efm

--John Abbe.....Fri Dec 04 00:04:45 -0800 2009

Why the removal of http://en.dwagn.org/wagn/*layout+*options ? (I thought it would be nice for people to be able to point to a not-yet-existent layout and not have to set its type.)

--John Abbe.....Fri Dec 04 12:58:59 -0800 2009

layouts don't have to be HTML. if you make a non-html layout, it won't show as an option.

Other migrations are in place.

--Ethan McCutchen.....Fri Dec 04 14:40:45 -0800 2009

had already done this work, but I added this ticket for testing (and to remind us to document, and to let folks know it's here...): add inclusion comments

--Ethan McCutchen.....Sat Dec 05 14:17:41 -0800 2009

should probably update to english css on wagn's where *css was last edited by wagbot.

--Ethan McCutchen.....Mon Dec 07 20:11:33 -0800 2009

*type, *right, etc rforms need to be hardened.

--Ethan McCutchen.....Mon Dec 07 22:35:20 -0800 2009

captcha setting not taking?

--Ethan McCutchen.....Tue Dec 08 09:29:15 -0800 2009

I also took care of everything mentioned here: several weirdnesses with 1.3, though I haven't deployed those changes yet. While the 20 v. 50 issue in itself was minor, it led me to some more significant bugs related to issues identifying the main slot using our new layout system. (eg., deleting main card didn't redirect) we may yet want to do better than what I've done, but it's a start. Desperate need for better auto tests here.

If we find more newly introduced bugs, please refer to them here.

--Ethan McCutchen.....Sat Dec 05 14:21:01 -0800 2009

1. √ new built-in view content for Sets

2. √ setting subtab interface needs to handle:

√ sets that haven't been created yet (coded)
√ friendly set names
√ special interface on type cards?

3. √ make *all a normal Set? (coded, but need to migrate to change all to Set)

4. √ take Set and Setting out of createable cardtypes?

--Ethan McCutchen.....Mon Dec 14 08:37:30 -0800 2009

show correct setting labels on options subtab

--Ethan McCutchen.....Mon Dec 14 15:51:26 -0800 2009

link to set and settings cards from options subtab

--Ethan McCutchen.....Mon Dec 14 15:51:48 -0800 2009

migrate back *invite and *request mistakes

--Ethan McCutchen.....Mon Dec 14 15:41:02 -0800 2009

check on pointer autocompletes

--Ethan McCutchen.....Wed Dec 16 12:20:12 -0800 2009

On wagn.org I'm seeing a bug where I edit an existing included pointer (eg, tags on a ticket) and when I click save I get redirected to a new page with just the content of the pointer. In fact, it feels like I'm seeing lots of editing bugs. (saw another trying to submit this comment)

--Ethan McCutchen.....Sat Dec 19 14:44:31 -0800 2009

I'm seeing an error where i add a comment and it is added, but the addition doesn't render in-place, i have to reload. Is this what you saw, Ethan?

I'm seeing similar behavior not for the main card, but any included card: saving does save, but i stay in edit mode (and of course if i save again i get a conflict). Inclusions are fine when being created, this only happens when editing.

--John Abbe.....Sun Dec 20 12:44:13 -0800 2009