2002/03/01 23:08 GMT (via web):
I'm trying to tweak Zwiki on a number of levels (just trying to push and pull and see what I can do). But I only seem to know enough so far to get myself into trouble (no biggie, I'm learning).

Anyway, I thought I'd make some changes in Parents.py (I'm going though all the code to make it XHTML and use style sheets for everything). I was going to change all the .big.big.big.strong. thing for the page title to .h1. I did this, but it doesn't show in my Zwiki site. Do I have to do some sort of "refresh"?

Also I was looking for where Zwiki adds the .html. and .body. tags into every page. I need to get rid of this since my standard wiki header and footer already have tags.


2002/03/03 18:15 GMT (via web):
I use strict validated XHTML and CSS2 for all my coding. ZWiki definetly does not.

ZWiki provides you with a "footer" and "header" concept, but then sticks extra html and body tags in the document BEFORE it renders the header and footer! I am not sure how to fix this. A grep through the Zope product directory shows no extra html and body tags. I am stumped.

Try validating the source for ZWiki's FrontPage by clicking the following link: .

The problem becomes a little more clear when trying to validate my custom wiki through the same validator by clicking the following link: .

Just view source on any ZWiki page and witness the nasty html. Extra html and body tags - no doctype, etc. How can I help get this in shape. I NEED this to work :]

See?


2002/03/04 03:05 GMT (via web):
I've also noticed the unwanted extra tags in ZWiki, and belive I have discovered a way to remove them. I've only tested this with the default structured-text wiki pages with Zope 2.4 and above.

For structured-text wiki pages extra tags are inserted by the structured-text parser used. The StructuredText module included with Zope does not pass the header keyword arguement, and thus when the source is rendered it assumes the default which is to add aditional html and body tags. I assume that when the module was created if the author wished to pass keyword arguements from a dictionary it required using the apply function, and the choice was made not to use apply. Python 2.0 added the ability to pass keyword arguements using a dictionary by prefixing them with a double astrik. So....

Edit the ZWikiPage function _structured_text in the else: block used for Zope 2.4
from: text = str(StructuredText.HTML(text,level=3))

to: text = str(StructuredText.HTML(text,level=3,header=0)) # passing header so as not to include extra html formating

Now edit StructuredText/__init__.py
from: def HTML(src, level=0, type=type, StringType=type('')):

to: def HTML(src, level=0, type=type, StringType=type(''),**kw): # adding ability to grab extra keyword arguements

from: return ClassicHTML(src, level)

To: return ClassicHTML(src, level,**kw) # passing extra keyword arguements on

restart Zope and your pages should no longer have extra html and body tags in your documents.


