Wagn administration includes maintaining an installation of Wagn on a server, and tasks within a Wagn generally managed by people with the Administrator role.
The Administrator+links card is a good place to add information and links and information. Only Administrators can see it by default.
Also see:
Clearing the cache
Problems with the cache can result in people seeing different content on the same from different accounts, or even seeing different content from the same account at different times. To clear the cache, go to:
(your Wagn's base URL)/admin/clear_cache
Spam
captcha can protect against most non-human spam.
If you get an overwhelming number of obviously spammy Sign up, you show them all in open view and thus easily deny them all with a link like this: http://wagn/org/Account_Request+*type+by_update?item=open
Upgrading
Standard Upgrade
1. Backups
Always back up your database and uploaded files.
2. Update Libraries
From your decko root directory run:
bundle update3. Update Database
Run the following:
decko update4. Restart your server.
Upgrade to Decko from Wagn
1. update references to “wagn” in file content
In your decko's root directory, edit Gemfile, config/application.rb, and config/routes.rb, and script/wagn, replacing “wagn” with “decko”. (Keep the same capitalization pattern.)
2. update references to “wagn” in file names.
From your decko root directory run:
mv script/wagn script/decko3. continue as with Standard Upgrade
See above.
If your Wagn was NOT installed from a gem, then first check the Wagn version of your existing installation:
For version 1.10 through 1.12.6
- Create a new Wagn app using steps 1 and 2 from the installation section above.
- Copy config/database.yml from the old site to the new one.
- Copy the old local/files contents to the new files directory.
- If you have edited config/wagn.yml in your old site, make the corresponding changes to the new config/application.rb file.
- Follow the standard upgrade procedure above.
Upgrading pre-version 1.10
First update your Wagn to version 1.10 via the old update mechanisms, and then follow the directions above to then upgrade to the wagn gem.
Tickets related to administering Wagn
Development Tickets (by status)
Ideas
Documentation Tickets
Support Tickets
support skinsadd Google Analytics supportstandardize special card namesinclude configuration card on installimprove administrability of permissionsclean up role and user setup on installmove most configuration options into cardsadd content to account request emailsadd role, member, editor to Related tabremove link from default tinyMCE setupimplement initial setup for new Wagnrespect inclusions in star-invite-plus-star-subjectway to generate lists of account emailsmigrate in contents of *account cardinterpret spaces in *home as underscoressimple pattern settingsimplement read-only modeallow access to other files and CGIs on the serverhard-code main page to "Home" if no *homesupport deleting old sessions