+Theme
Friendly Settings

+Date

+Blurb

Wagn is the wiki way to organize.  Our Wagn 1.3 release introduces Setting on any Set of cards, including layouts, table of contents, edit help, and captchas.

 

Have you ever noticed how many different kinds of configurations you have to learn to manage a website?  Or how every different configuration comes with its own set of rules?

 

Wagn hasn't been all that different from most wiki and CMS applications in this way.  Some configurations (like layout) applied to the entire site, some (like table of contents) to a single card, some (like autoname) to a specific type of cards, etc.  Learning to "Wagneer" meant learning the boundaries of each setting.

 

Our new Wagn 1.3 changes that by taking advantage of our everything-is-a-card approach.  Now any Setting can be applied to any Set of cards.  The set of cards can be as inclusive as all cards or as narrow as just one card, so you can be as general or as specific as you like.

 

Take layouts for example. When we introduced custom layouts in 1.2, you could only change the layout for the entire site.  Now you can apply layouts to any set of cards.  So I can a special layout for all User cards, or all cards ending in +address, or for that one card with the huge image.  This means you can now create special areas of your Wagn site for administrators or any other role.

 

In Wagn 1.3 we're introducing the first round of Set and Setting by converting several of the simplest site configurations into Wagn's new system.  Captchas, edit help, tables of contents, autonaming, and several pointer configurations (like input type and options) are now all controlled by settings. In the process, almost all of those settings became more powerful.  For example, you can now specify the minimum number of headings needed to autogenerate a table of contents --- for any set of cards!

 

If you want to try these new settings out, click on the "Options" tab on any card, and then click on the "settings" subtab.  (Sandbox.wagn.org is a great place to try out new features).  There you'll see the current settings for that card.  If you open any given Setting, you can see all the Set that the card is in and change the setting value as narrowly or broadly as you like.

 

These few settings are just the beginning.  In coming releases we'll be converting all kinds of card configurations into Setting cards, from favicons to formatting to permissions.  Not only will this greatly increase your power as a Wagneer, but it will also make it easier for wagn developers to create elegant interfaces for controlling this elegant settings sytem.

 

 

  • The raw view no longer works at all (it's been deprecated for a while; use naked to get the effect raw used to give).  it will be reintroduced with its intended meaning in the next release. See http://www.wagn.org/wagn/views
  • Due to layout changes, we have changed the names of some things in CSS:
    • page-left is now primary
    • page-right is now secondary
    • ...
  • many configurations have been patternized

 

+tickets by status

open

in progress

coded

testing

closed

 

 

We still need to

  • cancel of missing should return to missing
  • fix redirection after creating new cards?

 

Migrations from English:

http://en.dwagn.org/wagn/*all+*table_of_contents

http://en.dwagn.org/wagn/*table_of_contents+*rform

http://en.dwagn.org/wagn/*table_of_contents+*edit

http://en.dwagn.org/wagn/*layout+*rform

http://en.dwagn.org/wagn/*layout+*edit


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


error messages (on invalid card submission)

 

Found a problem here. Go to http://test.dwagn.org/Home and sign out, then click on "Add add more cards" and try to Create. The captcha comes up, and when you fill it out you get:

 

Denied!

for card add more cards: anon, You don't have permission to edit this card.

Sign in or Sign up

403 Forbidden

 

 

  --John Abbe.....Tue Dec 22 06:23:10 -0800 2009


Redirection after creating new cards is broken on ang and pinz. You see the new card rendered, but without reloading the page (i.e. there' still the "New Card" header, and card creation instructions).

http://test.dwagn.org/card/new

http://wagn.org/card/new

  --John Abbe.....Wed Dec 23 18:30:40 -0800 2009


the denied problem we decided to bail on for the release because it only comes up if you have create permission and not edit permission AND the card you're trying to create exists in the trash.

  --Lewis Hoffman.....Mon Dec 28 15:04:03 -0800 2009


why i cant update and download @ACEX?

  --Anonymous (Not signed in).....Sun Jun 06 03:04:43 -0700 2010


@ACEX v243 do not vork

  --Anonymous (Not signed in).....Sun Jun 06 03:06:07 -0700 2010