edit_html permission removed at 0.10
false
<-->
Home Recent
Request an Invitation Sign in
Page Release

Overview

Theme: No More "Wagn the Dog"

Date: 2008-07-26

 

Wagn 0.10 is faster, cleaner, and features some significant enhancements to our formatting system.

 

Point releases:

 

New Features

 

Bug Fixes

See closed tickets for details.

 

Tickets

Remaining (tickets here after release are targets for next point release.)

(2)
Multi-edit on non-formatted cards referencing current card and parts in inclusions

 

Completed

(46)
always clear the cache when updating a wagn Cardtype cardtype formatting forms and cardtypes allow contextual right-side in links and inclusions stop hanging Wagn on long saves install default TinyMCE settings making renaming clear card cache for old name fix create card permissions checking replace visible text on inclusions of no-permissions cards remove edit html from global permissions searches on sidebar break account pages migration skipping under rails 2.1 fix links to *template cards on migration layout and editing bug with large images Busted self left right in WQL gather more info from invitation requesters handle very looooong urls static landing pages script cards transclude content before call referencing card names in links

 

Upgrade Notes

 

Typical upgrade procedure for svn users:

  1. svn update
  2. sudo gem install ruby_openid
    sudo gem install cached_model
  3. rake db:migrate
  4. rake tmp:cache:clear
  5. restart mongrel

If you've set up a cache other than default file cache, you'll need to reset accordingly for step 4.


Templates renamed

What we were calling templates are now called forms, and we gave the two types separate names — that is, we ended use of +*template and replaced it with +*tform for type forms, and +*rform for right forms. See formatting.

 

Permissions

Once again it's a good time to review your permissions settings-- especially create permissions on cardtypes-- You may want anyone to create Basic and custom cardtypes, but you'll typically want to restrict creation of Script,Ruby,HTML, and perhaps Role and User as well.

 

 

 

Discussion

Page