Small trick to see where in web2py a class lives. the 99% of imports is in
gluon/__init__.py. In your case, you are searching for auth.wiki(), so is
in auth. auth is defined as from tools import Auth, so it's in
gluon/tools.py .
The "grep way" is faster, if you have grep at hand (couldn't live without
it)
*grep -nR 'def wiki(' .*
./gluon/tools.py:3280: def wiki(self,
3280 is the line number
On Saturday, October 27, 2012 2:51:20 PM UTC+2, Simon Carr wrote:
>
> Hi Massimo,
>
> I do like auth.wiki, but I am sure there is a bug in the creation of
> links. I have logged a an issue here.
>
> http://code.google.com/p/web2py/issues/detail?id=1119&start=100
>
> I would have a look myself, but after a lot of searching, I cant even find
> the code for auth.wiki
>
> Simon
>
> On Saturday, 27 October 2012 06:27:05 UTC+1, Massimo Di Pierro wrote:
>>
>> auth.wiki is better because of integration with oembed, web2py components
>> and group based permissions. It is not documented at all yet.
>>
>> On Friday, 26 October 2012 17:47:54 UTC-5, HittingSmoke wrote:
>>>
>>> I feel like I read Massimo say somewhere that plugin_wiki will be
>>> deprecated when auth.wiki is more complete and documented but don't quote
>>> me on that.
>>>
>>> On Friday, October 26, 2012 1:57:29 PM UTC-7, Niphlod wrote:
>>>>
>>>> can't say if plugin_wiki is going to be updated further, but
>>>> auth.wiki() is embedding quite a pack of features nonetheless. If you need
>>>> more features, stick with plugin_wiki.
>>>> PS: plugin_wiki never had a WYSIWYG editor, just an editor with
>>>> shortcuts buttons for bold, italics, list, etc. Markmin evolved into
>>>> supporting nested lists, autolinks, etc, and the editor used (markitup)
>>>> hasn't catched with the new improvements. On web2py > 2.1.1 there's the
>>>> preview, though.
>>>>
>>>>
>>>> On Friday, October 26, 2012 9:30:25 PM UTC+2, Simon Carr wrote:
>>>>>
>>>>> I notice in Web2Py 2.x the index function in Default offers the
>>>>> suggestion of returning auth.wiki
>>>>>
>>>>> I was assuming that this was just plugin wiki now built into the core.
>>>>> But I notice that there is no widget option and no WYSIWYG editor when
>>>>> creating a new page.
>>>>>
>>>>> Should I continue to plugin wiki if I still want these extra features,
>>>>> or am I missing something?
>>>>>
>>>>> Thanks
>>>>> Simon
>>>>>
>>>>
--
