Identity
Filter
Visitors
(1) (1) (1) (0) (2) (1) (0) (0) (0) (0) (0) (0) (0) (61) (0) (0) (0) (0)Subscribers
(0)
Highest posts
Latest posts
Links
Highest posts
Latest posts
You can use the system right now:
links to propose new sub elements
or 
buttons to vote against or for
an elementNo complex registration required, you can participate anonymously or just fill a pseudo (top right corner) in order to be differentiated. This pseudo can be password protected and email verified, or not. You choose.
I’m open to suggestions and follow closely everything said (every forum also being a mailing list, it’s easy to follow and answer to)!
Tell me what you think!
+8
New discussion
Answer
Hello, echarp!
I started to test a little here.
I managed to make the posting “Nice!”.
But how do I add text to that posting, or is it meant to only add new postings under int the thread “Nice!”??
A small comment, maybe the >-sign or “add” should be more understandeble by having only one link: Add posting to this thread(/level) or something?
Second question. I also managed to make some empty postings. How can I delete them?
Finally, lovely to see some action!
+2
New discussion
Answer
Can anyone help me with this error? I get it when using “rake db:migrate”
@— create_table(:choices, {:force=>true})
NOTICE: CREATE TABLE will create implicit sequence “choices_id_seq” for serial column “choices.id”
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index “choices_pkey” for table “choices”
> 0.3862s
- execute("ALTER TABLE choices ADD CONSTRAINT fk_elt_id FOREIGN KEY ( elt_id ) REFERENCES elts( id ) ")
rake aborted!
An error has occurred, this and all later migrations canceled:
PGError: ERROR: relation “elts” does not exist : ALTER TABLE choices ADD CONSTRAINT fk_elt_id FOREIGN KEY ( elt_id ) REFERENCES elts( id )
(See full trace by running task with —trace)@
+2
New discussion
Answer
It’s due to the DB schema evolutions. The schema dump is now conflicting with migrations.
I can correct that, do you use the svn version?
+1
New discussion
Answer
I retested the DB installation procedure, and corrected it.
Trying again with latest svn release should work…
+1
New discussion
Answer
-1
+1
New discussion
Answer
+3
+0
+0
+2
-1
+1
+1
New discussion
Answer
+0
-1
-1
-1
+2
New discussion
Answer
-1
-1