allan-simon / tatowiki Goto Github PK

seems like it's a cookie domain issue

step to reproduce

create a new user
now you should be login (note that the bug will not appear if you log using "users/login")
try to edit or create a new article
submit the form

-> error 500

For example when going on http://fr.wiki.sysko.fr/articles/show/page-principale

we see there's no links to other main pages, though they exists in the database and can be accessed directly using their own links

with should first create a unit test and then fix the problem

it affects version 0.8.1 (maybe before)

Links should look different whether they are:
• external links
• internal links
• internal links to non-existing pages
• internal links to pages from other languages
• internal links to non-existing pages from other languages (?)

i.e when providing the 5 languages , the main pages are not all interconnected

the problems seems to come from the model's method add_translation_link.

For the moment we rely on tatoeba's css

it would be better to have our own CSS

As the wiki is going to be read more often that it is edited, it would be better to cache the page, in order to not regenerate everything everytime

This page would be used to generate the database etc.

We should have a page where you enter your previous password, and you can put a new one

2013-01-21 02:42:49; cppcms, error: Caught exception [sqlite3:database is locked]

for the moment it's certainly possible to enter things that can create a XSS threat

I have read and accepted the term of use.

term → terms

This is the default main page, you can edit it byclicking on the button on the right pane

byclicking → by clicking

in a first time, restrict all the "edit" actions to registered users

reproduction steps:

1. deploy tatowiki on a remote server, port 42000
2. try to connect from another host
3. notice "connection failed"
4. create a ssh tunnel between localhost:41000: and remote:42000
5. try and connect to localhost:41000
6. notice that the connection is established

config.js
{
"service" : {
"api" : "http",
"port" : 42000
},
"cache" : {
"backend" : "thread_shared"
},
"http" : {
"script_names" : ["/TatoWiki"]
},
"localization" : {
"messages" : {
"paths" : [ "../locale" ],
"domains" : [ "tatowiki.dodges.it" ]
},
"locales" : [ "en_GB.UTF-8", "fr_FR.UTF-8" ]
},
"session" : {
"expire" : "renew",
"timeout" : 604800,
"location" : "server",
"server" : {
"storage" : "memory"
}
},
"TatoWiki" : {
"interfacelangs" : [
["en" , "en_GB.UTF-8", "English"],
["fr" , "fr_FR.UTF-8", "Français"],
["de" , "de_DE.UTF-8", "Deutsh"]
],
"languages" : [
["en" , "English"],
["fr" , "French"],
["de" , "German"]
],
"sqlite3" : {
"path" : "../data/sqlite6.db",
"source" : "./sql/sqlite3.sql"
},
"baseHost" : "tatowiki.dodges.it:42000"
}
}

As actually there's not really translation of each other but rather articles about the same subject , but in different languages

Rather than being a "hack" with the mardown format (like mediawiki does) it should be better to have "same article in different languages" link as something separate, so that it will be easier to make manipulation on this latter (like looking for popular articles not yet having a XXX language version)

for example if two people have created a page about the french language , we should be able to link them

Extend the markdown syntax, maybe like this:
• Add article titles slugification and allow [[page name]]
as a short for [page name](page name)
• [[page name/eng]] to do link to pages from other languages
• Disallow parenthesis or other characters that could mess up with
the link syntax in article names.

Almost all items are not translated

• “incorrect password”
• "history"
• "edit"
• "translate"
• "translated in"

http://qdii.dodges.it/logintato.png for an example

Note: it may be interesting to not really delete articles but to rather move them and their history / discussions to a "hidden place" (in case the delete was a mistake, or after discussion we discover that a previous version of the article was "acceptable)

Going to http://de.tatowiki.dodges.it:42000/articles/translate/whatever_that_does_not_exists
should bring an error.

In a first time only between the current one and a given one, but if we make it enough generic, to have version X vs version Y would simply be a "link" problem

time 1 - A edits the page XXXX
time 2 - B edits the same page
time 3 - A save the modification
time 4 - B save the modification -> he should get a message telling him that a modification has been while he was editing

Of course the best would be to tell him at the time 2 , but locking the page means to know when to unlock it, which is very hard to know (what if the browser of A crash, if he closes the page etc. the page would stay locks , and putting a timer to unlock a page would cause additional problem, what if A is still editing when its locking timer expire etc.)

For the moment we store the history of an article but we're not able to see it
Add a page to see it

For the moment there's no way from the interface to access to it
In a first time, a simple link at the top, next to logout would be enough

Though people are not supposed to arrive on such a page, the 404 error should be pretty looking and contains link to go back on "normal" pages

register
login
logout

Instead we should return to the form page with an error page explaining what's wrong

I.e if you have an article in english, you shouldn't be able to translate it in english.

for example, i wanted to edit a page, I'm redirected to login, once logged I should be redirected back to the page i wanted to edit

the server logs

2013-01-18 23:03:39; cppcms, error: Caught exception stoi

Note that the page was added in the database despite the error.

The title of the article was:

Awesome page

The text of the article was:

#AWESOME PAGE

#cool page

[ma page trop cool](http://www.qdii.fr)
elle est **super** !

This way users don't need to search to find where to create a new account

i.e /articles/show/ (and nothing more)

Make it looks more like http://en.wikipedia.org/wiki/Special:RecentChanges

It would be more convenient to have on one page the last activities on the wiki, in order to ease collaboration (translation/correction of newly added articles, detection of spam etc.)

CMakeLists.txt has references to files that are not present in the repository.

• tests/models/articles/add_translation_link.cpp
• tests/models/articles/articles.cpp

EDIT: those files are being deleted when "make clean" is run.

Or at least not with "show previous version page" as it's misleading to display the current version with a text saying it's a previous version ...

For the salt, maybe generating it automatically at the first launch would make it easier to not "commit" it by mistake