mmmWiki - Wiki Engine/Software (and online filesystem)
Most characteristic features (whether good or bad)
- No distributed management (like mediawiki). More like: one (1) "dictatorial" administrator can decide whether a page should be visible resp editable by others. The admin has total control and can detect any edit on multiple sites and can easily revert any edit.
- Is this non-democratic? No I don't think so, since it is supposed to be easy to set up a new wiki, visitors (editors) who feels misunderstood or rebuffed should be able to set up their own wiki or blog or whatever.
- One might say that this software is a bigger threat (competitor) to blogs/blog-software than to mediaWiki.
- Running on Node.js with MySQL database.
- Mediawiki-style syntax. See also: What wiki syntax to use
Features also found on MediaWiki
"Selling points" (The good stuff)
- Smooth fast editing/updating. (Especially for the admin)
- Multiple wikis (domains, (namespaces)) on a single implementation.
- Pretty much all the page is left to the designer of the page, no forced left-column etc. If you really want a left-column then see more at Multicolumn wiki
- Admin tools (click three times on the "Donate"-button within 10 seconds and the admin-button appears. This button will open the admin-tools):
- Elaborate File manager (Page/image lists)
- Backing up: Upload/download all pages/images to your local computer as files packed in zip-folders.
- Embed monitoring with iframes on your favorite page: Monitor multiple wikis
- Read/write access can be set on each page.
"Drawbacks" (The bad stuff)
- No user accounts, only two hardcoded passwords:
- "viewing password" for reading read-protected pages.
- "admin password" for doing administrative things (like writing to write protected pages).
- No nested templates (No templates in the templates)
- No text search.
- When renaming a page, all the links to it are not automatically renamed.
- My workaround: Before renameing you can see the parents of a page/image in the page/image lists where you manually can visit the parent pages and rename the links.
- Some administrative tasks are best done by executing raw SQL (Ex in Updating wiki software) which is why a MySQL interface is recommended. I use MySQL Workbench for excuting raw SQL.
- See also Todo (bugs) and Unimplemented stuff
- Admin/View passwords are SHA1-hashed.
- CSRF-codes are used.
- TLS (SSL):
- I'm currently using TLS with nginx
- Tested Servers: Developed primarily to work on linux/localhost and heroku.com.
- Tested Clients:
- Chrome OK
- Firefox OK
- Opera OK
- 9 and older: No editing
- Edge 12, IE 10-11: No editing *
- Edge 13 OK
- 9: No editing *
- 10: Hopefully OK (Since "generators" are working (ref), it should work)
- Android Browser: No editing
- UC Browser: No editing
* The webmaster can get most things working with this workaround
. (By disabling some administrator functionallity)
- External links of different kinds: http://example.com, mylink.
- Internal links: blabla
- Interwiki links. Ex: oak, oak
- Tables. See also: tables in nested lists
- Image examples
- Image gallery (with slide show).
- Templates: HELLO WORLD
- The iframe-tag can be used if the "Allow others to edit this page"-checkbox is unclicked;
- nowiki - tag (no wikitranslation + encoding of html special characters (
- The video-tag can be used. Ex:Video