Hi Alan, On a general note (for future consideration), it is useful to have some records in markmin and others in html. To achieve this I think we really need to add a 'render_type' field to accompany the raw data. Then we can really mix it up.
In one implementation, I also added an option for mixed Html and Markmin. Admittedly this is 'Frankenstein' data, but it still renders well. With an extra bit of work from say Beautifulsoup, you would never know! I know many will think this is too ugly, but in some cases we do have some very ugly content originating from various places but still wish to view it as best we can with a minimum of remedial work. IMO the "on/off switch" for Html does not provide enough flexibility for this, but a few alterations could make it so. Best wishes, D On Wednesday, May 22, 2013 6:58:00 PM UTC+1, Alan Etkin wrote: > > Also as this maybe important. In my init/model/db.py I have the >> following after auth tables are defined: >> > auth.wiki(resolve=False) >> > > The auth.wiki method arguments set the Wiki object options the first time, > and further configs must be changed with the auth.settings.wiki.option > syntax. render="markmin" is the default option and AFAIK is not updated > once it was created in the model. Try auth.wiki(resolve=False, > render="html"). That should solve the problem. > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
