I have found it to be stable enough to use, even in production. However, I think you have to be prepared to patch it at the moment. I have patched it to accommodate routes, reserved SQL keywords and some other small issues.
This is inconvenient. For example I spent ages tracking down a bug and then when I looked at the current source code it had already been fixed. Due to my reluctance to update my patched copy, I am (through my choice) working with out of date source code. I suppose I should create a clone copy on google code which might makes things easier. Bear in mind that three or four of the field names will change soon because of the SQL reserved names issue. However, it is still much better than having to create your own version! There are lots of features, it is already usable and will only get better! On Feb 20, 10:52 am, sebastian <[email protected]> wrote: > Hi All > > I'm reading about plugin_wiki and it looks like a great plugin to use > in real life applications... Just nervous about what the books says: > > DISCLAIMER: plugin_wiki is still very much under development and > therefore we do not promise backward compatibility to the same level > as for web2py core functions. > > how stable is plugin_wiki ? can we consider it as in unstable state ? > is it ready for production ? > > thanks
