liquid_feedback_core
annotate README @ 9:4af4df1415f9
Version beta10
Voting will be skipped, if no initiative is admitted for voting
Invite code feature allows people having an invite code to create one account
Contingent system to limit the number of initiatives or text entries to be submitted by each member within a given time
Ability to store a formatting engine for each draft, which can be used to allow initiatives to choose between available wiki parsers
New table setting storing user settings for the frontend (replaced hidden_hints column of beta9)
Better policy support:
- New table allowed_policy to select which policies can be used in each area
- Policies are now ordered by an index field
Bugfixes:
- In function close_voting(...): If there were no voters, this resulted in a NULL value as positive and negative vote counts
- In delete_private_data() function: Secret fields of member table are now deleted too
- Major bug fixed in lf_export, which caused data loss on execution
Voting will be skipped, if no initiative is admitted for voting
Invite code feature allows people having an invite code to create one account
Contingent system to limit the number of initiatives or text entries to be submitted by each member within a given time
Ability to store a formatting engine for each draft, which can be used to allow initiatives to choose between available wiki parsers
New table setting storing user settings for the frontend (replaced hidden_hints column of beta9)
Better policy support:
- New table allowed_policy to select which policies can be used in each area
- Policies are now ordered by an index field
Bugfixes:
- In function close_voting(...): If there were no voters, this resulted in a NULL value as positive and negative vote counts
- In delete_private_data() function: Secret fields of member table are now deleted too
- Major bug fixed in lf_export, which caused data loss on execution
author | jbe |
---|---|
date | Thu Dec 10 12:00:00 2009 +0100 (2009-12-10) |
parents | e6faf5ff83af |
children | 92fc60ed705d |
rev | line source |
---|---|
jbe@0 | 1 |
jbe@0 | 2 Setup the database: |
jbe@0 | 3 $ createdb liquid_feedback |
jbe@0 | 4 $ psql -v ON_ERROR_STOP=1 -f core.sql liquid_feedback |
jbe@0 | 5 |
jbe@0 | 6 Optionally insert demo data: |
jbe@0 | 7 $ psql -v ON_ERROR_STOP=1 -f demo.sql liquid_feedback |
jbe@0 | 8 |
jbe@0 | 9 Compile lf_update binary: |
jbe@0 | 10 $ make |
jbe@0 | 11 |
jbe@0 | 12 If you wish, copy the created lf_update file to /usr/local/bin or a |
jbe@0 | 13 similar directory. Ensure that "lf_update dbname=liquid_feedback" |
jbe@0 | 14 is called regularly. On successful run, lf_update will not produce |
jbe@0 | 15 any output and exit with code 0. |
jbe@0 | 16 |
jbe@0 | 17 NOTE: When writing to the database, some INSERTs must be executed |
jbe@0 | 18 within the same transaction, e.g. issues can't exist without |
jbe@0 | 19 an initiative and vice versa. |
jbe@0 | 20 |
jbe@8 | 21 To create an export file, which is containing all but private data, |
jbe@8 | 22 you may use the lf_export shell-script: |
jbe@8 | 23 $ lf_export liquid_feedback export.sql.gz |
jbe@8 | 24 |
jbe@0 | 25 To uninstall the software, delete the lf_update binary |
jbe@0 | 26 and drop the database by entering the following command: |
jbe@0 | 27 $ dropdb liquid_feedback |
jbe@0 | 28 |