2002/03/04 05:21 GMT (via web):
looking forward to testing this out tomorrow. I'm getting to know the ZWiki package pretty well, but I hadn't thought to look into the structured_text. time to stop trying to get around knowing python (after all, I'm running zope).


2002/03/04 20:42 GMT (via web):
worked! thanks... now that I can find where all these tags are getting inserted, I think I'm going to do some zope, zwiki, structured text hacking.


2002/03/05 20:35 GMT (via web):
What if I want to embed a reference to another document type in a WikiPage?? Suppose I upload a spreadsheet to a folder containing a Wiki Site. I should (and can) refer to the uploaded name via dtml. If I change the type of the uploaded document from application/x-octet-stream to application/spreadsheet, for instance, and set a helper in my brower to handle a application/spreadsheet type, shouldn't the Wiki page renderer send along some kind of header/whatever identifying the embedded object type? Instead, the file is rendered inline with the rest of the page. [ No, the file id is not a WikiWord. ]? Any thoughts on this?


Tim Dysinger, 2002/03/07 17:04 GMT (via web):
The problem that I mentioned early above regarding the extra tags in the html can also be fixed by specifying your standard_page_type and page_type to be classicwiki. I found the StructuredText problem about the same time as the person above. Rather than hack the server and the ZWiki code. I think I'll stick with classicwiki for now.

-TimDysinger?


2002/03/07 17:20 GMT (via web):
I have made some considerable hacks now to StructuredText, Parents.py, ZwikiPage?.py, the standard page header and footer. I say considerable because now the pages render valid xhtml1.1. However, they didn't require alot of work. Mostly it was just find and replace on the textual substitution procedures. Quite frankly, it's disappointing that with all the work people have obviously put into zope and zwiki that they didn't put in the right codes in the right order to validate.

of course, you can still add bad code if you want (no way to stop that), and I still have some ways to go to get rid of the extra "divs" that have been substituted for tables, but I think it's a great improvement. if you want the changes, or just more details about what I did, please email me at david.dickens@pepperdine.edu.


2002/03/07 17:22 GMT (via web):
maybe someone who's a professional programmer (as opposed to a server jockey like myself) can make proper "diff" files or something. or maybe even the maintainers of the products would like me to "nice up" my result so it can be graphed back into the main production trunc. this sort of stuff is a big deal to me, maybe it isn't to others.


2002/03/07 17:27 GMT (via web):
oh, and btw, my next project is to make the pages section 508 compliant (US government's accessability guidelines) and get as close to Web Content Accessibility Guidelines 1.0 (a w3c guideline) as possible as well. the only problem is that a few of these guidelines actually conflict with xhtml in minor ways. so I'll just have to get "as close" as possible.


Simon Michael <simon@joyful.com>, 2002/03/10 12:06 GMT (via mail):
One disk crash and reformat later...

linux ext2 users - did you know you can upgrade to ext3 with a simple tune2fs -j /dev/hdXX - if your kernel and disk utilities are up to date - making slow and scary post-crash disk repairs a thing of the past ?


Simon Michael <simon@joyful.com>, 2002/03/10 12:13 GMT (via mail):


> I change the type of the uploaded document from
> application/x-octet-stream to application/spreadsheet, for instance,
> and set a helper in my brower to handle a application/spreadsheet
> type, shouldn't the Wiki page renderer send along some kind of
> header/whatever identifying the embedded object type? Instead, the
> file is rendered inline with the rest of the page. [ No, the file id
> is not a WikiWord?. ] Any thoughts on this?

If you upload a spreadsheet or anything other than an image I would expect it to be linked (not embedded) in the zwiki page, and then clicking on that link you should indeed see the MIME type you configured. So I'm not clear what you're seeing here.


Simon Michael <simon@joyful.com>, 2002/03/10 12:16 GMT (via mail):
BillSeitz: thanks for the kudos. I thought we had a zwiki-in-the-news page but can't find it now.


Simon Michael <simon@joyful.com>, 2002/03/10 12:56 GMT (via mail):

> textual substitution procedures. Quite frankly, it's disappointing
> that with all the work people have obviously put into zope and zwiki
> that they didn't put in the right codes in the right order to
> validate.

We were waiting for you to come along. Thanks! Filed in the tracker as #112 structured text pages have extra html & body tags, and are not valid html/xhtml.

I do care about html and accessibility standards. It's good to know about the extra html & body tags, I'm guessing that started with the move to STXNG. The problem with fixing structured text is that it's part of zope, and so fixes need to go in via http://collector.zope.org/Zope . I'm sure a lot of people would like to see structured text made (X)HTML-clean.

That said, I have compensated for stx bugs in zwiki on occasion. If there are easy workarounds we can add as interim measures, I'm interested.


Simon Michael <simon@joyful.com>, 2002/03/10 13:30 GMT (via mail):
A very brief state of zwiki, 2002-03-10:
  recent happenings -
   rebuilt system after a disk crash
   learning pcl-cvs tricks - C-x v a generates a nice low-level changelog
   zenirc with John Wiegley's config rocks
   LA zope users' group meeting
   arch (http://regexps.com) is an interesting new version control system
   zwiki fixes coming from client work

  zwiki.org -
   new imeme setup working well, maintenance much easier, occasionally sluggish
   tracker enhancements - mailin to bugs@zwiki.org, latest issues on front page
   lost site traffic history in my disk crash 
   steady low-level discussion continues, no spam since subscribers-only policy

  zwiki -
   fear of 1.0 - releases slowing down! 
   approaching 0.9.9 release; then 0.9.10; 1.0 is some way off
   my priorities - 1. Testability 2. I18n, Docs 3. Scaling Zwiki Development

  recent work - 
   tests overhauled
    smarter, lighter unit tests, runnable from command line
    doctest still supported for the moment
    functional tests begun, using tres seaver's framework
   other things in cvs - wikimail enhancements, etc, see ChangeLog
   several renamings to be aware of: 
    wikis/ -> templates/
    zwiki_mailin.py -> mailin.py (tried to reverse this, couldn't)
    permissions! will need to update these on upgrading to 0.9.9

  some specific kinds of help needed - 
   update/write/specify unit, functional and other tests
   submit fixes for tracker issues (focussed patches preferred)
   collect, review & process patches/contributions
   wiki cleanup & organization
   write new documentation
   funding


Simon Michael <simon@joyful.com>, 2002/03/10 12:00 GMT (via mail):
"Michael R. Bernstein" <webmaven@lvcm.com> writes:
> I was wondering what versions of Zope were required for various versions
> of ZWiki. We're currently running ZWiki 0.8.2 on Zope 2.3.3, and I was
> wondering if Zope would have to be upgraded as well as ZWiki, or if we
> could upgrade ZWiki to 0.9.8 without upgrading Zope.

Hi Michael,

I'm not completely sure. Zwiki >= 0.7 requires zope >= 2.2, other than that there have been no hard version requirements. In that specific case I would expect no problems; I would back up and then do it. In general I always recommend running the latest zwiki version and I'd like to hear about problems preventing that. When we have a functional test suite this issue should be clearer.

Regards , --Simon (moved from ZWiki)


natesain, 2002/03/10 19:09 GMT (via web):
Looking further into the subject of extra HTML added by STXNG I've found a solution that only needs changes to ZWiki. ZWiki imports the StructuredText module which defines several ways of rendering a stx document: DocBook?,HTML,HTMLNG,HTMLWithImages?... the module also provieds several parsers that generate a DOM like structure from the stx source. If I understand corectly the HTML renderer is a backwards compatable function for those who want ClassicSTX? redering. I don't think the guys at Zope consider its inserting extra HTML to be a bug. The solution is to use the newer renderers in the StrucutredText? module. To use the newer renderers (like HTMLNG), use the Document parser to create a STX DOM structure and then pass that strucutre to HTMLNG. Doing this we can also pass the header arguement. So: text = str(StructuredText.HTML(text,level=3)) becomes text = str(StructuredText.HTMLNG(StructuredText.Document(text),level=3,header=0)) It would also be easy to experment with HTMLWithImages? which has syntax for adding images in STX: text = str(StructuredText.HTMLWithImages?(StructuredText.DocumentWithImages?(text),level=3,header=0))


SimonMichael, 2002/03/10 19:52 GMT (via web):
Great! This makes the test pass so without thinking any more about it BOOM! In it goes. Everybody watch out for related breakages in the next while.


SimonMichael, 2002/03/10 20:36 GMT (via web):
PS HTMLWithImages has the old problem and I don't see a HTMLNGWithImages.


SimonMichael, 2002/03/10 20:38 GMT (via web):
PPS by "the test" I meant the unit test I added earlier, testIssueNo0012StxDoubleHtmlTag.


Simon Michael <simon@joyful.com>, 2002/03/10 22:13 GMT (via mail):

The Changelog file has been renamed to CHANGES.txt and made similar to Zope's; appears on the ReleaseNotes page. These are the high-level changes.

A new ChangeLog? file is now generated from cvs history; appears on the page of the same name. This lists low-level cvs activity in a convenient place.


Simon Michael <simon@joyful.com>, 2002/03/12 01:56 GMT (via mail):
30-day database pack, 165M -> 100M


2002/03/12 16:27 GMT (via web):
Small thing: I set up zwiki but I needed to change "from ZWiki.ZWikiPage" to "from ZWikiPage" in ZWikiWeb?.py for it to work.


Simon Michael <simon@joyful.com>, 2002/03/12 18:25 GMT (new page):
ToastPage?


Simon Michael <simon@joyful.com>, 2002/03/12 18:30 GMT (via mail):

> Small thing: I set up zwiki but I needed to change "from
> ZWiki.ZWikiPage" to "from ZWikiPage" in ZWikiWeb?.py for it to work.

Is this with a very recent cvs version ?


Simon Michael <simon@joyful.com>, 2002/03/12 18:41 GMT (via mail):
RFC - zwiki now mails out only comments by default. This site still sends all edits, since it's usually low-traffic and I have found it useful. I'm thinking of changing zwiki.org to the default behaviour. Comments ?


Jos Yule <jos@trapeze.com>, 2002/03/12 19:38 GMT (via mail):

> RFC - zwiki now mails out only comments by default. This site still sends
> all edits, since it's usually low-traffic and I have found it useful. I'm
> thinking of changing zwiki.org to the default behaviour. Comments ?

That sounds good to me - JY


SimonMichael, 2002/03/12 20:07 GMT (via web):
Using my time machine I can tell the ayes will have it, so zwiki.org subscribers now receive comments only. I would like more notification options at some point.


Dan, 2002/03/12 20:47 GMT (via web):
What's the best-practices way of getting my Zwiki site -- on which I have done some customization of the header and footer stuff but not modified any functionality other than that -- up to snuff with the latest release here? This feature of notifying subscribers only of new comments is something I'd really like to incorporate.


Simon Michael <simon@joyful.com>, 2002/03/12 21:28 GMT (via mail):
Best practice would be CVS. Eg: cd into your Products directory and move your old ZWiki out of the way. Then:

cvs -d:pserver:anonymous@cvs.zwiki.sourceforge.net:/cvsroot/zwiki login (no password)

cvs -z3 -d:pserver:anonymous@cvs.zwiki.sourceforge.net:/cvsroot/zwiki co -d ZWiki zwiki

This will give you a ZWiki directory containing the latest and greatest. When you want to update this, within the ZWiki directory do

cvs update -dP

or the equivalent in your cvs gui if you use one. If you have modified some of the files locally, cvs will not overwrite them but will ask you to do a merge. Some details could be added here.


Simon Michael <simon@joyful.com>, 2002/03/12 21:31 GMT (via mail):
Also, you can browse this site's files at http://zwiki.org/zwikidir . These are exactly what the site is running right now, whereas cvs may occasionally be (even) more bleeding edge.


Dan, 2002/03/12 22:37 GMT (via web):
OK, thanks. I will have to talk to my Zope host service and see how this works itself out. I'm not certain I can run cvs from inside my Zope instance on their server. Not sure I can't, either!


SimonMichael, 2002/03/12 22:49 GMT (via web):
Ok, if it's a situation like eg Codeit where you install zope products via ftp, you would keep an up-to-date copy of the product locally (by cvs or other means) and periodically upload the latest files to your zope host using an ftp script or tool or something like sitecopy.


2002/03/12 23:39 GMT (via web):
Yeah, that works. I can install all the new products I want, so I just have to be careful not to step on my changes.


2002/03/13 14:27 GMT (via web):

Simon Michael <simon@joyful.com>, 2002/03/12 18:30 GMT (via mail):

> Small thing: I set up zwiki but I needed to change "from
> ZWiki.ZWikiPage" to "from ZWikiPage" in ZWikiWeb?.py for it to work.

Is this with a very recent cvs version ?

Yes; this is with the latest version. Notice, for example, that ZWikiPage.py has from CatalogAware? import CatalogAware? to import from the current directory, but ZWikiWeb?.py has from ZWiki.ZWikiPage import ZWikiPage which doens't work (unless you have a ZWiki package somewhere else in the search path...)


Simon, 2002/03/13 21:18 GMT (via web):
Server responding rather slowly at the moment :(

Colorful bugs! :) (see #37 do more with colours ?)


Simon, 2002/03/14 00:04 GMT (via web):
And, more tracker UI updates.


Simon Michael <simon@joyful.com>, 2002/03/16 19:58 GMT (via mail):
I grok the "import ZWiki.ZWikiPage" problem now.. fixed, thanks.


Simon Michael <simon@joyful.com>, 2002/03/17 00:06 GMT (via mail):
RFC - do you think the upcoming renamed permissions [1] should be:
 Add ZWiki Pages
 Add ZWiki Webs
 Zwiki: Add comments to wiki pages
 Zwiki: Change wiki page types
 Zwiki: Change wiki page content
 Zwiki: Reparent wiki pages
 Zwiki: Recycle wiki pages

or:

 Add ZWiki Pages
 Add ZWiki Webs
 Zwiki: Add a comment
 Zwiki: Change page type
 Zwiki: Edit this page
 Zwiki: Reparent page
 Zwiki: Recycle page

or something else ?

Changing these creates hassle for admins so I'd like to do it as infrequently as possible. Thanks, --Simon

[1] http://zwiki.org/ReleaseNotes


Simon Michael <simon@joyful.com>, 2002/03/17 01:29 GMT (via mail):
"Bill Seitz" <Bill@axiomlegal.com> writes:
 > see enclosed
 > * tweaks to Python files (these aren't core to weblog capabilities -
 > they cover supporting acronyms as wikinames, and expanding wikinames in
 > 'title' tags)
 > * *.zexp of folder containing just DTML views for weblog
 > [Attachment 2: ZWikiPage.py]
 > [Attachment 3: ZWikiRegexes.py]
 > [Attachment 4: wikiweblog-custom.zexp]

Hi Bill, thanks for sending these. I have uploaded them to [zwikidir/contrib]?.

NB neither these nor the other pending patches are top priority for me; my current plan[1] is to revisit patches after doing some i18n work.

In general if you or someone else thinks something should go into core zwiki sooner, any and all of the following will help: brief explanation of what this is and why it belongs in the core product, public discussion, focussed individual patches, unified diffs against latest cvs source, outraged demands from multiple would-be users, etc.

If none of these happen I'll look at this work as soon as I can. I think it will make a great wiki template. I assume it will be wanting some support methods not currently in the core product.

--Simon

[1] http://zwiki.org/SimonMichael


Simon Michael <simon@joyful.com>, 2002/03/18 18:09 GMT (via mail):
I just checked in:
  use a 'subscribers_list' list property instead of the
  'subscribers' property, and convert old instances on the
  fly. This needs more testing.  Also update the folder's
  _properties so folder subscribers appear in the ZMI.

I believe this is working now, but I would appreciate feedback from test pilots before next release. Here's how:

As always, save a copy of your data.fs just in case. Create a couple of dummy wiki & page subscribers if you don't have any. Then restart with the latest cvs zwiki (refresh may work in this case, I'm not sure). As you visit pages you should see the same page and wiki subscribers on the subscribe form that you had before. And in the ZMI you should see a subscriber_list lines property replacing the subscribers string property, with the proper subscriber addresses listed one per line.

And, in the hope of reaching the people affected: before getting this right I overwrote a couple of subscriptions on zwiki.org. If you were subscribed to a page other than GeneralDiscussion, you'll need to resubscribe. Sorry about that.

Thanks, -Simon


Simon Michael <simon@joyful.com>, 2002/03/18 18:55 GMT (via mail):
Dieter Maurer <dieter@handshake.de> writes:
> Zwiki: add page
> Zwiki: add webs
> Zwiki: add comment
> Zwiki: change type
> Zwiki: edit page
> Zwiki: reparent page
> Zwiki: recycle page

Zope names the add page/add wiki permissions itself, and "Add *" is consistent with all other zope products, so I thought it ok to leave those.

I could change my meta_type so they would be "Add Zwiki *", for consistent spelling, but I'm not ready to do that.

So, one vote for descriptive/consistent with other zope permissions, and one vote for brief/consistent with zwiki UI. At the moment I lean slightly towards:

  Add ZWiki Pages
  Add ZWiki Webs
  Zwiki: Add comments to pages
  Zwiki: Change page types
  Zwiki: Edit pages
  Zwiki: Reparent pages
  Zwiki: Recycle pages

Thanks for the replies; nb it looks as if your cc's to zwiki.org will have bounced since you're not subscribers, sorry about that.


Simon Michael <simon@joyful.com>, 2002/03/18 22:57 GMT (via mail):
Removed backlinks' "set" links for now. They are handy, but removing them is a simpler way to protect against robots than requiring authentication.


Simon Michael <simon@joyful.com>, 2002/03/19 00:58 GMT (via mail):
30-day pack, 175Mb -> 145Mb.

Re-enabled search and quote in header by default.


Simon Michael <simon@joyful.com>, 2002/03/19 06:20 GMT (via mail):
There's a problem with wiki subscribers getting copied into the page subscriber list (when you do an edit ? I haven't figured it out).


BillSeitz, 2002/03/20 20:52 GMT (via web):
Where in the queue stands a feature to ease renaming a page? The key requirements being to (a) fix the Parents list of any pages for which the renamed page was the parent, and (b) changing the content of any other pages that Backlink to the renamed page.


Simon, 2002/03/22 04:48 GMT (via web):
I agree it's worth doing.. I'm inclined to do it for 0.9.10.


Simon Michael <simon@joyful.com>, 2002/03/26 19:10 GMT (via mail):
Hi =C1lvaro,

cc'ing the general comments to the wiki, I hope you don't mind.


> 1. I've not seen the translation I sent you amongst the
> wiki templates in cvs, are you planning to include it after
> all?

Not presently.. in general I would like template releases and maintenance to be decoupled from the core product. I would be glad to see you publish it on the wiki, any time you like - let me know if there are problems with this approach. After 0.9.9 I will be focussing on i18n and will look at it more closely, if it makes sense to bundle it I will. See more below.


> 2. I have an example of a growing and interesting wikisite
> for you to see. They (we) are very happy with zwiki (and
> they're going to REALLY love the Tracker thing, once I
> manage to install it --will it be default in next version?
>
> http://alqua.com/tmresources

Thanks! I love to see examples of what others are doing with zwiki. Texmacs sounds cool and I saw a tex user calling the site a joke so must investigate later :)

Yes, the (latest) tracker is something I would like to bundle in some form - any ideas ? As with your translation, I suppose it makes sense to go in this order:

  1. build it by hand (done)
  2. publish on the wiki as a zodb template (a zexp for import into /Control_Panel/Products/ZWiki)

2a. alternately: publish as a filesystem template (a tarball for unpacking in Products/ZWiki/templates). Filesystem templates can create only zwiki pages and dtml methods by default, though scripts could be provided for other things like catalog setup.

  1. if it turns out to be generally useful enough, add it to the core product as an included filesystem template, integrating any required support code, ui's, etc.


> 3. ooh, I can no longer resist temptation, when will 0.9.9 be out, ;)

The only thing stopping it now is the doSubscriberListFixups bug which copies subscribers from the wiki list to the page list when you comment on a (pre 0.9.9 only ?) page. I am waiting for more energy to figure this object migration stuff out, or a kind soul to sort it out for me. (I found a diversion: hacking on Frozen-Bubble !)

Best regards --Simon


Simon Michael <simon@joyful.com>, 2002/03/26 19:12 GMT (via mail):
Is it just me, or has this site been extremely slow for a week or two ?


EdwardKreis, 2002/03/27 09:15 GMT (via web):
Probably, just you, as for me the site seems as usual - sometimes little slower or faster but no extreme changes in speed.


John Hunter <jdhunter@ace.bsd.uchicago.edu>, 2002/03/27 16:18 GMT (via mail):

When I try to write dtml tags in my ZWiki, I get an error when I try to save the Zwiki page. I want these tags to be rendered literally as code, eg <pre> so I tried the :: example syntax. Below is the ZWiki

Solution

Use the PARENTS object. In this case:

    dtml-in "PARENTS[0].objectValues()"

is what you are looking for

But I want to put the '<' and '>' around the dtml-in tag, ZWiki will not save this.

How can I include literal DTML tags in ZWiki?

Thanks, ZWiki-0-9-8


2002/03/28 12:25 GMT (via web):
You can probably include '<' and '>' by encoding it as: &< and &&rt;


2002/03/28 12:27 GMT (via web):
Hmm, i meant &lt; and &rt


2002/03/28 13:47 GMT (via web):
Not having my day... You can encode '<' as &lt; and '>' as &gt;

BTW It takes about 40 seconds to add this (anonymous) comment. This might be caused by sending the comment over e-mail. It might be better to use Maildrophost (http://www.dataflake.org/software/maildrophost) instead of Mailhost.


John Hunter <jdhunter@ace.bsd.uchicago.edu>, 2002/03/28 14:46 GMT (via mail):

Yes, Thanks for the tip. I know about < and >, but I expected '<' and'>' to work because they work for structured text, eg, in the CVS source for The Zope Book, all that is needed is to be in a code environment with the :: syntax and you can post DTML in literally. If you are writing ZWiki about DTML, which is what I want to do, it is a hell of a lot more convenient for the code environment to render literally. I am actually surprised this doesn't work, because it's my understanding that ZWiki derives from StructuredText.


Dean, 2002/03/28 16:00 GMT (via web):
TextFormattingRules insight needed... I'm having a trouble with lists and heirarchial lists outside of plain text (no wrapping. =() and HTML.

Also finding that adding extra spaces between paragraphs does not seem natural.

Any suggestions?

Also.. How do you register an "indent" without using the TAB key? (IE TextEdit? control nuance..)


2002/03/28 16:27 GMT (via web):
Can you update DownloadZwiki? and/or ZWikiInstallation? pages to explain how the CVS-version can be installed. I cannot find the ZWikiWebs?.zexp in the CVS-checkout. I would love to try 0.9.9.

I managed to get the files from CVS using: cvs -d:pserver:anonymous@cvs.zwiki.sourceforge.net:/cvsroot/zwiki login cvs -z3 -d:pserver:anonymous@cvs.zwiki.sourceforge.net:/cvsroot/zwiki co zwiki


Simon Michael <simon@joyful.com>, 2002/03/29 21:19 GMT (via mail):

> Can you update DownloadZwiki? and/or ZWikiInstallation? pages to explain
> how the CVS-version can be installed. I cannot find the ZWikiWebs?.zexp
> in the CVS-checkout. I would love to try 0.9.9.

I think you'll see the sourceforge cvs instructions when you click "accessed" on the DownloadZwiki? page ? Also I sent brief instructions to this page in the last month or two, maybe someone can dig it up. ZWikiWebs?.zexp no longer exists in the product, if you saw some documentation that made you think it was needed please say where.


Simon Michael <simon@joyful.com>, 2002/03/29 21:25 GMT (via mail):

> TextFormattingRules insight needed... I'm having a trouble with lists
> and heirarchial lists outside of plain text (no wrapping. =() and HTML.

Are we talking about the structured text page type ? I'm not sure what problem you're seeing.


> Also finding that adding extra spaces between paragraphs does not seem
> natural.

Right, structured text doesn't support it.. I would use <br>'s for now.


> Also.. How do you register an "indent" without using the TAB key? (IE
> TextEdit? control nuance..)

It'll have to be spaces, I guess..


Simon Michael <simon@joyful.com>, 2002/03/29 21:35 GMT (via mail):
John Hunter <jdhunter@ace.bsd.uchicago.edu> writes:
> Yes, Thanks for the tip. I know about < and >, but I expected <
> and'>' to work because they work for structured text, eg, in the CVS
> source for The Zope Book, all that is needed is to be in a code
> environment with the :: syntax and you can post DTML in literally. If
> you are writing ZWiki about DTML, which is what I want to do, it is a
> hell of a lot more convenient for the code environment to render
> literally. I am actually surprised this doesn't work, because it's my
> understanding that ZWiki derives from StructuredText.

Zwiki supports various page rendering modes, several of which are based on structured text. I think you're using the structuredtextdtml page type ("Structured text + zwiki + HTML + DTML" on the editform). Not even the all-powerful :: can prevent DTML from being executed in this case. I think if you change your pages to "Structured text + zwiki + HTML" or "Structured text + zwiki" it will do what you want. In fact the former is the default for new wikis. If this is not making sense, let me know.


Simon Michael <simon@joyful.com>, 2002/03/29 21:40 GMT (via mail):

> Probably, just you, as for me the site seems as usual - sometimes little
> slower or faster but no extreme changes in speed.


> BTW It takes about 40 seconds to add this (anonymous) comment. This

Hmm, thanks for the data points. Keep 'em coming. Mailhost does not normally seem to cause a slowdown, I am suspecting general server performance issues in this case.


2002/03/29 21:59 GMT (via web):
Imeme made some performance improvements to the server last wednesday, which may have helped. More data points will clarify the situation.


2002/03/29 22:00 GMT (via web):
ok, I saw a really slow comment there. Will keep you posted on progress.


John Hunter <jdhunter@ace.bsd.uchicago.edu>, 2002/04/01 15:39 GMT (via mail):

>>>>> "Simon" =3D=3D Simon Michael <simon@joyful.com> writes:

Simon> Zwiki supports various page rendering modes, several of Simon> which are based on structured text. I think you're using Simon> the structuredtextdtml page type ("Structured text + zwiki Simon> + HTML + DTML" on the editform). Not even the all-powerful Simon> :: can prevent DTML from being executed in this case. I Simon> think if you change your pages to "Structured text + zwiki Simon> + HTML" or "Structured text + zwiki" it will do what you Simon> want. In fact the former is the default for new wikis. If Simon> this is not making sense, let me know.

Yep, this makes perfect sense and that is what I thought was the source of the problem. My idea was to create a new wiki which does not support DTML and then copy all the files over. But when I created the new wiki, I was only given one type to choose from (with a checked checkbox):

  Type: zwikidotorg
=A0
I remember with earlier ZWiki installs I could choose with HTML or
with HTML+DTML but now I don't see where to set this.  Is it a ZWiki
Page option or a ZWiki web option?

OK, I just took a look at properties of some of my ZWiki pages. I see the page_type property; mine is set to structuredtext so it surprises me that it is choking on my dtml code (it returns the error 'No closing tag, for tag < dtml-in "PARENTS[0]?.objectValues()">, on line 18 of ZopeHowtos'=20

Thoughts?

Thanks, John Hunter=20